Agents Administration - Tests
 

Configuration of SapMsgTest

This test reports the number of SAP ABAP instance servers that are communicating with the SAP Messaging server.

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.

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.

  • The port number to which the selected server is listening to has to be specified in the PORT textbox.

  • 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.

  • 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.

  • To make diagnosis more efficient and accurate, the eG system 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 against DETAILED DIAGNOSIS. To disable the capability, click on the Off option.

    The option to selectively enable/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 bad and normal 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 “$” or contain a series of “*”. A value of "none" in the parameter value indicates that the corresponding parameter value can be changed if required.