|
|
Administering SAS Servers |
|
The sasDependentSpawner object class configures a dependent spawner. The sasDependentSpawner object class is defined using the attributes listed in the following table. For each attribute, the table shows:
The name that identifies the attribute on the LDAP server (or in the configuration file). Under each attribute 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: Dependent spawners are used only in IOM Bridge configurations. Therefore, IOM Bridge is listed as the server type for each attribute.
A definition of the attribute.
For step-by-step instructions on defining the metadata for a dependent spawner, refer to Configuring a Dependent Spawner.
| sasDependentSpawner 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 sasDependentSpawner objects, this is
always sasDependentSpawner. If you use IT Administrator, this identifier is assigned automatically. |
|
| sasCommand In IT Administrator: N/A |
Optional |
IOM Bridge (except OS/390) |
The command used to launch the object server. If specified, this command overrides the sasCommand specified in the sasServer definition. Paths with blanks must be in quotation marks. On Windows, paths with embedded blanks must be in double quotation marks. | |
| sasDependentSpawnercn In IT Administrator: Name |
Required | IOM Bridge | The unique name for this sasDependentSpawner object. When specified at dependent spawner invocation, its value identifies which sasDependentSpawner definition to use. | |
| sasDomainName In IT Administrator: Connections 
Domain |
Optional | IOM Bridge | The security domain in which the sasDependentSpawner definition participates. sasDomainName and sasLogicalName are used to acquire the sasServer definitions that the dependent spawner services. If the dependent spawner is to support multiple object servers and master spawners, they must all have the same domain name. If the server(s) and master spawner(s) do not have domain name attribute(s), do not define a domain name attribute for the dependent spawner. | |
| 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 the dependent spawner's 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 sasDependent Spawner definition. sasDomainName and sasLogicalName are used to acquire the
sasServer definitions that the dependent spawner services. If a server or master spawner has more than one logical name, specify at least one of the names. If the dependent spawner is to support multiple servers and master spawners, specify all necessary logical names. 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 dependent 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 dependent spawner instance may execute. Multiple values can be assigned to this attribute. The machine name must be entered as a fully qualified domain name (for example, machine.corp.com). The string localhost can be used to signify the host on which the dependent spawner is executing. The host(s) may or may not be the same machine(s) on which the master spawner(s) and server(s) reside. |
|
| 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 dependent 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 dependent 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 dependent 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 dependent spawner in order to perform administration tasks. If neither sasOperatorPort nor sasOperatorService is specified, the service name sasobjoper is used as the sasOperatorService. The dependent spawner will not start without an Administrator listen port or service. | |
| sasPLUName In IT Administrator: Logging
Verbose |
Optional) | IOM Bridge (OS 390 only |
The Partner Logical Unit name that the dependent spawner is to use (in conjunction with the sasTpName) to launch the object server. If specified, this sasPLUName overrides the sasTpName specified in the sasServer definition. | |
| sasTpName In IT Administrator: N/A |
Optional | IOM Bridge (OS 390 only) |
The Transaction Program name that the dependent spawner is to use (in conjunction with the sasPLUName) to launch the object server. If specified, this sasTpName overrides the sasTpName specified in the sasServer definition. | |
| sasVerbose In IT Administrator: N/A |
Optional | IOM Bridge | When present, this attribute causes the dependent spawner to record more details in the log file (sasLogFile or slf). | |
|
|
Administering SAS Servers |
|