Configuring SAP Web Application Server

The following sections provide you the details about the files to be installed and how to make them available to the eG agent based on the versions of the SAP WAS.

Configuring SAP Web AS Versions Prior to v7.3

Before attempting to monitor a SAP Web AS that is of a version prior to v7.3, ensure that the following files are copied to the /opt/egurkha/lib directory (in Unix; on Windows, this will be the <EG_INSTALL_DIR>\lib directory):

  • com_sap_pj_jmx.jar
  • exception.jar
  • logging.jar
  • sapj2eeclient.jar

While the sapj2eeclient.jar is available in the {SAP_WAS_HOME_DIR}\usr\sap\TPP\DVEBMGS00\j2ee\j2eeclient directory, the other 3 jar files reside in the {SAP_WAS_HOME_DIR}\usr\sap\TPP\DVEBMGS00\j2ee\admin\lib directory.

Once the files are copied, restart the eG agent on the SAP Web AS.

Configuring SAP Web AS v7.3 (and above)

To monitor a SAP Web AS v7.3 (or above), do the following:

  1. Copy the sap.com~tc~bl~pj_jmx~Impl.jar file from the <SAP_WAS_HOME_DIR>\<SID>\<instance name>\j2ee\cluster\bin\ext\tc~jmx\lib\privatedirectory to the /opt/egurkha/lib directory (in Unix; on Windows, this will be the <EG_INSTALL_DIR>\lib directory) on the eG agent host.

  2. Likewise, copy the following files from the <SAP_WAS_HOME_DIR>\<SID>\<instance ID>\j2ee\j2eeclient\directory to the opt/egurkha/lib directory (in Unix; on Windows, this will be the <EG_INSTALL_DIR>\lib directory) on the eG agent host:

    • sap.com~tc~je~clientlib~impl.jar
    • sap.com~tc~exception~impl.jar
    • sap.com~tc~logging~java~impl.jar

  3. Then, rename all the four files so copied as indicated below:

    File Name Rename as
    sap.com~tc~bl~pj_jmx~Impl.jar com_sap_pj_jmx.jar
    sap.com~tc~je~clientlib~impl.jar sapj2eeclient.jar
    sap.com~tc~exception~impl.jar exception.jar
    sap.com~tc~logging~java~impl.jar logging.jar
  4. Finally , restart the eG agent on the SAP Web AS.