ABAP Instance Availability Test

This test reveals whether the connection between the SAP ABAP instance and the SAP Messaging server is available or not.

Target of the test : The SAP Messaging server

Agent deploying the test : An internal/remote agent

Outputs of the test : One set of results for the SAP ABAP instance being monitored.

Configurable parameters for the test
Parameter Description

Test Period

How often should the test be executed


Host name of the server for which the test is to be configured.


Enter the port to which the specified host listens.


Specify the port number of the SAP Message server.


This test uses an lgtst command to extract critical statistics from the SAP Message server. Specify the full path to the library files used in the execution of the lgtst command.


Specify the full path to the lgtst executable in the Command Path text box.


The MessagePort, LibraryPath and CommandPath parameters are applicable only to non-windows platforms.


Specify the number of SAP ABAP instances to be polled by the lgtst command, so as to determine whether load balancing has been enabled on the SAP ABAP server or not.


If the value chosen is Yes, then the server under consideration is a passive server in a SAP ABAP INSTANCE cluster. No alerts will be generated if the server is not running. Measures will be reported as “Not applicable” by the agent if the server is not up.

Measurements made by the test
Measurement Description Measurement Unit Interpretation


Indicates whether a SAP ABAP application server is currently available for communicating with a SAP Message server.


If the value of this measure is 0, it means that the SAP ABAP application server can no longer communicate with other SAP ABAP servers (especially if central instance and dialog instance are installed in separate systems). The value 100 indicates the availability of the SAP ABAP application server.


  • This test uses an lgtst command to extract critical statistics from the SAP Message server. With this command, you can check the active instances of your SAP System and check existing logon groups directly at the operating system level. To ensure that this test functions smoothly, the lgtst command needs to be copied to the /opt/egurkha/bin directory (on Unix, or the <EG_INSTALL_DIR>\bin on Windows).
  • Another pre-requisite for the smooth execution of this test is that, in the transaction SMLG, the External RFC Permitted attribute will have to be defined for any one of the logon groups on the SAP Message server.