eG Monitoring
 

Measures reported by AsAbapCenProcTest

Central services form the basis of communication and synchronization for the SAP ABAP cluster. They are responsible for lock administration, message exchange, and load balancing within the cluster.

Central services run on one physical machine and constitute a separate instance. This SAP Central Services Instance (SCS) comprises the message server and the enqueue server.

The message server keeps a list of all server processes in the SAP ABAP cluster and provides information about their availability to Internet Communication Manager (ICM). It also represents the infrastructure for data exchange between the participating server processes.

The enqueue server manages logical locks. The enqueue server runs on the Central Services instance of the SAP ABAP cluster. It manages the lock table in the main memory and receives requests for setting or releasing locks. It maps the logical locks to the database.

If one of these processes is not running or is error prone, then, the data requests cannot be catered as the locks cannot be set or released. Sometimes, the process may suddenly stop while a lock is being held. This may cause data overhead which leads to performance bottlenecks on the target SAP ABAP Instance. To avoid such performance implications, it is necessary to monitor the status of the central services round the clock! The AsAbapCenProcTest helps administrators in this regard.

This test auto-discovers the central service processes and for each process, reports the current status. This test also reveals if the process is running or not and if the process was restarted recently. In addition, administrators may also be enlightened to the uptime of the process. This way, administrators may be able to figure out which process is actually lagging behind to run and is contributing to performance bottlenecks.

Outputs of the test : One set of results for each process on the target SAP Web Application server being monitored.

The measures made by this test are as follows:

Measurement Description Measurement Unit Interpretation
Display_Status Indicates the current state of this process.   The values reported by this measure and its numeric equivalents are mentioned in the table below:

Measure Value Numeric Value
Normal 1
Critical 2
Error 3
Offline 4
Note:

By default, this measure reports the Measure Values listed in the table above to indicate the current status of this process. The graph of this measure however, is represented using the numeric equivalents only i.e., 1 to 4.

Process_Status Indicates whether/not this process is running.   The values reported by this measure and its numeric equivalents are mentioned in the table below:

Measure Value Numeric Value
Yes 1
No 0
Note:

By default, this measure reports the Measure Values listed in the table above to indicate whether/not this process is running. The graph of this measure however, is represented using the numeric equivalents only i.e., 0 or 1.
is_Restarted Indicates whether/not this process was restarted during the last measurement period.   The values reported by this measure and its numeric equivalents are mentioned in the table below:

Measure Value Numeric Value
Yes 1
No 0
Note:

By default, this measure reports the Measure Values listed in the table above to indicate whether/not this process was restarted. The graph of this measure however, is represented using the numeric equivalents only i.e., 0 or 1.
Total_uptime Indicates the time elapsed since this process was restarted. Seconds