How to Monitor SAP HANA Database Server Using eG Enterprise?

eG Enterprise monitors the SAP HANA Database Server in an agent based and agentless manners. A set of pre-requisites should be fulfilled before attempting to monitor the SAP HANA database server. These requirements are discussed below.

Pre-requisites for Monitoring the SAP HANA Database Server

To monitor the SAP HANA database server:

  • A special database user account vested with the Monitoring role has to be created in every SAP HANA database instance that requires monitoring. The syntax of the script to be used for user creation is as follows:

    create user <username>  password  <password>

    grant monitoring to <username>

    A sample script for user creation is:

    create user sapegadmin password eGurkha@123;grant monitoring to sapegadmin;

    The credentials of this user have to be passed to the User and Password parameters while configuring the tests.

  • To connect to SAP HANA via JDBC, the eG agent needs the driver file provided by SAP, called ngdbc.jar. This driver file is part of the SAP HANA Client installation, which in turn will be part of your SAP HANA installation. To make this driver file available to the eG agent, do the following:

    • Copy the ngdbc.jar file from the SAP HANA client installation path to the <EG_INSTALL_DIR>\agent\lib directory (on Windows; on Unix, this will be the /opt/egurkha/agent/lib directory) on the eG agent host.

    • The table below provides the default location of the ngdbc.jar on different platforms.

      Platform Package version Default installation path
      Linux x86, 32 bit 32 bit /usr/sap/hdbclient
      Linux x86, 64 bit 64 bit /usr/sap/hdbclient
      Linux x86, 64 bit 32 bit /usr/sap/hdbclient32
      Other Unix/Linux platforms - /usr/sap/hdbclient
      Windows x86, 32 bit 32 bit C:\Program Files\sap\hdbclient
      Windows x86, 64 bit 64 bit C:\Program Files\sap\hdbclient
      Windows x86, 64 bit 32 bit C:\Program Files (x86)\sap\hdbclient

    If the HANA client is installed by a user without administrative rights, then that client will be available only to that user.

  • Then, restart the eG agent.