Siebel Infrastructure Test

Components refer to the 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. In order to effectively measure the end-user experience with a Siebel server, it is essential to keenly observe and analyze the fluctuations in responsiveness, and errors encountered by these components. The Siebel Infrastructure test enables such an analysis. In the event of any deterioration in the performance of a Siebel server, the metrics reported by this test will enable administrators to figure out whether there are any unresponsive/error-prone components on the Siebel server, which are impacting its performance.

Target of the test : A Siebel Application Server

Agent deploying the test : A remote agent

Outputs of the test : One set of results for each Siebel server being 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.

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.


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.

Measurements made by the test
Measurement Description Measurement Unit Interpretation

Average transfer time

Indicates the average time taken to transfer connections between components.


A low value is desired for this measure. A high value of this measure may indicate connection bottleneck.

Maxed out errors

Indicates the number of times the connection transfer failed due to the components being busy.


A high value of this measure indicates that  the component is overloaded and hence unable to handle excess load.

Successful connections

Indicates the number of connections that were successfully forwarded to the components.


A high value is desired for this measure.

Total connections

Indicates the total number of connections to the components.



Total transfer time

Indicates the overall time spent in transferring connections to the components.



FDR buffer wraps

Indicates the number of FDR buffer wraps per second on the components.


Siebel flight data recorder files (extension .fdr) are records of system and server component behavior at run time. In the event of a system or server component failure, the settings and events leading to the failure are captured and logged.

FDR buffer life

Indicates the time elapsed since the FDR buffer was last created.



FDR aging rate

Indicates the average time taken for each FDR buffer wrap on the components.



Task completion rate

Indicates the rate at which the tasks were completed for the server components.



Tasks exceeding capacity

Indicates the number of tasks that were assigned to the components after the maximum task limit of the components was reached.


A high value for this measure is an indication of overload on the Siebel server.

Database connection retries

Indicates the number of times the database connection was retried due to database connection loss.


A low value is desired for this measure. A high value is an indication of poor database connectivity.

Deadlock rollbacks

Indicates the number of times the connection was retried due to deadlock rollbacks on the database.


Deadlock rollback is a condition when forced rollback is initiated by the database manager due to a deadlock.

Exhausted retries

Indicates the number of connection retries that were exhausted.


A high value indicates persistent connectivity issues that needs to be addressed immediately.