Siebel Stats 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 resource usage, responsiveness, and errors encountered by these components. The Siebel Stats test, executed by an internal agent, 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 resource-intensive/error-prone components on the Siebel server, which are impacting its performance.

Target of the test : A Siebel Application Server

Agent deploying the test : An internal agent

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


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.

Measurements made by the test
Measurement Description Measurement Unit Interpretation

CPU time

Indicates the total CPU time for component tasks


Ideally, the value of this measure should be low. A very high value could indicate that users are executing one/more CPU-intensive tasks on the Siebel server. Further investigation is hence required to zero-in on the resource-hungry components.

Elapsed time

Indicates the total elapsed (running) time for component tasks.


This measure is indicative of time taken by the task to complete its operation.

Think time

Indicates the average end-user think time between requests.



Total response time

Indicates the total amount of time taken by the components to respond to requests.


A very high value indicates slow component responsiveness. Response time issues can be caused by high resource utilization or heavy load on the components.

Total tasks

Indicates the total number of tasks completed for the server components.



Avg response time

Indicates the average time taken by the components to respond to requests.


A very high value indicates that the component responds slowly to requests. Response time issues can be caused by high CPU utilization or heavy load on the components.

Avg connection time

Indicates the average connect time for component sessions.


Ideally, a low value is desired. A high value indicates connection bottlenecks.


Indicates that the component job ran but encountered an error during operation.


Ideally, this value should be 0.

Tests attempted

This indicates the number of test attempted.



Tests failed

This metric represents the number of tests failed.



Tests successful

This metric represents the number of test successful.