How to Monitor SAP ABAP Server Using eG Enterprise?

eG Enterprise monitors the SAP ABAP Instance in an agent-based approach and an agentless approach. To obtain all the critical measures pertaining to the performance of the SAP ABAP Instance, it is recommended that you use eG’s Agent-based Monitor. Regardless of the monitoring approach, a set of pre-requisites should be fulfilled before attempting to monitor the SAP ABAP server. These requirements are discussed below.

Pre-requisites for Monitoring a SAP ABAP Instance Using eG Enterprise

Before attempting to monitor a SAP ABAP instance, make sure that the following are in place:

To connect to a SAP ABAP instance and run tests on it, the eG agent needs to be configured with the following:

When monitoring a SAP ABAP Instance, eG Enterprise also monitors the SAP Messaging server using the following tests: SAP Messages test, Application Server Connectivity test, and SAP Group Load Balancer test. In order for these tests to function smoothly, the following pre-requisites will have to be fulfilled.

  • These tests use an lgtst command to extract critical statistics from the SAP Messaging 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 should to be defined for any one of the logon groups on the SAP Messaging server.