Bookshelf Home | Contents | Index | Search | PDF |
Siebel Server Administration Guide > Siebel Enterprise Server Architecture > Siebel Server Components >
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 5, Table 6, and Table 7 define the shell types created in various scenarios.
Table 5. Interactive Mode Components Multithreaded Object Manager Based Shell False False siebsess True False siebmtsh True True siebmtshmw
Table 7. Background Mode Components Object Manager Based Shell (Created at Bootstrap) Shell (Created at Runtime) False siebproc siebsh True siebprocmw siebshmwExamples of Siebel Server shells:
- A background mode component that is not object manager based is brought up in a siebproc shell. For example, Transaction Processor (TxnProc).
- An interactive component that is multithreaded and not object manager-based is brought up in a siebmtsh shell. For example, Server Request Processor (SRProc).
- A multithreaded, object manager-based component is brought up in a siebmtshmw shell. For example, Call Center Object Manager (SCCObjMgr).
Parameters Controlling Number of Shells
The following parameters, defined for each multithreaded batch and interactive mode component, control the number of shells that start up:
- MaxMTServers
- MinMTServers
- MaxTasks
- DfltTasks
See Parameters and Determining Application Object Manager Parameter Values 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 Viewing Siebel Server Event Logs for details on viewing Siebel Server log files.
Bookshelf Home | Contents | Index | Search | PDF |
Siebel Server Administration Guide, Version 7.5, Rev. C Published: 18 April 2003 |