eG Monitoring
 

Measures reported by AsAbapProcessTest

The following processes are considered key for the proper functioning of a SAP ABAP instance:

  • Dispatcher: The ABAP dispatcher is the central process of the SAP ABAP. The main task of the ABAP dispatcher is to distribute requests to its work processes.

  • Message server: The SAP message server runs as a separate process, mostly on the same host as the central instance, and performs the following tasks in the SAP ABAP system:

    • Serves as a central communication channel between the individual application servers (instances) of the system;

    • Performs load distribution of logons using SAP GUI and RFC with logon group;

    • Acts as an information point for the Web Dispatcher and the application servers

  • IGS Watchdog: The Internet Graphics Service (IGS) constitutes the infrastructure to enable the application developers to display graphics in an Internet browser with a minimum of effort. The IGS has been integrated in the different SAP UI technologies from HTML GUI to Web Dynpro ABAP/Java and provides a server architecture where data from an SAP system or another source can be used to generate graphical or non-graphical output.

If any of these processes is offline, or experiences Critical errors, or reboots often, then the SAP ABAP system many not be able to perform the related operations. For instance, if say, the Dispatcher process is offline, then request processing will come to a standstill. Likewise, if the message server is not running, then no communication will happen between SAP instances. To avoid such issues, admiistrators should periodically run the AsAbapProcessTest test to check on the health state (whether Critical, Normal, Offline, or Online) and operational state (whether running or not running) of each of the critical processes described above, and capture process failures before they impact the critical operations of the SAP ABAP system.

The measures made by this test are as follows:

Measurement Description Measurement Unit Interpretation
Display_Status Indicates the current health state of this process.   The values that this measure can report and their corresponding numeric values are discussed in the table below:

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

Note:

By default, the test reports the Measure Values in the table above to indicate process state. In the graph of this measure however, the same is represented using the numeric equivalents only.

If the value of this measure is Critical, Error, or Offline, you can use the detailed diagnosis of the measure to determine the probable cause of the abnormal process status. The detailed diagnosis will also reveal when the process was started and the elapsed time of the process. From this information, you can figure out when the problem could have occurred and how long the problem may have persisted.

Process_Status Indicates whether/not this process is running currently.   The values that this measure can report and their corresponding numeric values are discussed in the table below:

Measure Value Numeric Value
Yes 1
No 2

Note:

By default, the test reports the Measure Values in the table above to indicate whether a process is running or not. In the graph of this measure however, the same is represented using the numeric equivalents only.
is_Restarted Indicates whether/not the process was restarted in the last measurement period.   The values that this measure can report and their corresponding numeric values are discussed in the table below:

Measure Value Numeric Value
No 1
Yes 2

Note:

By default, the test reports the Measure Values in the table above to indicate whether a process was restarted or not. In the graph of this measure however, the same is represented using the numeric equivalents only.