Siebel Components Test

The requests to every application executing on a Siebel server are typically handled by one/more object managers. If the object manager required by an application is not running, then the Siebel server will be forced to reject all requests for that application, causing the end-user to suffer. The Siebel Components test monitors each of the object managers to ascertain their current state and load.

Target of the test : A Siebel Application Server

Agent deploying the test : An internal agent

Outputs of the test : One set of results for every object manager monitored.

Configurable parameters for the test
Parameter Description

Test period

How often should the test be executed.


The host for which the test is to be configured.


The port number at which the specified host listens to. By default, this is 1199.


Provide the full path to the install directory of the Siebel server.


Provide the IP address/host name of the Gateway server.


This refers to the name that was specified for the Enterprise server during a Siebel installation. An Enterprise server is a logical entity. It collectively represents the Siebel application servers and gateway server.


This test executes a command on the Siebel server to extract the statistics of interest; this command requires administrator privileges to execute. Therefore, enter the name of the Siebel administrator.


Specify the administrator password.

Confirm Password

Confirm the Siebel Agent Password by retyping it here.

Exclude Components


Measurements made by the test
Measurement Description Measurement Unit Interpretation

Run state

Indicates the current state of this Siebel Object Manager.


The value 0 for this measure indicates that the object manager is unavailable. While 1 indicates that the object manager is online (i.e., it is available, but not currently running any tasks), 2 indicates that the object manager is running (i.e., it is available and is currently running one/more tasks).

Max tasks reached

Indicates whether this object manager has reached its 'maximum tasks' limit or not.


This measure is a true indicator of load on the object manager. As long as the value of this measure is 0, it is an indication of an optimal number of tasks currently executing on the object manager. If the value becomes 1, it implies that the 'maximum tasks' limit has been reached. When this happens, eG Enterprise triggers an alarm indicating an overload on the object manager. During such circumstances, the object manager will run out of threads to execute any more tasks, and will therefore be unable to handle subsequent requests.

Maximum MTServers

An MTServer is a multi-threaded component process; this measure indicates the maximum number of MTServers per component per server.



Active MTServers

Indicates the currently active MTServers on this object manager.


The value of this should be close to the value of the Num_max_mts_svr measure. 

Percent usage of MTServers

Indicates the percentage of maximum MTServers that are being actively used by this object manager.


Ideally, the value of this measure should be between 90-100%. A far less value indicates that the object manager is grossly under-utilizing the MTServers. This happens when the object manager does not have enough tasks to run, and is more or less idle. 

Minimum MTServers

Indicates the minimum number of MTServers that should run, by default, on this object manager when the Siebel server starts.



MTServer crashes

Indicates whether/not the MTServer crashes were on this object manager.


The value Yes for this measure indicates that one or more MTServers were crashed and the number of MTServers running on this object manager is lesser than the value of Minimum MTServers measure. Consequently, the load on the server increases and the request processing capability of the object manager reduces. While No indicates that the number of MTServers running on the object manager is greater than or equal to the value of the Minimum MTServers measure. This indicates that there are enough MTServers are available on the object server to handle the requests.