For each type of transaction, this test reports the number of transactions that are currently open and the maximum time taken for executing transactions. Using this test, you could figure out which transaction is taking too long to execute and is currently blocking other transactions.

The default parameters associated with this test are as follows:

• The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

• In the HOST text box, the host name of the server for which the test is to be configured has to be specified.

• Specify the port number at which the specified HOST listens to in the PORT text box. The default port is 30015.

• In order to monitor a SAP HANA database server, a special database user account with Monitoring privileges has to be created in every SAP HANA database instance that requires monitoring. The syntax of the script that is used for user creation is:

  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 name of this user has to be specified in the USER text box.

• Specify the password of the specified USER in the PASSWORD text box.

  Note:

  The password should be alpha-numeric containing atleast one uppercase alphabet and a special character.

• Confirm the password by retyping it in the CONFIRM PASSWORD text box.

• In the EXCLUDE TRANSACTION TYPE text box, specify a comma-separated list of transaction types that need to be excluded from the scope of monitoring. By default, none is specified in this text box.

• If the value chosen for the ISPASSIVE parameter is Yes, then the SAP HANA database server under consideration is a passive server in a SAP HANA cluster. No alerts will be generated if the server is not running. Measures will be reported as “Not applicable” by the agent if the server is not up.

• To make diagnosis more efficient and accurate, the eG Enterprise suite embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the DETAILED DIAGNOSIS capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option.

  The option to selectively enabled/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:

  • The eG manager license should allow the detailed diagnosis capability
  • Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.

• If multiple components of the same component type are awaiting configuration, then an APPLY TO OTHER COMPONENTS check box will appear in this page. Clicking on this check box will allow you to apply the configuration to all/selected components of that type.

• Once the necessary values have been provided, clicking on the Update button will register the changes made.

When changing the configuration for specific servers, a “*” beside the text box corresponding to the parameter signifies that these values have to be manually configured by the user. The parameter values that require to be configured will typically be prefixed with a *ldquo;$” or contain a series of “*”. A value of "none" in the parameter value indicates that the corresponding parameter value can be changed if required.