Configuration of SiebelLoRuTkTest

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.

This page depicts the default parameters that need to be configured for the SiebelLoRuTkTest test.

• The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

• In the HOST text box, specify host for which the test is to be configured.

• In the PORT text box, specify the port number at which the specified host listens to. By default, this is 1199.

• In the INSTALLDIRECTORY text box, specify the full path to the install directory of the Siebel server.

• In the GATEWAYSERVER text box, specify the IP address/host name of the Gateway server.

• The ENTERPRISESERVER 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 the SEIBELSERVERNAME text box, specify the name of the Siebel server that is to be monitored from the group of Siebel servers in the Enterprise server.

• The DEBUG flag indicates whether the test should run in debug mode or not. If you wish to run the test in the debug mode, this flag should be set to true. By default, this flag is set to false.

• 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.

• In the PASSWORD text box, specify the administrator password and confirm the password by retyping it in the CONFIRM PASSWORD text box.

• In the TIMEOUT text box, 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.

• 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 the COMPONENTLIST text box. For example, SeverMgr, ApptBook. By default, this is set to all.

• 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.

• 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.

• 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 enabled/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.

• Once the above values are provided, click on the UPDATE button to register the changes made.

When changing the configuration for specific servers, a “*” beside the text box corresponding to the parameter signifies that these values have to be manually configured by the user. The parameter values that require to be configured will typically be prefixed with a “$” or contain a series of “*”. A value of “none” in the parameter value indicates that the corresponding parameter value can be changed if required.