SAS 9.1.3 Integration Technologies » Server Administrator's Guide


Starting Servers
Server Startup Command
Specifying Metadata Connection Information
Customizing the Server Command for COM/DCOM Connections
Initializing UNIX Environment Variables for Workspace Servers
Invoking (Starting) the Spawner
On Windows
Updating a Spawner Service
On UNIX
On Alpha/VMS
Server and Services Startup Order
Reference Materials
Object Server Parameters
Spawner Invocation Options
Starting Servers

Invoking (Starting) the Spawner

After you have created a metadata configuration file for the metadata server, you can then use the metadata configuration file to invoke and administer the defined spawner. 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 (operator) to monitor and control the spawner's operation. For instructions, see Monitoring the Spawner Using Telnet.

Example Commands

In the following examples, objspawn.xml is the metadata configuration file that you created using the METACON command in SAS. The following are examples of the spawner command in the UNIX and Windows NT environments:

  • UNIX example using a configuration file:

    prompt> /sasv91/utilities/bin/objspawn 
      -sasSpawnercn "Spawner 1" -xmlconfigFile objspawn.xml
      -sasLogFile "/sasv91/utilities/bin/objspawn.log"
    
  • Windows NT example using a configuration file:

    c:\program files\sas\sas 9.1> objspawn -sasSpawnercn Spawner1
       -xmlConfigFile objspawn.xml -install
       -sasLogFile "c:\logs\objspawn.log"
    

Notes:

  • In these examples, the command line options point to a spawner definition to use and a configuration file (objspawn.xml) where the configuration parameters are located.
  • The invocation options vary depending on the platform. Refer to the Spawner Invocation Options for details.
  • On Windows, in most cases you should install the spawner as a Windows NT service using the -install option.
  • If you do not specify the -sasSpawnerCn option, the object spawner uses the first sasSpawner definition (on the metadata server) that has the same machine name as the current host.