 |
|
| System Options for SAS Application Server Components |
OBJECTSERVERPARMS System Option
Specifies startup parameters for SAS Integrated Object Model (IOM) servers.
| Valid in: | configuration file, SAS invocation, metadata |
| Category: | Environment control: Initialization and operation |
| PROC OPTIONS GROUP= | EXECMODES (internal) |
| Applies to these servers: | workspace, stored process, OLAP, metadata |
| See: | OBJECTSERVER System Option |
| Syntax | |
| Syntax Description | |
| Details | |
| CLASSFACTORY | |
| CLIENTENCRYPTIONLEVEL | |
| DNSMATCH | |
| NOMETAAUTOINIT | |
| PORT | |
| PROTOCOL | |
| SERVER | |
| SERVICE | |
| TIMEOUTSECONDS | |
| TRUSTSASPEER | |
| Example | |
| See Also |
Syntax |
| -objectserverparms "parameter-1, ... , parameter-n" |
Syntax Description
- parameter
-
The following table summarizes the valid parameters and where they can be used:
| Details |
All object server parameters are applicable on the command line that starts the server:
-
In configuration files on z/OS, do not precede system options with a hyphen. Also, an equal sign must precede the first parameter that follows the OBJECTSERVERPARMS keyword. For example:
objectserver objectserverparms="cel=credentials protocol=bridge port=8561"
-
For servers that are started by the object spawner, the object server parameters come from your server definition in the SAS Metadata Repository. (The server definition is located under the Server Manager plug-in of SAS Management Console. In the server definition, select the Options tab to locate the Object Server Parameters field).
-
For servers that are not spawned (such as those that are run from command scripts or those that are run as services or daemons) you use the sas -objectserver -objectserverparms "parameters" invocation to specify the object server parameters on the command line.
To simplify the command that is needed to invoke an IOM server, the server start-up sequence by default connects back to the metadata server in order to fetch additional information, including object server parameters. You can fetch object server parameters from metadata as follows:
-
When you start the server with a script, some object server parameters cannot be obtained from the metadata. (In the preceding table, only those parameters that are designated as "Metadata" in the "Valid In" column can be stored in the metadata.)
-
When you start the server with a spawner, all object server parameters can be obtained from the metadata.
-
Certain object server parameters are automatically added by the object spawner when it starts workspace and stored process servers. Therefore, the following parameters should not be stored in metadata for workspace and stored process servers: CLASSFACTORY, CLIENTENCRYPTIONLEVEL, PORT, PROTOCOL, SERVER, and SERVICE.
Note: Object server parameters that are specified on the command line
always override object server parameters obtained from a SAS metadata repository. ![[cautionend]](../../../../common/63294/HTML/default/images/cautend.gif)
| CLASSFACTORY |
By default, an IOM server hosts the Workspace class. If you want to specify an alternate class to expose as the top-level class, use CLASSFACTORY to identify the class to IOM.
When using the SERVER object server parameter, the classfactory does not need to be specified because it is obtained from the logical server definition in the SAS Metadata Repository.
This option is primarily used to start the SAS Metadata Server.
Do not specify this option with spawned servers; it will be supplied automatically by the spawner.
Syntax |
| -objectserverparms "classfactory | clsid = class-identifier" |
-
Valid in: Metadata, Command Line Alias: clsid Values Supported: 36-character class identifier - class-identifier
-
specifies the 36-character class ID number that specifies the type of server to instantiate. (For example, 0217E202-B560-11DB-AD91-001083FF6836 specifies a SAS Metadata Server). An IOM server exposes one top-level class through its class identifier.
| CLIENTENCRYPTIONLEVEL |
The CLIENTENCRYPTIONLEVEL parameter specifies the degree of encryption for the IOM server to use when making outbound calls. This option is used only by the bridge protocol engine.
Do not specify this option with spawned servers; it will be supplied automatically by the spawner.
Syntax |
| -objectserverparms "clientencryptionlevel | cel = none | credentials | everything" |
-
Valid in: Command Line (only) Alias: cel Values Supported: none, credentials, everything - NONE
-
use no encryption.
- CREDENTIALS
-
(default) encrypt only a user's credentials when establishing a client session.
- EVERYTHING
-
encrypt all data (including a user's credentials) sent during a client session.
| DNSMATCH |
The object spawner replaces all instances of the DNSMATCH value with the local machine name in its list of servers. This option is necessary if your network configuration resolves a single DNS alias to multiple machines that run SAS servers.
For example, you configure SAS OLAP servers on two different machines: n1.my.org and n2.my.org. The DNS alias srv.my.org resolves to both of these machines, so clients can send a request to the alias and a server on one of the two machines will receive it. To support this configuration, specify DNSMATCH=srv.my.org in the server start-up command on each machine.
Note: For workspace servers and stored process servers, this parameter
is provided automatically when you specify the -dnsMatch
object spawner option.
Syntax |
| -objectserverparms "dnsmatch | dns" |
-
Valid in: Command Line (only) Alias: dns Values Supported: Not applicable - DNSMATCH | DNS
-
specifies a DNS alias that will be accepted by the server as a match for the local machine name.
| NOMETAAUTOINIT |
The NOMETAAUTOINIT parameter specifies that the IOM server should not connect back to the SAS Metadata Server during startup in order to obtain additional configuration information such as object server parameters and pre-assigned libraries. In SAS 9.2, IOM servers connect to the metadata server by default (METAAUTOINIT is on). The NOMETAAUTOINIT parameter is applicable only if you have specified your logical server with the SERVER object server parameter. For further details, see Add System Options to the Workspace Server Launch Command.
Syntax |
| -objectserverparms "nometaautoinit | metaautoinit" |
-
Valid in: Metadata, Command Line Alias: Not applicable Values Supported: Not applicable
| PORT |
The PORT parameter specifies the TCP/IP port on which the IOM bridge protocol engine listens for client connections.
Do not specify this option with spawned servers; it will be supplied automatically by the spawner.
Syntax |
| -objectserverparms "port = port-number" |
-
Valid in: Metadata, Command Line Alias: Not applicable Values Supported: TCP/IP numeric value - port-number
-
is a valid TCP/IP port number.
| PROTOCOL |
The PROTOCOL parameter specifies the protocol engines to launch in server mode. Server mode indicates that the protocol engines will listen for client connections. If you specify (com, bridge) then a multi-user server can simultaneously support clients that use different protocols.
Note: COM is not supported on all servers.
Do not specify this option with spawned servers; it will be supplied automatically by the spawner.
Syntax |
| -objectserverparms "protocol = bridge | com | (com, bridge)" |
-
Valid in: Metadata, Command Line Alias: Not applicable Values Supported: bridge, com (com, bridge) - BRIDGE
-
is a protocol engine that you can launch in server mode.
- COM
-
is a protocol engine that you can launch in server mode.
| SERVER |
The SERVER parameter can be used to retrieve many of the OBJECTSERVERPARMS options (including PORT, PROTOCOL, and CLASSFACTORY) from a SAS Metadata Repository.
Do not specify this option with spawned servers; it will be supplied automatically by the spawner.
Syntax |
| -objectserverparms "server = 'logical-server-name' | 'omsobj:LogicalServer/object-ID'" |
-
Valid in: Command Line (only) Alias: Not applicable Values Supported: 'Logical server name, omsobj:LogicalServer/object-ID' - 'logical-server-name'
-
the logical server name for the IOM run-time and server application to use to locate configuration information in a SAS Metadata Repository. Enclose in single quotation marks, as shown in this example: SERVER='sasapp - Logical OLAP Server'.
- 'omsobj:LogicalServer/object-ID'
-
the object definition ID that is generated for the logical server for the IOM run-time and server application to use to locate configuration information in a SAS Metadata Repository. Enclose in single quotation marks.
To determine the generated object ID, in SAS Management Console, select the logical server definition, and then select File
![[arrow]](../../../../common/63294/HTML/default/images/arrow.gif)
Properties from the menu bar. Use
the Uniform Resource Identifier (URI) formatted value that is shown in the
ID field as the argument for the object ID, as shown in this example: SERVER='omsobj:LogicalServer/01234567.01234567'.
| SERVICE |
The SERVICE parameter specifies the TCP service name for the port that the IOM Bridge protocol engine will use to listen for connections from clients.
Do not specify this option with spawned servers; it will be supplied automatically by the spawner.
Syntax |
| -objectserverparms "service = service-name" |
-
Valid in: Metadata, Command Line Alias: Not applicable Values Supported: TCP service name - service-name
-
a valid TCP service name (for example, from /etc/services on a UNIX system).
| TIMEOUTSECONDS |
The TIMEOUTSECONDS parameter specifies the time interval that an OLAP server or a stored process server waits before it stops a client process and cleans up the server run-time environment context.
Note: The TIMEOUTSECONDS parameter does not apply to the workspace servers or to
the sas metadata server.
Syntax |
| -objectserverparms "timeoutseconds = seconds" |
-
Valid in: Metadata, Command Line Alias: Not applicable Values Supported: numeric value that represents seconds - seconds
-
the interval in seconds that an OLAP server or a stored process server waits before stopping a client process. seconds is a number that is equal to or greater than five.
| TRUSTSASPEER |
The TRUSTSASPEER parameter enables SAS peer sessions from IOM servers to connect as trusted peer sessions. If you specify a blank or empty file, then you disable trusted peer support.
Note: This parameter is valid only for the command that starts the
SAS Metadata Server.
For more information, see Trusted Peer Connections in the SAS Intelligence Platform: Security Administration Guide.
Syntax |
| -objectserverparms "trustaspeer | tsaspeer = pathname" |
-
Valid in: Metadata, Command Line Alias: tsaspeer Values Supported: XML file - pathname
-
is a pathname to a file containing XML that describes the allowable trusted peer connections, the users who can connect, and the machines from where the connections can be established.
Enclose the pathname in single quotation marks if there is a space in the path. For example:
'C:\SAS 9.2\FoundationServers\Lev1\SASMain\MetadataServer\trustedPeers.xml'
| Example |
This example shows how the OBJECTSERVERPARMS system option can be used in a configuration file that is used to start the metadata server:
-objectserver -objectserverparms "cel=credentials protocol=bridge port=8561 classfactory= 0217E202-B560-11DB-AD91-001083FF6836 trustsaspeer=C:\SAS\ FoundationServers\Lev1\SASMain\MetadataServer\trustedPeers.xml"
Note: In configuration files on z/OS, do not precede system options with a hyphen. Also, an equal sign must precede the first parameter that follows the OBJECTSERVERPARMS keyword. For example:
objectserver objectserverparms="cel=credentials protocol=bridge port=8561"
| See Also |
|
System Options: |
|
|
Copyright © 2010 by SAS Institute Inc., Cary, NC, USA. All rights reserved.