Bookshelf Home | Contents | Index | PDF |
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:
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. 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, 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 manually start, see About Starting Siebel Server Components. Examples of Siebel Server shells:
Parameters Controlling Number of ShellsThe following parameters configure shell (process) startup for interactive, batch, and background mode components:
See Siebel Enterprise, Server, and Component 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 Siebel System Monitoring and Diagnostics Guide for details on viewing Siebel Server log files. |
Siebel System Administration Guide | Copyright © 2010, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |