Using a Configuration File to Define the Metadata (IOM Bridge)

If you do not use LDAP as the metadata repository, you can create a flat configuration file that contains the object definitions for an IOM Bridge server configuration. The configuration file must then be installed on the server and on each client machine.

Note: If your configuration requires more than one or two servers, or if multiple clients will be using the servers, we strongly recommend the use of LDAP as a central metadata repository. The use of LDAP also gives you the ability to use access control lists to control access to the servers in your enterprise.

To define an IOM Bridge server configuration using a configuration file:

1. Use a text editor to code the configuration file. At a minimum, the file must define a server object and a spawner object. You can also define one more more SAS login objects, logical name objects, and/or dependent spawner objects. To create the file:

   • Refer to the attribute descriptions for each object type:
     • Attributes for sasLogin
     • Attributes for sasLogicalNameInfo
     • Attributes for sasServer
     • Attributes for sasSpawner
     • Attributes for sasDependentSpawner

   • Refer to the following examples:
     • Example Minimal Configuration
     • Example Server and Spawner
     • Example Using Logical Names
     • Example UUID Generator
     • Example Dependent Spawner

   • Use the LDAP Data Interchange Format (LDIF), format, which has the following syntax rules:

     • Start each entry in column one.

     • To indicate a comment line, place '#' in column one.

     • Use the following general format for each entry: "attribute: value".

     • If an entry spans multiple lines, insert a blank in the first column of each continuation line. The blank in column one is a continuation character and is consumed by the LDIF file parser. Therefore, it should not be considered part of the entry.

     • A blank line must precede a distinguished name (exclude comment lines and the first distinguished name in the file). In LDIF, the DN is required to identify the beginning of the next object class definition. The spawner's LDIF parser relies on this requirement in order to separate object class definitions. The DN name can be any value, unless it is a sasMultiUserObject attribute that points back to a sasLogin object class instance, in which case the specific DN name must be used.

     • Two consecutive blank lines indicate the end of the configuration file definitions.

2. Save the file with a name of your choice (for example, objspawn.cfg).

3. Install the file on the server machine and on each client machine.

You can now start the spawner. For instructions, refer to Starting the Spawner.