Siebel Server Administration Guide > Application Object Manager Administration > Siebel Application Object Manager Parameters >

Named Subsystems


The Application Object Manager can maintain several different values for a particular parameter using named subsystems. The desired value used by the application object manager depends on the context. In other words, an Application Object Manager has several groups of parameters with context-dependent values: in context 1, parameters PA and PB have values V1A and V1B, respectively, whereas in context 2, the same parameters have values V2A and V2B. For example, the Application Object Manager uses different configuration information that depends on the datasource on which the business components are based. Which datasource, and datasource configuration, is used for a particular business component is context information that can come from several different sources. A business component can specify a datasource in the compiled repository file, or a client can select a datasource from several available datasources. Configuration information like the TableOwner or Database Case Sensitivity have different values depending on the datasource selected.

The parameters that have a context dependency are defined as named subsystem parameters. The component code using these named subsystems can request the subsystem parameter values using a context name and receives the value belonging to the named instance.

Table 15 lists the Named Subsystems that contain parameters used by Application Object Managers.

Table 15. Named Subsystems Used by Application Object Managers 
Named Subsystem
Alias
Type
Description
DataMart Datasource
DataMart
InfraDatasources
Datamart datasource used by AppObjMgr components
Gateway Datasource
GatewayDataSrc
InfraDatasources
Gateway datasource used by AppObjMgr components
Object Manager Cache
ObjMgrCache
InfraObjMgrCache
Object Manager cache parameters
Server Datasource
ServerDataSrc
InfraDatasources
Server datasource used by AppObjMgr components

Table 16 lists a sample of named subsystem parameters, their respective named subsystems, and a description.

Table 16. Selection of Named Subsystem Parameters
Parameter Alias
Named Subsystem
Data Type
Description
DSConnectString
GatewayDataSrc
String
Specifies the host name of the Siebel Gateway. The value $(GatewayAddress) for the parameter ConnectString of the GatewayDataSrc section of the Application Object Manager's configuration file is replaced at runtime with the value for the named subsystem parameter DSConnectString. An incorrect setting for DSConnectString results in Server Administration not being accessible from the standard Web client.
DSConnectString
ServerDataSrc
String
Specifies the database connection information. On SQL Server and DB2, this information is the ODBC Datasource Name; on Oracle (native) this information is the service name from tnsnames.ora.
DSFileSystem
ServerDataSrc
String
Set this parameter to *FSM* to allow the use of the File System Manager server component for standard Web clients.
DSMaxCursorSize
ServerDataSrc, GatewayDataSr, or DataMart
Integer
The configuration file parameter MaxCursorSize is set for the application object manager component using the named subsystem parameter DSMaxCursorSize. The applicable subsystem used by the application object manager corresponds to the component parameter OM - Data Source. This parameter is only valid with IBM DB2 UDB for OS/390 and z/OS. See Siebel Web Client Administration Guide for further details on MaxCursorSize.
DSPreFetchSize
ServerDataSrc, GatewayDataSr, or DataMart
Integer
The configuration file parameter PreFetchSize is set for the application object manager component using the named subsystem parameter DSPreFetchSize. This parameter is only valid with IBM DB2 UDB for OS/390 and z/OS. See Siebel Web Client Administration Guide for further details on PreFetchSize.
DSEnterpriseServer
ServerDataSrc, GatewayDataSr
String
Specifies name of Siebel Enterprise Server used by various named subsystems. The value in the application object manager's configuration file is replaced at runtime with the value set for the named subsystem.
DSRequestServer
ServerDataSrc
String
Specifies where asynchronous calls are redirected, for example when using Interactive Assignment. Set this value to the logical name of the Siebel Server, not the machine name. The default value is null. If Resonate is used, this value must be set to null.

You can create and modify Named Subsystems using both the Siebel Server Manager GUI and command-line interfaces. For information on configuring Named Subsystems, see Configuring Named Subsystems. To configure Named Subsystems using the Siebel Server Manager command-line interface, see Named Subsystem Management Commands.


 Siebel Server Administration Guide, Version 7.5, Rev. C 
 Published: 18 April 2003