Configuring SAP ABAP Instance for Monitoring by eG Enterprise suite

In Windows installations of the SAP ABAP Instance, ensure that the following steps are adhered to before attempting to monitor the SAP ABAP Instance:

  1. Download the SAPJCO API from the SAP Marketplace.
  2. The API will be available in the SAP Marketplace as a zip file. After downloading the API, extract the following files from the zip:

    • sapjcorfc.dll
    • librfc32.dll
    • sapjco.jar
  3. Copy the extracted files to the <EG_INSTALL_DIR>\lib directory on the eG agent host. The classpath is already set for this jar file.

    Note:

    • The eG Enterprise suite requires SAPJCO 2.0 for monitoring the SAP ABAP Instance. This in turn needs JRE 1.2 or higher.  If SAPJCO 2.1 is downloaded instead, then ensure that a minimum of JRE 1.3 is available.
    • The eG agents use the BC-XAL interface to connect to SAP ABAP INSTANCE for monitoring. This interface is compatible only with SAP ABAP INSTANCE release 4.5b and higher.

For SAP installations on Unix, follow the steps given below:

  1. Download the SAPJCO API from the SAP Marketplace.
  2. Extract the following files from the zipped API and copy them to the /opt/egurkha/lib directory:

    • libsapjcorfc.so (in AIX systems, this would be libsapjcorfc.o)
    • librfccm.so (in AIX systems, this would be librfccm.o)
    • sapjco.jar
  3. The path of these files should be set in LD_LIBRARY_PATH variable.
  4. Finally, restart the eG agent.

Note:

The SAP_R3_server component of the eG Enterprise suite also monitors the SAP Messaging server, using the following tests: SapMsgTest, SapMsgInfoTest, and SapGroupLbTest. 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 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.