How Does eG Enterprise Monitor SAP Business Warehouse Instance?

SAP Business Warehouse Instance can be monitored in an agent-based or an agentless manner. Agentless monitoring is the recommended approach.

For agentless monitoring of SAP Business Warehouse Instance, the eG agent should be deployed on a remote Windows host in the environment. For agent-based monitoring, make sure that the eG agent is deployed on the SAP Business Warehouse Instance being monitored.

Regardless of where it is deployed (whether on a remote Windows host or on the SAP Business Warehouse Instance), the eG agent collects metrics using SAPControl Web Service.

Pre-requisites for Monitoring a SAP Business Warehouse Instance Using eG Enterprise

The Pre-requisites for monitoring a SAP Business Warehouse Instance is similar to that of the pre-requisities for monitoring a SAP ABAP Instance.

Before attempting to monitor a SAP Business Warehouse Instance, make sure that the following are in place:

  • For running tests on the SAP Business Warehouse Instance/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 topic.
  • Typically, the SAP JCO library that the eG agent needs to connect to a SAP ABAP Instance/SAP ABAP System supports 64-bit only. However, the eG agent on AIX supports only 32-bit. This is why, if you are using an eG agent on AIX to monitor a SAP Business Warehouse Instance/ SAP ABAP Instance, you need to replace the 32-bit agent JRE folder with the corresponding folder from a 64-bit JRE installation.

To connect to a SAP ABAP Instance/SAP Business Warehouse 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 topic.
  • The SAP user as who the eG agent has to connect the SAP ABAP Instance/SAP ABAP System; 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_BGRFC, S_RFC, S_RFC_ADM, S_RFCACL, S_TCODE, S_ADMI_FCD, S_RZL_ADM, S_TABU_DIS, S_TABU_NAM, S_USER_GRP, S_XMI_PROD, S_APPL_LOG, S_TOOLS_EX. 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 topic.
  • The system number of the SAP ABAP Instance/SAP ABAP System to be monitored; make sure that you know the system number of the target SAP ABAP Instance/SAP ABAP System 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 topic.
  • Where a SAP router is used, the router string of the target SAP ABAP Instance/SAP ABAP System; make sure you figure out what the router string is before you set out to monitor the ABAP Instance/ABAP System. To determine the router string of the instance/system being monitored, use the steps detailed in Identifying the SAP Router String and System Number topic.

When monitoring a SAP ABAP Instance/SAP Business Warehouse Instance, eG Enterprise also monitors the SAP Messaging server using the following tests: SAP Application Servers test, SAP Instance Reachability 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 will have to be defined for any one of the logon groups on the SAP Messaging server.