Share

Siebel Server Component Processes (Shells)

The Siebel Server runs each component in its own separate process (or shell). These shells provide 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. 

 

 



Siebel Server forks an appropriate shell based on below factors:

 Ø  Component mode (interactive, batch  or background)  

Ø  Component is object manager-based or not  

Ø  Component is multithreaded or not

Below Table is list of process created at component startup (bootstrap) and at runtime.

Component Mode

Multithreaded

Object Manager Based

Shell (Created at Bootstrap)

Shell (Created at Run Time)

Interactive

TRUE

TRUE

NA

siebmtshmw

Interactive

TRUE

FALSE

NA

siebmtsh

Interactive

FALSE

FALSE

NA

siebsess

Batch

TRUE

TRUE

siebmtshmw

siebmtshmw

Batch

TRUE

FALSE

siebmtsh

siebmtsh

Batch

FALSE

TRUE

siebprocmw

siebshmw

Batch

FALSE

FALSE

siebproc

siebsh

Background

TRUE

FALSE

siebproc

siebsh

Background

TRUE

TRUE

siebprocmw

siebshmw

 F  Note 1: Background mode components run as multithreaded process only. 

F  Note 2: Interactive mode components which are object manager based run as multithreaded process only.

Examples of Siebel Server shell:

ü  A multithreaded, object manager-based component is brought up in a siebmtshmw shell. For example, Call Center Object Manager.

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)

2 comments on “Siebel Server Component Processes (Shells)”

  1. Li Huang Reply

    Thanks for the article. Really helpfull.
    Can you plz explain the modes Components runs ?

    Thanks,
    Li Huang

  2. Ashish Kumar Ashish Kumar Reply

    Components run in one of several modes:

    Interactive mode. Interactive components start tasks automatically in response to user requests. The tasks end when the user ends the session. Examples of interactive mode tasks are the Synchronization Manager and all Application Object Managers (AOMs).

    Background mode. Background components handle background processing tasks. Typically, background tasks are called by interactive mode tasks. Background tasks run until explicitly shut down. Examples of background tasks are Transaction Router and Workflow Monitor Agent.

    Batch mode. Batch mode components handle processing of asynchronous work requests. When the task is complete, the component exits. Examples of batch mode components are Database Extract and Enterprise Integration Manager (EIM).

Leave A Reply

Your email address will not be published. Required fields are marked *

error: Content is protected !!