SAS 9.1.3 Integration Technologies » Administrator's Guide (LDAP Version)


Setting up an IOM Bridge Server and Spawner
Quick Start: Simple Server and Spawner
Summary of Setup Steps
Spawner Overview
Spawner Requirements
Metadata Overview
Creating the Metadata for an IOM Bridge Server
Using the IT Administrator Wizard
Using IT Administrator
SAS Login Object
Server Object
Spawner Object
Using a Configuration File
Configuring a UUID Generator
Configuring and Starting the Object Spawner on z/OS
Invoking (Starting) the Spawner
On Windows
On UNIX
On Alpha/VMS
Spawner Invocation Options
Administering the Server and Spawner:
Using Telnet
Using the IT Configuration Application
Spawner Error Messages
Metadata Examples
Minimal Configuration
Server and Spawner
Using Logical Names
UUID Generator
Message Queue Polling
Reference Materials
Attributes for Logical Names
Attributes for Logins
Attributes for Servers
Object Server Parameters
Server Startup Command
Attributes for Spawners
Initializing UNIX Environment Variables for Workspace Servers
IOM Bridge Servers

Starting the Spawner on UNIX

The SAS object server is launched in the client's home directory (as specified in the client's password entry). If the client has a directory in its home directory that is named the same as its user ID, SAS will use that directory as the SAS session's SASUSER path.

Note: If you are printing or using SAS/GRAPH procedures, you must set the DISPLAY environment variable to a running X server. For example:

export DISPLAY=<machine name>:0.0

Ensure that the setuid root bit is set for elssrv, sasauth, and sasrun. If the setuid root bit is not set for these utilities, objspawn will not be able to launch SAS sessions. For details about setting the setuid root bit, see Changing the setuid Permissions to Root.

Start the spawner program (called objspawn) using a command that specifies the appropriate options. Refer to the Spawner Invocation Options for a complete list of valid options for the command. The following examples use "/sasv9/" as the directory in which SAS was installed.

Note: Some of the example commands are broken into more than one line for presentation purpose. However, the command must be entered as a continuous text stream on the command line.

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

    prompt> /sasv9/utilities/bin/objspawn 
       -configFile objspawn.cfg
  • The following command launches the spawner with the configuration information on an LDAP directory server:

    prompt> /sasv9/utilities/bin/objspawn 
       -ldapHost machine.abc.com 
       -ldapBase "sasComponent=sasServer,
          cn=SAS,o=ABC Inc,c=US"
    
  • The following command launches the spawner, specifying the sasSpawner definition to use, with the configuration information on an LDAP server:

    prompt> /sasv9/utilities/bin/objspawn 
       -ldapHost machine.abc.com
       -ldapBase "sasComponent=sasServer,
          cn=SAS,o=ABC Inc,c=US"
       -sasSpawnercn mySpawner
    

Note: After the spawner is started, an attempt is made to write a message to stdout indicating whether objspawn initialization completed or failed.

Changing the setuid Permissions

You can change the setuid permissions of files in !SASROOT/utilities/bin and set the owner to root by using either of the following methods.

Method 1: Using SAS Setup

  1. Log in to the root account.
    $ su root
  2. Run SAS Setup from !SASROOT/sassetup.
  3. Select Run Setup Utilities from the SAS Setup Primary Menu.
  4. Select Perform SAS System Configuration.
  5. Select Configure User Authorization.

Method 2: Using the Command Line

From a UNIX prompt, type the following:

$ su root
# cd !SASROOT/utilities/bin
# chown root elssrv sasauth sasperm sasrun
# chmod 4755 elssrv sasauth sasperm sasrun
# exit