Starting the Spawner on Windows

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

   Define the user rights for the user who invokes the spawner. The user who invokes the spawner, in addition to being a Windows administrator, must have the following user rights:

   • act as part of the operating system (Windows NT and Windows 2000).

     This right needs to be held by the owner of a multi-user SAS session that will be authenticating connecting clients. This right is also required for the owner of the objspawn process. The Windows routine LogonUser() requires this user right for the process owner in order for it to authenticate other users.

   • adjust memory quotas for a process (Windows XP only).

     This right needs to be held by the owner of an objspawn process. The Windows routine CreateProcessAsUser() requires this user right for the process owner in order for that user to be able to launch SAS sessions on behalf of the connecting client.

   • increase quotas (Windows NT and Windows 2000).

     This right needs to be held by the owner of an objspawn process. The Windows routine CreateProcessAsUser() requires this user right for the process owner in order for that user to be able to launch SAS sessions on behalf of the connecting client.

   • replace the process level token.

     This right needs to be held by the owner of an objspawn process. The Windows routine CreateProcessAsUser() requires this user right for the process owner in order for that user to be able to launch SAS sessions on behalf of the connecting client.

   To set the administrator's user rights on Windows NT:

   1. Select Start Programs Administrative Tools User Manager.
   2. From the Policies drop-down list, select User Rights.
   3. Select the Show Advanced User Rights check box.
   4. Add rights using the Right drop-down list.

   To set the administrator's user rights on Windows 2000:

   1. Select Start Settings Control Panel Administrative Tools Local Security Policy.
   2. Select Security Settings Local Policies User Rights Assignment.
   3. Add rights by double-clicking each right and assigning the appropriate users.

   To set the administrator's user rights on Windows XP:

   1. Select Start Settings Control Panel Administrative Tools Local Security Policy.
   2. Expand the tree for Local Policies and select User Rights Assignment.
   3. Add rights by double-clicking each right and assigning the appropriate users.
      
      

2. Define the user rights for each client that connects to the spawner. Similar to the administrator, each client that connects to the spawner must have the following user right: log on as a batch job.

   The log on as a batch job user right needs to be held by every client that you want to connect into a multi-user SAS session or objspawn. The Windows routine LogonUser() requires this user right in order to authenticate the client's credentials.

3. Restart Windows to apply the new user rights.

4. Start the spawner program (called objspawn.exe) using a command that specifies the appropriate options. (You should have already created a metadata configuration file for the spawner to use to access the SAS Metadata Server.) In most cases, you should install the spawner as a service. Refer to the Spawner Invocation Options for a complete list of valid options for the command.

   In the following examples, c:\program files\sas\sas 9.1\objspawn is the installed SAS folder and c:\objspawn.xml is the metadata configuration file that you created using the METACON command in SAS.

   • The following command installs the spawner as a Windows NT service and updates the registry to hold the options that are specified (in this case -sasSpawnercn and -xmlConfigFile):

     c:\program files\sas\sas 9.1\objspawn -sasSpawnercn Spawner1 
        -xmlconfigFile c:\objspawn.xml -install
     

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

   • The following command installs the spawner as a Windows NT service, specifies service dependencies, and names the service:

     c:\program files\sas\sas 9.1\objspawn -sasSpawnercn NameofSpawner
       -installDependencies "service1;service2" 
       -name serviceName -xmlconfigfile c:\objspawn.xml
       -install
     

   • The following command launches the spawner with the configuration file and specifies a log file:

     c:\program files\sas\sas 9.1\objspawn -sasSpawnercn "Spawner 1" 
        -xmlconfigFile c:\objspawn.xml -saslogfile c:\logs\objspawn.log
     

Note: After the spawner is started, a message is written to the application event log indicating whether objspawn initialization completed or failed.