eG Help

A Siebel Server task is an instantiation of a Siebel Server component. To run a Siebel Server task, you must run a component job, which requests one or more Siebel Server tasks to run.

A Siebel Server task might be in one of four fundamental states: Running, Paused, Stopping, or Completed.

This test reports the currently running and completed tasks on every object manager on a Siebel server. In addition, this test reports the tasks on which errors were detected.

Measurement	Description	Measurement Unit	Interpretation
No_of_running_task	Indicates the number of tasks that are currently running on this Object Manager	Number	The detailed diagnosis of this measure, if enabled, provides the details of tasks that are currently running. Such details include the task ID, the object manager that is running the task, the mode in which the task is running, and the date/time at which the task began running. Using this information, you can quickly identify long-running tasks, and investigate the reason behind the same.
No_of_completed_task	Indicates the number of tasks that ran to completion and exited normally on this Object Manager.	Number
No_of_error_task	Indicates the number of tasks on which error was detected on this Object Manager.	Number	A low value is desired for this measure. A gradual/steady increase in the value of this measure is a cause of concern which may affect the overall performance of the Siebel Application server.