|Administering SAS Servers|
Summary of Setup Steps
Creating the Metadata
Using the IT Administrator
Using IT Administrator:
SAS Login Object
Using a Configuration File
Configuring a Dependent
Configuring a UUID Generator
Configuring and Starting
the Spawner on OS/390
Invoking (Starting) the Spawner
Spawner Invocation Options
Administering the Spawner:
Using the Configuration
Spawner Error Messages
Server and Spawner
Using Logical Names
Attributes for sasLogin
Attributes for sasServer
Attributes for sasSpawner
Setting Up an IOM Bridge Server: Introduction
An IOM Bridge server configuration enables client access using the IOM Bridge for COM or IOM Bridge for Java.
The IOM Bridge for COM is a software component of Integration Technologies that is used (transparently) to enable native COM/DCOM applications to access server data on either Windows platforms or on non-Windows platforms such as a UNIX or OS/390. The IOM Bridge for Java is used (transparently) when a Java client accesses an IOM Server. This bridge allows developers to write Java applications that access server data.
For more information about the IOM Bridge for COM and the IOM Bridge for Java, refer to Connecting Clients to IOM Servers.
When to Use an IOM Bridge Server Configuration
You must use an IOM Bridge server configuration if:
You can also use an IOM Bridge server configuration if the object server will run on a Windows machine and will be accessed by Windows clients. In this situation, clients will connect to the server using the IOM Bridge instead of COM/DCOM.
Components of an IOM Bridge server configuration
An IOM Bridge Server configuration consists of:
How an IOM Bridge Server Works
In order for an IOM Bridge server to be available to clients, the spawner program must be running on the server machine. When a client application needs to access the object server, it uses Integration Technologies distributed objects to submit a request to the object spawner for a SAS workspace. To obtain information about the server and spawner, the application accesses metadata from the LDAP server or configuration file. Alternatively, the server information can be imbedded in the application program.
On receiving the request, the object spawner authenticates the user and launches an object server. The client then uses server configuration information from the LDAP server or configuration file to requests a workspace on the server.
After acquiring a workspace, the client application uses Integration Technologies distributed objects to issue one or more requests for SAS language services, data services, file services, or utilities. The SAS software processes these requests in the workspace and returns information to the client.
When the client application is finished using the server, it issues a request to close the workspace.