Siebel Long Running Tasks Test

Server-side tasks can take often a long time to complete. For example, when a task is executed to fetch large amount of data from the database, it can take long time to finish. In such cases, it can soar CPU and memory usage which inturn affects the user interaction with the application. This test tracks the currently running tasks in each object manager on the Siebel server and identifies the tasks that have been running for a long time. And the administrators are forewarned on the details of these resource-intensive tasks, thus helping them to take proactive measures to minimise the resource usage by optimizing the long running tasks.

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 that is to be monitored.

Configurable parameters for the test
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.

InstallDirectory

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

GatewayServer

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

EnterpriseServer

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.

SiebelServername

Provide the name of the Siebel server that is to be monitored from the group of Siebel servers in the Enterprise server.

UserName

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.

Password

Specify the administrator password.

Confirm Password

Confirm the Password by retyping it here.

Timeout

Specify the duration (in seconds) for which this test should wait for a response from the Siebel Application server. If there is no response from the server beyond the configured duration, the test will timeout. By default, this is set to 120 seconds.

Component List

Each Siebel Server functions as an application server and is composed of server components. Each server component performs a defined function. Server components or groups of components determine what applications and services a Siebel Server supports. Specify a comma-separated list of Siebel components that need to be monitored in this text box. For example, SeverMgr, ApptBook. By default, this is set to all.

Long Running Task Cutoff Mins

For a task to be regarded as a long running task, in the Long Running Task Cutoff Mins text box, specify the duration (in minutes) beyond which the task continued running. The default value is 2.

DD Frequency

Refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD frequency.

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

Long running tasks

Indicates the number of tasks that are currently running on this Object Manager for more time than the configured Long running Task Cutoff.

Number

The detailed diagnosis of this measure, provides the details of tasks that are currently running for longer duration than the value defined in the Long Running Task Cutoff Mins. Such details include the task ID and Start time.

Using this information, you can quickly identify long-running tasks, and investigate the reason behind the same.