Agents Administration - Tests
 

Default Parameters for SapMsgInfoTest

This test reveals whether the connection between the SAP ABAP instance server and the SAP Messaging server is available or not.

Note:

  • This test uses 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.

This page depicts the default parameters that need to be configured for the SapMsgInfoTest.

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

  • Specify the port number of the SAP Message server in the MESSAGEPORT text box.

  • Specify the path of the library files used in the execution of the lgtst command in the LIBRARYPATH text box.

  • This test uses an lgtst command to extract critical statistics from the SAP Message server. Specify the full path of the lgtst executable in the COMMANDPATH text box.

    • Note:

    The MESSAGEPORT, LIBRARYPATH and COMMANDPATH parameters are applicable only to non-windows platforms.

  • If the ISPASSIVE parameter is set to YES, then it means that by default all the SAP ABAP instance servers are passive servers in a SAP ABAP instance cluster. No alerts will be generated if the servers are not running. Measures will be reported as "Not applicable" by the agent if the servers are not up.

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

When changing default configurations of tests, the values with “$” indicate variables that will be replaced by the eG system according to the specific server being managed - for instance, $hostName is the host/nickname of the target host, $port is the port number of the server being monitored. e.g., for a server xyz:80, $hostName will be changed automatically by the eG manager to “xyz” and $port will be changed to “80” when configuring a test.