Siebel Tasks Test

This test reports the current and completed tasks on every object manager on a Siebel server.

Target of the test : A Siebel Application Server

Agent deploying the test : An internal agent

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


In order to monitor the Siebel Application server, a valid user possessing admin privileges is required. Specify the credentials of such a user in the UserName text box.


Specify the administrator password.

Confirm Password

Confirm the Password by retyping it here.



Oracle Server IP

Specify the IP address of the Oracle Database server which is the backend database of the target Siebel Application server.

Oracle Port No

Specify the port number of the Oracle Database server.

Oracle SID

Specify the SID of the Oracle Database server.

Oracle UserName

In order to monitor an Oracle database server, a special database user account has to be created in every Oracle database instance that requires monitoring. A Click here hyperlink is available in the test configuration page, using which a new oracle database user can be created. Alternatively, you can manually create the special database user. When doing so, ensure that this user is vested with the select_catalog_role and create session privileges.

The sample script we recommend for user creation (in Oracle database server versions before 12c) for eG monitoring is:

create user oraeg identified by oraeg

create role oratest;

grant create session to oratest;

grant select_catalog_role to oratest;

grant oratest to oraeg;

The sample script we recommend for user creation (in Oracle database server 12c) for eG monitoring is:

alter session set container=<Oracle_service_name>;

create user <user_name>identified by <user_password> container=current default tablespace <name_of_default_tablespace> temporary tablespace <name_of_temporary_tablespace>;

Grant create session to <user_name>;                                

Grant select_catalog_role to <user_name>;

The name of this user has to be specified here.

Oracle Password

Password of the specified database user.

Confirm Password

Confirm the password by retyping it here.

Log Directory

Specify the full path to the log file of the target Siebel Application Server. For example, the location can be specified as C:\siebelsrv\log.

Detailed Diagnosis

To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option.

The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:

  • The eG manager license should allow the detailed diagnosis capability
  • Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.
Measurements made by the test
Measurement Description Measurement Unit Interpretation

Running tasks

Indicates the number of tasks currently running on this Object Manager.


The detailed diagnosis of this measure, if enabled, provides the details of tasks current running. Such details include the task ID, the object manager that is running the task, the mode in which the task is running, the query that is executing and the date\time at which the task started running. Using this information, you can quickly identify long-running tasks, and investigate the reason behind the same.

Completed tasks

Indicates the number of tasks that ran to completion and exited normally on this Object Manager.