| Siebel CRM System Administration Guide Siebel 2018 E24823-01 |
|
 Previous |
 Next |
View PDF |
| Siebel CRM System Administration Guide Siebel 2018 E24823-01 |
|
Previous |
Next |
View PDF |
The Siebel application uses parameter values based on the level at which they are set. Parameter values at the highest levels are inherited by the same parameter at lower levels. For example, a parameter set at the enterprise level contains the same value for the same parameter at the server and component level, unless the value is overridden at a lower level. If a change is made to that parameter at the enterprise level, then this value is inherited down to the lower levels. Table 4-1 lists the parameter-setting levels in order from highest to lowest.
If a parameter value is set at a lower level, and a new change is made to the same parameter at a higher level, then the new change does not inherit down to the lower level unless the override is deleted at that lower level.
|
Note: Do not set lower-level parameters to a blank or empty value. To negate a parameter value, use the appropriatedelete parameter override command. |
Once you set a parameter at a lower level, this value creates an entry in the Siebel Gateway registry and, from that time on, you must maintain it at this level. That is, any further changes that are to affect this level must be made at this level unless you delete the override.
|
Note: Querying for a specific parameter in either the Parameter field or the Alias field returns matches from both fields. For example, querying in the Parameter field by using the expression File* returns the result Siebel File System, because the parameter's alias is FileSystem. |
Table 4-1 lists the parameter-setting levels in order, from highest to lowest. Named subsystem parameters can apply to entities at different levels.
Table 4-1 Hierarchy of System Parameters
| Level | System Parameter | Comment |
|---|---|---|
|
1 |
Default from library |
Default, hard-coded values from the library. Does not apply for passwords and other parameters that require user-supplied values. |
|
2 |
Siebel Enterprise parameter |
For more information, see "About Siebel Enterprise Server Parameters" and "Configuring Siebel Enterprise Parameters". |
|
3 |
Siebel Server parameter |
For more information, see "About Siebel Server Parameters" and "Configuring Siebel Server Parameters". |
|
4 |
Siebel Server component parameter, enterprise level |
Enterprise-level Siebel Server component parameters are set by configuring component definition parameters. For more information, see "Configuring Siebel Enterprise Component Definition Parameters" and "About Siebel Server Component Definitions". |
|
5 |
Siebel Server component parameter, server level |
For more information, see "About Siebel Component Parameters" and "Configuring Siebel Server Component Parameters". |
|
6 |
Siebel Server component task parameter |
Configure these parameters mainly for batch tasks or when invoking tasks from a script or a workflow process. For more information, see "About Task Parameters", "Starting a Component Job", and "Configuring Siebel Server Task Dynamic Parameters". |
This topic contains the following information:
Related Topics
"Deleting System Parameter Overrides"
"Parameter Management Commands"
Parameters that affect or modify advanced product functionality are, by default, hidden from the Server Manager GUI.
To make advanced or hidden parameters visible, click Advanced or Hidden on the parameter views for the enterprise, Siebel Server, or components. To restore the default view, click Reset.
Related Topics
The Server Manager GUI provides parameter availability status for system parameters at the following levels: enterprise, Siebel Server, component definition, component, task, and session. Certain parameters become available or effective only after specific Siebel Server operations are performed. Review the parameter availability status options in Table 4-2 to determine the type of action necessary to make your parameter change effective.
Table 4-2 Parameter Availability Status Options
| Availability Status | Description |
|---|---|
|
Immediately |
These parameters are effective immediately and require no further Siebel Server operations. These parameter are also known as dynamic parameters. All other parameters are static parameters. |
|
At Next Task |
These parameters are effective at the start of the next task. |
|
At Component Restart |
These parameters require a restart of the server component before they become effective. |
|
At Server Restart |
These parameters require a restart of the Siebel Server before they become effective. |
|
Require Reconfiguration |
These parameters require the component definition to be reconfigured before they become effective. |
Related Topics
"Reconfiguring Siebel Server Component Definitions"
"Administering Siebel Servers"
Enterprise parameters set the attributes of the entire Siebel Enterprise Server. These parameters are initially set when the Siebel Enterprise Server is initially configured by using the Siebel Management Console. Each Siebel Server installed and configured in the Siebel Enterprise Server inherits these enterprise parameters. Many of the parameters that can be set at the enterprise level are server or named subsystem parameters, which can then be modified or overridden on each Siebel Server.
For example, if a Siebel environment contains multiple Siebel Servers, and the component parameters Maximum MT Servers (alias MaxMTServers) and Maximum Tasks (alias MaxTasks) are set at the enterprise level for a specific component with the values 5 and 100, respectively, then, unless override values are in effect, each Siebel Server in the environment runs this specific component with a maximum of 5 server processes (MaxMTServers) and a maximum 100 tasks (MaxTasks). The values 100 and 5 do not apply to the enterprise as a whole, but provide values for each instance of the component on an individual Siebel Server.
|
Note: Setting parameters at the enterprise level sets generic parameters used by all of the Siebel Servers and components across the enterprise. To set component-specific parameters for all components across an enterprise, configure the component definition parameters. |
Related Topics
Siebel Server parameters set the attributes of each Siebel Server. These parameters are either used by the Siebel Server for its own operation, such as Shutdown Wait Time, or inherited by the components assigned to that Siebel Server.
The entire set of parameters for a given Siebel Server is a combination of the enterprise parameters inherited from the enterprise, and those specified when the Siebel Server is initially configured. Either type can be modified for any given Siebel Server.
If Siebel Server-level parameters are changed, then any future configurations to Siebel Enterprise Server-level parameters do not cascade down to the Siebel Server parameter level for that particular parameter. To restore this functionality, see the description of the appropriate delete parameter override command.
New values for Siebel Server-level dynamic parameters, which are parameters marked as Effective Immediately, apply to subsequently started tasks, unless these values are overridden at a lower level.
New values for static parameters, which are parameters not marked Effective Immediately, do not apply to subsequently started tasks until you stop and restart the Siebel Server system service. For both fixed and static parameters, the Server Manager views continue to show both the current value and the value upon Siebel Server restart.
Related Topics
Siebel component parameters set the attributes specific to a particular component type. These parameters are set initially when the defined component is created. For each component assigned to a Siebel Server, the component inherits the Siebel Enterprise and Siebel Server parameters applicable to that Siebel Server. The three types of parameters (except those marked Fixed when the defined component was created) can be overridden for the particular component on that Siebel Server.
If component-level parameters are changed, then any future configurations to Siebel Enterprise Server or Siebel Server-level parameters do not cascade down to the component parameter level for that particular parameter. To restore this functionality, see the description of the appropriate delete parameter override command.
New values for component-level dynamic parameters, which are parameters marked as Effective Immediately, apply to subsequently started tasks, unless these values are overridden at a lower level.
New values for static parameters (that is, parameters that are not marked Effective Immediately) do not apply to subsequently started tasks until you stop and restart the Siebel Server system service. For both fixed and static parameters, the Siebel Server Manager views continue to show both the current value and the value upon Siebel Server restart.
Related Topics
Task parameters control the execution of a specific task. These parameters consist of Siebel Enterprise, Siebel Server, and component-level parameters for the Siebel Server and the component for which the task is being executed, as well as task-specific parameters specified when you start a task. Task parameters are set or overridden when you first start the task. After a task is running, only dynamic parameters can be changed.
|
Note: The delay before the new parameter value is picked up and used by a running task varies by component, depending on how often the tasks for a particular component recheck their parameter values. |
Related Topics
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. 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 4-1. 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"
