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/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 an appropriate shell based on the component mode (interactive, batch, or background) and whether the component is object manager-based, multithreaded, or both. Table 4, Table 5, and Table 6 define the shell types created in various scenarios.

NOTE:  To conserve system resources and minimize the number of processes started on the Siebel Server, disable components and component groups that you do not plan to run. For information on disabling components and component groups, see About Enabled and Disabled Component Groups and About Enabling and Disabling Siebel Server Components.

Examples of Siebel Server shells:

• 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 (alias SCCObjMgr).

Parameters Controlling 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)

See Parameters and About AOM Parameters in Server Manager for further information and details on configuring these parameters.

To review information on the shells forked by the Siebel Server, access the Siebel Server log file. See System Monitoring and Diagnostics Guide for Siebel Business Applications for details on viewing Siebel Server log files.