Administering SAS Servers |
The sasSpawner object class contains information for an instance of a SAS spawner. The sasSpawner object class is defined using the attributes listed in the following table. For each option, the table shows:
The name that identifies the attribute on the LDAP server (or in the configuration file). Under each attributes name, the table shows the corresponding tab and field name in the IT Administrator application.
"Required" or "Optional" to indicate whether the attribute is required.
The type of server configuration for which the attribute is used. Note: Spawners are used only in IOM Bridge configurations. Therefore, IOM Bridge is listed as the server type for each option.
A definition of the attribute.
For step-by-step instructions on defining the metadata for a spawner, refer to Using the IT Administrator Wizard to Define a Server and Spawner or Using IT Administrator to Define a Spawner. If you are not using an LDAP server, you can use a configuration file to define a spawner. For instructions, see Using a Configuration File to Define the Metadata.
sasSpawner Attribute Definitions | ||||
---|---|---|---|---|
Attribute Name | Required/ Optional |
Server Type | Definition | |
description In IT Administrator:: Description |
Optional | IOM Bridge | Text to summarize why this object definition exists. This attribute is not used by the spawner. | |
objectClass In IT Administrator: N/A |
Required | IOM Bridge | The object class identifier. For sasSpawner objects, this is always
sasSpawner . If you use IT Administrator, this identifier is assigned automatically. |
|
sasDomainName In IT Administrator: Connections Domain |
Optional | IOM Bridge | The security domain in which the sasSpawner definition participates. The spawner definition must have the same domain name as the server with which it connects. The spawner uses the domain name, along with the machine name and logical name, to determine which server(s) it services. The lack of a domain is considered a domain; therefore, if the spawner definition has no domain name, it will be associated only with servers that have no domain name. | |
sasEncryptionModulesPath In IT Administrator: Encryption Modules Path |
Optional | IOM Bridge (except OS/390) | The path where the encryption modules reside. See SAS/SECURE for more information regarding the available encryption algorithms. On Windows NT, when this attribute is omitted, the spawner queries the registry for the path in which the client SAS/SECURE libraries were installed. | |
sasLogFile In IT Administrator: Logging Log File |
Optional | IOM Bridge | A fully qualified path to the file in which spawner activity is to be logged. Paths with blanks must be in quotation marks. On Windows, paths with embedded blanks must be in double quotation marks. On OS/390, filenames are specified similar to //dsn:myid.objspawn.log for MVS and //hfs:filename.ext for OpenEdition files. | |
sasLogicalName In IT Administrator: Logical Names |
Optional | IOM Bridge | The logical names associated with this sasSpawner definition. When a spawner receives a request to start a SAS session, it looks for servers in its own domain and on its own machine that have the same logical name as the spawner. If logical names are specified, then the spawner supports only those sasServer instances whose logical names are a subset of the logical names defined here. If you are using a configuration file instead of LDAP, specify each logical name as a separate attribute and value pair. |
|
sasLUName In IT Administrator: OS/390 OS/390 Logical Unit Name |
Optional | IOM Bridge (OS/390 only) | The Logical Unit Name for this spawner instance. | |
sasMachineDNSName In IT Administrator: Machines |
Required | IOM Bridge | The DNS name(s) and IP address(es) for the machine(s) on which this spawner definition may
execute. Multiple values can be assigned to this attribute.
The machine name must be the official network name (for example, machine.corp.com). The string localhost can be used to signify the host on which the spawner is executing. |
|
sasMasterPort In IT Administrator: Connections Master Port |
Optional | IOM Bridge | The port that dependent spawners are to use to connect to this spawner instance. If your configuration includes dependent spawners, you must specify either sasMasterPort or sasMasterService. For more information, see Configuring a Dependent Spawner. | |
sasMasterService In IT Administrator: Connections Master Service |
Optional | IOM Bridge | The service that dependent spawners are to use to connect to this spawner instance. If your configuration includes dependent spawners, you must specify either sasMasterPort or sasMasterService. For more information, see Configuring a Dependent Spawner. | |
sasNetEncrKey In IT Administrator: Encryption Key Length |
Optional | IOM Bridge | A numeric value (0, 40, or 128) that specifies the encryption key length. See SAS/SECURE for more information regarding this attribute. | |
sasNetMac In IT Administrator: Encryption Enable MAC Encryption |
Optional | IOM Bridge | A boolean value (true or false) that specifies whether to use Message Authentication Code (MAC) encoding. MAC is the equivalent of a checksum that is used to ensure that the original message has not been modified. MAC integrity checking adds an extra 16 bytes to RC4 encrypted messages and an extra 24 bytes to RC2, DES, and TripleDES encrypted messages. See SAS/SECURE for more information regarding this attribute. | |
sasOperatorPassword In IT Administrator: Connections Operator Password |
Optional | IOM Bridge | The password that an operator must enter to connect to the spawner in order to perform administration tasks. The default password is sasobjspawn. | |
sasOperatorPort In IT Administrator: Connections Operator Port |
Optional | IOM Bridge | The port on which to connect to the spawner in order to perform administration tasks (such as checking status). If neither sasOperatorPort nor sasOperatorService is specified, the service name sasobjoper is used as the sasOperatorService. The spawner will not start without an Administrator listen port or service. | |
sasOperatorService In IT Administrator: Connections Operator Service |
Optional | IOM Bridge | The service in which to connect to the spawner in order to perform administration tasks. If neither sasOperatorPort nor sasOperatorService is specified, the service name sasobjoper is used as the sasOperatorService. The spawner will not start without an Administrator listen port or service. | |
sasSpawnercn In IT Administrator: Name |
Required | IOM Bridge | The unique name for this sasSpawner object. When specified at spawner invocation, its value identifies which sasSpawner definition to use. | |
sasUUIDNode In IT Administrator: Connections UUID Node |
Optional | IOM Bridge | The 12-character string that represents this spawner's node portion of its generated UUIDs. See the section titled Request a Universally Unique Identifier (UUIDGEND) for more information regarding UUID generation by the spawner. | |
sasUUIDPort In IT Administrator: Connections UUID Port |
Optional | IOM Bridge | The port on which to connect to request UUID generation. | |
sasUUIDService In IT Administrator: Connections UUID Service |
Optional | IOM Bridge | The service on which to connect to request UUID generation. | |
sasVerbose In IT Administrator: Logging Verbose |
Optional | IOM Bridge | When present, this attribute causes the spawner to record more details in the log file (sasLogFile or slf). |
Administering SAS Servers |