Siebel System Administration Guide > Siebel Enterprise Server Architecture > About Siebel Server Components >

About Server Component Processes (Shells)

The Siebel Server runs each component in its own separate process (or shell). These shells provide the interface for a component to communicate with shared memory, and use infrastructure facilities for logging, events, networking, and so on.

A shell performs the following actions when it is forked off:

• Initializes the logging and networking facility.
• Determines which component to run. The component is specified as a DLL (personality DLL), which is run by the Siebel Server either as part of the input parameters or as part of a network message.
• Attaches to shared memory.

The Siebel Server forks off an appropriate shell based on the component mode (interactive, batch, or background) and whether the component is object manager-based, multithreaded, or both. The tables in this topic identify the shell types created in various scenarios for interactive-mode, batch-mode, and background-mode components.

NOTE:  To conserve system resources and minimize the number of processes running on the Siebel Server, disable the component groups that you do not plan to run. If you cannot disable a component group because you require components within the group, then you can set other components within the group that you do not require to Manual Start mode. For information about disabling component groups, see About Enabled and Disabled Component Groups. For information about setting a component to start manually, see About Starting Siebel Server Components.

Shell Types for Interactive-Mode Components

Table 6 identifies the shell types created for interactive-mode components.

Shell Types for Batch-Mode Components

Table 7 identifies the shell types created for batch-mode components.

Shell Types for Background-Mode Components

Table 8 identifies the shell types created for background-mode components.

Examples of Shells for Siebel Server Components

The following are examples of shells for Siebel Server components:

• A background component that is not object manager-based is brought up in a siebproc shell. For example, Transaction Processor (alias TxnProc).
• An interactive component that is multithreaded and not object manager-based is brought up in a siebmtsh shell. For example, Server Request Broker (alias SRBroker).
• A multithreaded, object manager-based component is brought up in a siebmtshmw shell. For example, Call Center Object Manager for U.S. English (Call Center Object Manager (ENU), alias SCCObjMgr_enu).

Parameters Controlling the Number of Shells

The following parameters configure shell (process) startup for interactive, batch, and background mode components:

• Maximum MT Servers (alias MaxMTServers)
• Minimum MT Servers (alias MinMTServers)
• Maximum Tasks (alias MaxTasks)
• Default Tasks (alias DfltTasks)

For more information about configuring these parameters, see Siebel Enterprise, Server, and Component Parameters and Application Object Manager Parameters in Server Manager.

To review information about the shells forked off by the Siebel Server, access the Siebel Server log file. For information about viewing Siebel Server log files, see Siebel System Monitoring and Diagnostics Guide.