Siebel System Administration Guide > Configuring Siebel Servers > About Siebel System Parameters >

About Named Subsystem Parameters

Named subsystems are groupings of defined enterprise parameters, which allow the Siebel Server to manage multiple sets of parameter values. Like other server constructs, such as component definitions, server parameters, enterprise parameters, and component parameters, they are stored in the Siebel Gateway Name Server. When a Siebel Server starts, it retrieves this information and creates a copy of the named subsystems in shared memory. You can create named subsystems by using the Server Manager GUI or command-line interface.

The Server Manager GUI also refers to named subsytems as enterprise profiles. You create new named subsystems in the Profile Configuration subview of the Enterprises view in the Administration - Server Configuration screen.

By using named subsystems, the Application Object Manager can maintain several different values for a particular parameter. The 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 data source on which the business components are based. Which data source, and data source configuration, is used for a particular business component is context information that can come from several different sources. A business component can specify a data source in the compiled repository file, or a client can select a data source from several available data sources. Configuration information like database case sensitivity can have different values depending on the data source.

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

Named subsystem parameters are set at the enterprise level only. Parameter names associated with a data source usually start with DS so they do not conflict with the other parameters from the levels 2 to 6 in Table 17. Named subsystem parameters have a higher priority than the default parameter settings that are hard-coded in their library.

Where they apply, named subsystem parameters override parameters set at the Siebel Enterprise, Siebel Server, and server component levels.

Related Topics

About Siebel System Parameters

Creating Siebel Enterprise Server Named Subsystems

Configuring Siebel Enterprise Server Named Subsystem Parameters

Named Subsystem Management Commands