Quick Start: Simple Server and Spawner

The following steps help you to get a simple server and spawner IOM Bridge connection up and running on a Windows or UNIX platform. For details about setting up more complex configurations, see Summary of Setup Steps (IOM Bridge Server).

Windows

1. Install SAS Version 9 (including SAS Integration Technologies) on the server machine. Refer to the SAS documentation for the details of this procedure.

2. Use a Windows editor to create an LDIF configuration file and save it as c:\objspawn.cfg. Use the following example of a minimal LDIF configuration file: Configuration File Example: Minimal Configuration. Replace the sasCommand statement with the Windows location of the SAS system. For example:

   sasCommand: "c:\Program Files\SAS\SAS 9.1\sas"
      -config "c:\Program Files\SAS\SAS 9.1\sasv9.cfg"
   

3. Note: This step is only necessary if you are not starting the spawner as a service.

   Define Windows User Rights for the administrator. (For detailed instructions about defining Windows User Rights, see Starting the Spawner on Windows). The user who invokes the spawner must be an administrator and must have the following user rights:
   
   
   • act as part of the operating system (Windows NT and Windows 2000)
   • increase quotas (Windows NT and Windows 2000)
   • replace the process level token
   
   

4. Define Windows User Rights for each client. For each client that connects to the spawner, specify

   • log on as batch job
   
   
5. Start the Object Spawner with the objspawn.cfg configuration file using one of the following methods:
   
   

   • To start the object spawner with the objspawn.cfg configuration file, from a DOS command window enter the following command:

     c:\Program Files\SAS\SAS 9.1> objspawn
        -configFile  C:\objspawn.cfg
     

   • To install the object spawner as a service and update the registry to hold the options that are specified (in this case -configFile), from a DOS command window enter the following command:

     c:\Program Files\SAS\SAS 9.1> objspawn
        -configfile c:\objspawn.cfg  -install
     

     Use the Windows "net start" command to start the object spawner as a Windows service (case does not matter):

     net start "sas object spawner daemon"
     

     Note: When you install the spawner as an NT service, you must specify the fully-qualified path to the configuration file. When the spawner is started as an NT service, it will self configure using the options that are placed in the registry at install time.

     Note: When using the Windows Services utility, the object spawner service appears as the SAS Object Spawner Daemon II.

   For the complete list of spawner invocation options, see Spawner Invocation Options.

6. Test your server connection using the Integration Technologies Configuration application (ITConfig), which is installed with the Integration Technologies Windows Client Development Component. See Using the Integration Technologies Configuration Application.

UNIX

1. Install SAS Version 9 (including SAS Integration Technologies) on the server machine. Refer to the SAS documentation for the details of this procedure.

2. For sasrun, sasauth, and elssrv, the setuid bit must be set and the owner must be root. To set the setuid bit and set the owner to root, see Changing the setuid Permissions
   
   
3. Locate a user or temporary directory where you can write and save a configuration file. For example,

   /users/myid
   

4. Use an editor to create an LDIF configuration file and save it as objspawn.cfg. Use the following example of a minimal LDIF configuration file: Configuration File Example: Minimal Configuration. Replace the sasCommand statement with the location of the SAS system.

5. To start the object spawner with the objspawn.cfg configuration file, from a UNIX system prompt enter the following command:

   /sasv9/utilities/bin/objspawn
      -configfile /users/myid/objspawn.cfg
   

   For the complete list of spawner invocation options, see Spawner Invocation Options.
   
   
6. Test your server from a Windows machine using the Integration Technologies Configuration application (ITConfig), which is installed with the Integration Technologies Windows Client Development Component. See Using the Integration Technologies Configuration Application.