Siebel System Administration Guide > Configuring Siebel Servers >

Checking Your Enterprise and Siebel Server Configurations

One of the main objectives of your enterprise and Siebel Server configurations is to make sure server components are properly configured and ready to execute tasks. Check the following bullet list to make sure you meet the necessary configuration conditions for this objective:

• The component group that contains the server component member is enabled at the enterprise level. For information on this procedure, see Enabling Component Groups on a Siebel Enterprise Server.
• The component group that contains the server component is enabled at the Siebel Server level. For information on this procedure, see Enabling Component Groups on a Siebel Server.
• The component definition is enabled. The component definition defines the configured component for the enterprise and all its Siebel Servers. For information on this procedure, see Enabling a Siebel Server Component Definition.
• The server component is enabled at the Siebel Server level. For information on this procedure, see Enabling Components on a Siebel Server.

If the previously listed conditions are true, the Siebel Server allocates resources (space in shared memory and a public port) for the server component to use when the Siebel Server starts.

Additionally, check the following run-time conditions:

• The component group that contains the server component must be online at the server level. For information on this procedure, see Setting Siebel Server Component Groups Online.
• The server component must be online at the server level. For information on this procedure, see Setting Siebel Server Components Online.

If the previously listed conditions are true, the Siebel Server marks the server component ready (available) for starting new tasks and performs any additional steps necessary, for example, the starting of shells if the server component is multithreaded. The number of multithreaded shells started is governed by the parameter Min MT Servers (alias MinMTServers). If the server component is a background mode component, it starts the background number of tasks governed by the parameter Default Tasks (alias DfltTasks).