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:
- For running tests on the SAP ABAP instance and pulling the desired metrics, the eG agent uses a few SAP JCO connector files. Make sure that these files are downloaded from the SAP Marketplace to the eG agent host. To know how, refer to the Downloading the SAP JCO Connector files Required for Monitoring
To connect to a SAP ABAP instance and run tests on it, the eG agent needs to be configured with the following:
- The name/number of the SAP client as what the eG agent has to connect to the SAP ABAP instance; to know what client ID to provide, use the procedure detailed in the Determining the Client ID/Name for the eG Agent to Connect to the SAP ABAP Instance
- Typically, to connect to a SAP ABAP instance and run tests, the eG agent requires the permissions of a SAP user who has been assigned the following authorization objects: S_RFC, S_RFC_ADM, S_BGRFC, S_RFCACL, S_TCODE, S_ADMI_FCD, S_TABU_DIS, S_XMI_PROD, S_TOOLS_EX, S_RZL_ADM, S_USER_GRP, S_APPL_LOG. Ideally, you should create a new user role on the SAP ABAP instance for this purpose, associate the above-mentioned authorization objects with that role, and assign the new role to an existing SAP user. To know how to do this, refer to Creating a New User Role for Monitoring and Assigning it to a SAP User
- The system number of the SAP ABAP instance to be monitored; make sure that you know the system number of the target SAP ABAP instance before you begin monitoring. To determine the system number of the instance being monitored, use the steps detailed in Identifying the SAP Router String and System Number
- Where a SAP router is used, the router string of the target SAP ABAP instance; make sure you figure out what the router string is before you set out to monitor the ABAP instance. To determine the router string of the instance being monitored, use the steps detailed in Identifying the SAP Router String and System Number
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.