Object Server Parameters

All object server parameters are applicable on the command line that starts the server:

• 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, those that are run as Windows services, or those that are launched by COM), you use the OBJECTSERVERPARMS SAS option to specify the object server parameters on the command line.

To simplify the command that is needed to invoke an IOM server, the server startup sequence can also connect back to the metadata server in order to fetch additional information, including object server parameters. This feature involves use of the SERVER= and METAAUTOINIT object server parameters. See Specifying Metadata Connection Information for details. The object server parameters that can be obtained in this way have the value "Metadata, Command Line" for the "Valid for Script" attribute. These object server parameters can be specified in the server definition in SAS Management Console. In the server definition, select the Options tab to locate the Object Server Parameters field.

Important Note:

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. These parameters have the value "Command Line Only" for the "Valid for Script" attribute. These object server parameters must be specified on the command line.

• When you start the server with a spawner, all object server parameters can be obtained from the metadata (even those that have the value "Command Line Only" for the "Valid for Script" attribute).

Note: Object server parameters that are specified on the command line always override object server parameters obtained from a SAS Metadata Repository.

ANONYMOUSLOGINPOLICY

Specifies whether the server permits any access at all to connections that do not supply a user ID (in programming terms, ones that supply a zero-length user ID).

If you specify "restrict," then the server allows connections that do not have a user ID; however, the client only has restricted access to the IServerStatus interface (used primarily for querying basic server status).

If you specify "deny," then the server completely disallows connections that do not provide a user ID. The default is "restrict." For details about ANONYMOUSLOGINPOLICY, see Setting Up Additional Server Security in the Security section.

APPLEVEL

Specifies the detail level of the trace that is written by the server application (such as the OLAP server, the SAS Metadata Server or the SAS Stored Process Server). The default value if APPLEVEL is omitted (1) enables logging at a level that is suitable for a production server; therefore, this parameter is optional. APPLEVEL=0 disables the application's logging and is discouraged because it suppresses useful diagnostic information. Higher APPLEVEL values can invoke additional tracing. The SAS Metadata Server, for example, defines additional logging levels. For details, see "Administering the SAS Metadata Server Log" in the "Administering the SAS Metadata Server Log and Audit Trail" chapter of the SAS Intelligence Platform: System Administration Guide.

CLASSFACTORY

Specifies the class ID number, which specifies the type of server to instantiate (for example, 2887E7D7-4780-11D4-879F-00C04F38F0DB specifies a SAS Metadata Server). An IOM server exposes one top-level class through its class identifier.

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 the classfactory option to identify the class to IOM.

When using the SERVER= objectserverparms suboption, 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.

CLIENTENCRYPTIONLEVEL

Specifies the degree of encryption to use when making outbound calls. This option is used only by the bridge protocol engine.

DNSMATCH

specifies a DNS alias that will be accepted by the server as a match for the local machine name. In addition, the 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 startup command on each machine.

Note: For Workspace Servers and Stored Process Servers, this parameter is provided automatically when you specify the -dnsMatch spawner option.

IOMLEVEL

Specifies trace level for protocol-independent IOM events, particularly calls and the SAS LOG of workspaces. The default is 0. If IOMLEVEL is set to 1, then the calls that enter and leave the server are traced. This feature can be very helpful for identifying whether a problem arose in a client or in the server. Using IOMLEVEL=1 with the SAS Metadata Server will capture the input and output XML strings for metadata requests. For more information, see "Administering the SAS Metadata Server Log" in the "Administering the SAS Metadata Server Log and Audit Trail" chapter of the SAS Intelligence Platform: System Administration Guide.

For performance reasons, it is recommended that IOMLEVEL=1 be used only when diagnosing problems. Higher values of IOMLEVEL produce traces that are intended only for use by SAS Technical Support. Depending on the calls that are being traced, the JNLSTRMAX and JNLLINEMAX values may need to be increased to prevent truncation of long strings and long lines.

JNLARRELM

Specifies the maximum number of array elements to print out when an IOM array value is traced.

JNLLINEMAX

Specifies the maximum length of a line printed in the IOM server journal.

JNLSTRMAX

Specifies the maximum length of string printed in the IOM server journal. This option can be used to adjust the amount of material included in an IOM trace. A value greater than 500 is recommended.

LOGFILE

Specifies an alternative file for the SAS log for IOM server trace output.

Note: Using this option on a spawned server can prevent multiple servers from running simultaneously because they will all try to open the same log file. It is therefore recommended that this option be used only for specific diagnostic tasks.

Note: The user who starts the server must have execute and write permissions for the log destination path.

METAAUTOINIT | NOMETAAUTOINIT

Specifies whether the IOM server should 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. When METAAUTOINIT is specified, the server uses the provided META* options to connect to the SAS Metadata Server. With NOMETAAUTOINIT, IOM server startup does not connect back to the SAS Metadata Server. The default depends on the type of server. For further details, see Server Startup Command. This option is applicable only if you have specified your logical server with the SERVER= object server parameter.

PELEVEL

Specifies trace protocol engine logic and packets. Level 3 specifies the most verbose output. The default is 0.

PORT

Specifies the value for the bridge protocol engine to use as the port to start listening for client connections. Do not specify this option with spawned servers; it will be supplied automatically by the spawner.

PROTOCOL

Specifies the protocol engines to launch in server mode. Server mode indicates that the protocol engines will listen for client connections. By default, Windows servers use the COM protocol engine and all other servers use the Bridge protocol engine. If you specify (com, bridge) then a multi-user server can simultaneously support clients using different protocols. Do not specify this option with spawned servers; it will be supplied automatically by the spawner.

SERVER

Specifies the logical server name for the IOM run-time and server application to use to locate configuration information in a SAS Metadata Repository. The SERVER= option can be used to retrieve many of the OBJECTSERVERPARMS options (including PORT, PROTOCOL and CLASSFACTORY) from a SAS Metadata Repository. For details, see Specifying Metadata Connection Information.

SERVICE

Specifies the TCP service name (for example, from /etc/services on a UNIX system) 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.

TRUSTSASPEER

Enables SAS peer sessions from IOM servers to connect as trusted peer sessions. If you specify a blank or empty file, any SAS peer session can connect as a trusted peer. If you specify a file that contains a list of trusted domains, SAS peer sessions are only trusted if they belong to a domain that is listed in your trusted peer file. For more information, see Implementing Trusted Authentication Mechanisms.

Note: This parameter is only valid for the command that starts the SAS Metadata Server.

V8ERRORTEXT

Indicates that the MVA components should return Version 8 style error messages instead of the Version 9 XML style error messages.