Invoking (Starting) the Spawner

After you have used IT Administrator or configuration files to define a server and spawner, you are ready to invoke and administer the defined spawners. Refer to the appropriate startup procedures for your server platform:

• Starting the Spawner on Windows
• Starting the Spawner on UNIX
• Starting the Spawner on Alpha/VMS

After you have started the spawner, you can connect to the spawner as an administrator (operator) to monitor and control the spawner's operation. For instructions, see Monitoring the Spawner Using Telnet.

Security Considerations

The spawner can be launched with the -nosecurity option. However, this option should be used with caution, since it will allow any client connecting to the spawner to obtain an object server using the same user ID that launched the spawner. This means that any client that can manipulate the host file system can obtain an object server as if the client had the user ID that launched the spawner.

Note: If you use the -nosecurity option, the -install option is ignored.

Example Commands

The following are examples of the spawner command in the UNIX and Windows NT environments:

• UNIX example using an LDAP server:

  prompt> /sasv9/utilities/bin/objspawn -sasverbose
  	-saslogfile /usr/logs/obj.log
  	-ldaphost ldapsrv.alphalite.com  -ldapport 389
  	-sasSpawnercn Finance
  	-ldapbase "sascomponent=sasServer,cn=ldapsrv,
  	   o=Alphalite Airways,c=us"
  	

• UNIX example using a configuration file:

  prompt> /sasv9/utilities/bin/objspawn -configFile objspawn.cfg

• Windows NT example for launching a spawner that connects to a secure LDAP server with a default port of 389. The -sasSpawnercn option tells the spawner to use the sasSpawner definition of IOMSpawner. The -ldapBase tells the spawner where in the tree to start searching for the server, spawner, and login definitions. This -ldapbinddn option tells the spawner to bind to the LDAP server with the user "uid=sasiom1,ou=People,o=ABC Inc,c=US"

  c:\sasv9> objspawn -ldapHost machine.abc.sas.com -ldapPort 389
    -ldapBase "sasComponent=sasServer,cn=SAS,o=ABC Inc,c=US"
    -sasSpawnercn IOMSpawner -sasverbose
    -ldapbinddn "uid=johndoe,ou=People,o=ABC Inc,c=US"
    -ldapPw mypassword -sasLogFile objspawnldap.log
  

• Windows NT example for launching a spawner with an LDIF configuration file:

  c:\sasv9>objspawn -configFile c:\sasv9\objspawn.cfg
  

Notes:

1. In the first and third examples, the command line options point the spawner to the LDAP server and base distinguished name where the configuration parameters are located.
2. In the second and fourth examples, the command line options point the spawner to a configuration file (objspawn.cfg) where the configuration parameters are located.
3. The invocation options vary depending on the platform. Refer to the Spawner Invocation Options for details.
4. On Windows, in most cases you should install the spawner as an NT service using the -install option.
5. If you do not specify the -sasSpawnerCn option, the object spawner uses the first sasSpawner definition (on the LDAP server) that has the same machine name as the current host.