Metadata Overview (IOM Bridge)

The metadata that supports Integration Technologies consists of objects, each defined by a collection of attributes that define the object. The metadata for an IOM Bridge server configuration must include the following classes of objects:

• sasServer object. A sasServer object contains startup and connection information for a particular instance of a SAS object server. For each instance of an object server, the following information is defined in the metadata:

  • Server name
  • Machine name
  • Connection information, including service or port
  • Other information including logical names, encryption information, commands, and workspace pooling information, as required.

  For detailed information about the attributes included in the metadata for a server, see the sasServer Attributes List.

• sasSpawner object. A sasSpawner object contains configuration information for a particular instance of a SAS spawner. The spawner is a program that must run on a server machine when an IOM bridge server configuration is used. The spawner listens for and authenticates incoming client requests and launches server instances as needed. For each spawner instance, the following information is defined in the metadata:

  • Spawner name
  • Machine name
  • Other information, including logical names and encryption information, as required

  For detailed information about the attributes included in the metadata for a spawner, see the sasSpawner Attributes List.

The following classes of objects are optional:

• The sasLogin object is a convenient tool to provide the credentials necessary for a spawner to start a SAS session. Using logins, the spawner can create SAS sessions without having to keep track of the specifics of a user's ID and permissions. For each sasLogin instance, the following information is defined in the metadata:

  • Login name
  • Person references for authorized users or groups of users
  • The SAS login and password needed to access the SAS object server
  • Domain name
  • Logical name

  For detailed information about the attributes included in the metadata for a SAS login, see the sasLogin Attributes List.

• The sasLogicalNameInfo object is created automatically if you use IT Administrator to assign a logical name to a spawner or server. Logical names are used to create resource groupings. For more information, refer to Assigning Logical Names and sasLogicalNameInfo Attributes List.

• The sasDependentSpawner object can be used to define dependent spawners, which assist the main, or master spawner, in handling client requests for an IOM server. For more information, refer to Configuring a Dependent Spawner and sasDependentSpawner Attributes List.

The following example configuration files demonstrate the basic metadata needed to create a working IOM Bridge server configuration:

• Example Minimal Configuration
• Example Server and Spawner
• Example Using Logical Names
• Example UUID Generator
• Example Dependent Spawner