Siebel System Monitoring and Diagnostics Guide > Monitoring Siebel Server Run-Time Operations >

About Siebel Server Component States

A Siebel Server component might be in one of the following states: Starting Up, Online, Running, Offline, Shutting Down, Shutdown, or Unavailable.

The Siebel Server component state is dependent on the assignment state of the component group to which it belongs; only Siebel Server components within assigned component groups when the Siebel Server was started can be Running or Online:

• Starting Up. Indicates that the Siebel Server component is in the process of starting up. When this process is complete, the state changes to Online. When a new task is started for the component, the component state changes to Starting Up during the initialization phase and then to Running.
• Online. Indicates that tasks are currently not running for the Siebel Server component, but new tasks might be started through the Siebel Server Manager (or in response to client requests, for interactive-mode components). When the Siebel Server starts, components for which processes are not started by default are online.
• Running. Indicates that tasks are currently running for the Siebel Server component on the Siebel Server, and new tasks are allowed to start (up to the value of the Maximum Tasks parameter for the component). When the Siebel Server starts up, background-mode components for which processes are started by default (components with a Default Tasks parameter set to a nonzero value) start.
• Offline. Indicates that new tasks might not be started for the component, though current running tasks can continue running (for background-mode components) or run to completion (for batch-mode and interactive-mode components).

  You might want to disable an individual component to perform a system maintenance operation outside of the Siebel Server. For example, you might disable the Synchronization Manager component to do a file system reorganization on the docking subdirectory.

  To minimize the number of multithreaded processes started on the Siebel Server, you might want to disable components that you do not plan to run.

  You might also want to disable components due to database licenses. If you have exceeded the maximum licensed connections for your database, then you might want to disable the Siebel Server components that you plan not to use. You must only disable components for which you do not plan to run tasks across the entire enterprise. Setting the Min MT Servers parameter to 0 for multithreaded Siebel Server components renders the server component unable to run tasks.

  An offline component might be set to Online (or Started, if there are still tasks running for the offline component) or Shutdown, in which case, any running tasks are stopped as cleanly as possible.

• Shutting Down. Indicates that the Siebel Server component is in the process of shutting down. When this process is complete, the state changes to Shutdown.
• Shutdown. Indicates that processes are not running for the component and new tasks might not be started. Each task running when the component shuts down is stopped as soon as possible. Components are set to Shutdown when the Siebel Server shuts down, with the exception of the Siebel Server Manager component, which remains Online to perform administrative commands executed by the Siebel Server Manager. Background-mode components that are set to Shutdown but have a Default Tasks parameter set to a nonzero value might be set to Online or Started.
• Unavailable. Indicates that processes are not running for the component when a Siebel Server process is running. Multithreaded Siebel Server components change to an Unavailable component state when the Min MT Servers parameter is set to a value greater than 0 and no Siebel Server processes are actually running for that component. In this case, the Siebel Server component might exit with an error and become unavailable because it failed to initialize. Siebel Server components might also go into this state if the database connection is down. In this case, you must restart the Siebel Server component after the database connection has been reestablished.

Server Component Status Fields

Each server component record has two fields in which the status appears as shown in Table 14.