SAP System Status Test

For each instance of the SAP ABAP system being monitored, this test reports the current status. Using this test, administrators can figure out the error-prone instances and the instances that were offline with ease. This may help them troubleshoot the issues before end users start complaining about the unavailability of the instances.

Target of the test : A SAP ABAP System

Agent deploying the test : An internal agent

Outputs of the test : One set of results for each Instance type: Instance name of the target SAP ABAP System 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.

Central WSDL Port

By default, this test uses the SAPControl web service for collecting measures. In this text box, specify the port number of the SAPControl web service. To determine the exact port number of the SAPControl web service, you can look up the etc/services file on the SAP ABAP system being monitored. If the port number is not declared in the etc/services file, you can specify the default port number of the web service against WSDL Port If the web service is not SSL-enabled, then the default port number of the web service will be: 5<NR>13. Similarly, if the web service is SSL-enabled, then the default port number of the web service will be: 5<NR>14. <NR> in the port number refers to the system number of the SAP server being monitored. The system number is an indicator of the TCP/IP port at which the SAP server listens. For example, for a server that listens at port 3200, the system number will be ‘00’. Similarly, if the SAP server port is 3201, the system number will have to be specified as ‘01’. Accordingly, the default port number of an SSL-enabled SAPControl web service will be 50014 , if the system number is 00, or 50114, if the system number is 01.

OS Username and
OS Password

To enable the test to access the SAPControl web service and determine process state, you need to configure the OS Username and OS Password parameters of the test with the credentials (i.e., name and password) of an OS user, who fulfills one of the following conditions:

  • The name of the OS user should be declared using the service\admin_users profile parameter; (OR)
  • The name of the user group to which the OS user belongs should be declared using the service\admin_groups profile parameter; (OR)
  • The OS user should have the permission to execute the sapstartsrv executable

Confirm Password

Confirm the OS password by retyping it here.


Set this flag to Yes, if the SAPControl web service is SSL-enabled. Set this flag to No, if the SAPControl web service is not SSL-enabled.

DD Frequency

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.

Detailed Diagnosis

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 enable/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.
Measurements made by the test
Measurement Description Measurement Unit Interpretation


Indicates the current status of this instance.


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
ABAP Central Instance is Critical 7
ABAP Central Instance is Error 8
ABAP Central Instance is Offline 9
Java Central Instance is Critical 12
Java Central Instance is Error 13
Java Central Instance is Offline 14
Application Instance is Critical 17
Application Instance is Error 18
Application Instance is Offline 19
One or more Application Instance are Critical 21
One or more Application Instance are Error 22
One or more Application Instance are Offline 23


By default, this measure reports the Measure Values listed in the table above to indicate the current status of each SAP ABAP instance. The graph of this measure however is represented using their corresponding numeric equivalents only.