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 start-up procedures for your server platform:

As you use these instructions, refer to the list of Spawner Invocation Options that are available.

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

Security Considerations

You should consider the following points relative to security and access control options for the spawner in development environments:

In a Windows environment, 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 userid 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 userid that launched the spawner.

Note: If you use the -install option to install the spawner as an NT service, do not use the -nosecurity option.
In a UNIX environment, a client can connect to and use the spawner if it presents the same credentials that were used to start the spawner. This means that you can launch the spawner using the ID of the developer that needs access to it. This prevents you from having to start the spawner with root privileges. If the host makes use of shadow passwords, you will need to specify the -authprog option.

Example Commands

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

UNIX example using an LDAP server:

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

UNIX example using a configuration file:

prompt> /sasv8/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:\sasv8> objspawn -ldapHost machine.abc.sas.com -ldapPort 389 
  -ldapBase "sasComponent=sasServer,cn=SAS,o=ABC Inc,c=US" 
  -sasSpawnercn IOMSpawner -ldapbinddn "uid=johndoe,ou=People,o=ABC Inc,c=US"
  -ldapPw mypassword -sasLogFile objspawnldap.log -sasverbose
```
Windows NT example for launching a spawner with an LDIF configuration file:
```
c:\sasv8> objspawn -configFile c:\sasv8\objspawn.cfg
```

Notes:

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.
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.
The invocation options vary depending on the platform. Refer to the Spawner Invocation Options for details.