Siebel Components Test
Components refer to various tasks or programs that run on the Siebel server and perform the work requested by the user. For example, the object manager is one of the key components on a Siebel server. 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 : A remote agent
Outputs of the test : One set of results for every Object Manager that is to be monitored.
| Parameter | Description |
|---|---|
|
Test period |
How often should the test be executed |
|
Host |
The host for which the test is to be configured. |
|
Port |
The port number at which the specified host listens to. By default, this is 1199. |
|
JMX Remote Port |
Specify the port at which the JMX listens for requests from the remote hosts. Ensure that you specify the same port that you have mentioned in the agentconfig.connectors.xml file in the <SIEBEL_INSTALL_DIR>\siebsrvr\mgmtagent\pref\system folder used in the target application. |
|
JNDIName |
The JNDIName is a lookup name for connecting to the JMX connector. By default, this is jmxrmi. If you have resgistered the JMX connector in the RMI registery using a different lookup name, then you can change this default value to reflect the same. |
|
Siebel Agent User and Siebel Agent Password |
In order to monitor the Siebel Application server, a valid user possessing admin privileges is required. Specify the login credentials of such a user in the Siebel Agent User and Siebel Agent Password text boxes. |
|
Confirm Password |
Confirm the Siebel Agent Password by retyping it here. |
| Measurement | Description | Measurement Unit | Interpretation | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
State |
Indicates the current state of this Siebel Object Manager. |
|
The values that this measure can report and their corresponding numeric values are tabulated below:
Note: By default, this measure reports the above-mentioned Measure Values while indicating the current state of this Siebel Object Manager. However, in the graph of this measure, the current status will be represented using the numeric equivalents only. |
||||||||||||||||
|
Max MTServers |
Indicates the maximum number of MTServer per component per server. |
Number |
An MTServer is a multi-threaded component process. A high value for this measure is indicative of too many users logging into the Siebel server. |
||||||||||||||||
|
Active MTServers |
Indicates the number of MTServers that are currently active on this Object Manager. |
Number |
The value of this measure should be close to the Max MTServers measure. |
||||||||||||||||
|
MTS usage factor |
Indicates the percentage of MTServers that are being actively used by this Object Manager. |
Percent |
Ideally, the value of this measure should be between 90-100%. A far less value indicates that the object mnager 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. |
