SAS® Integration Technologies: Administrator's Guide (LDAP Version)

Starting the Spawner on Windows
To start the spawner on a Windows host:
1. Note: This step is only necessary if you are not starting the spawner as a service.
Define the user rights for the administrator. The user who invokes the spawner, in addition to being an
administrator, must have the following user rights:
♦ replace the process level token.
♦ act as part of the operating system (Windows NT and Windows 2000, not needed if you install the
spawner as a service)
♦ adjust memory quotas for a process (Windows XP only, not needed if you install the spawner as a
service )
♦ increase quotas (Windows NT and Windows 2000, not needed if you install the spawner as a service)
To set the administrator's user rights on Windows NT:
a. Select Start Programs Administrative Tools User Manager.
b. From the Policies pull−down menu, select User Rights.
c. Click the Show Advanced User Rights check box.
d. Add rights using the Right: drop−down menu.
To set the administrator's user rights on Windows 2000:
a. Select Start Settings Control Panel Administrative Tools Local Security Policy.
b. Select Security Settings Local Policies User Rights Assignment.
c. Add rights by double−clicking on each right and assigning the appropriate users.
To set the administrator's user rights on Windows XP:
a. Select Start Settings Control Panel Administrative Tools Local Security Policy.
b. Expand the tree for Local Policies and select User Rights Assignment.
c. Add rights by double−clicking on 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 batch job.
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. The
spawner program is installed in your installed SAS folder. 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:\sasv9 is the installed SAS folder and objspawn.cfg is an LDIF
configuration file. In the last example, spawner2.xml is an XML metadata configuration file that was
created using the Integration Technologies Configuration application.
Note: Some of the example commands are broken into more than one line for presentation purposes.
However, the command must be entered as a continuous text stream on the command line.
♦ The following command installs the spawner as an NT service and updates the registry to hold the
options that are specified (in this case −configFile):
Starting the Spawner on Windows 141