Agents Administration - Tests
 

Default Parameters for SapAlertsTest

This test periodically tracks the errors that are newly added to the alert log of the SAP ABAP instance server.

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

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

  • In the CLIENTNAME text box, specify the ID of the client system as what the eG agent will be connecting to the SAP ABAP instance. To know how to determine the client ID to use, Click Here.

  • In the INSTANCENAME text box, specify the name of the SAP ABAP instance to be monitored. To figure out the name of the monitored instance, Click Here.

  • In the TIMEOUT text box, indicate the duration (in seconds) for which this test should wait for a response from the SAP ABAP instance. By default, this is set to 120 seconds.

  • Typically, to connect to a SAP ABAP instance and run tests, the eG agent requires the permissions of a SAP user who has been assigned the following privileges: S_RFC, S_TABU_DIS, S_XMI_PROD, S_TOOLS_EX, S_RZL_ADM. Ideally, you will have to create a new user role on the SAP ABAP instance for this purpose, associate the above-mentioned privileges with that role, and assign the new role to an existing SAP user. To know how to create the SAP user, Click Here. Once the new role is assigned to a SAP user, specify the name of this user against SAPUSER.

  • The PASSWORD text box indicates the password of the specified SAPUSER.

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

  • An indicator of the TCP/IP port at which the SAP server listens. For example, for a server that listens at port 3200, the SYSNO will be ‘00’. Similarly, if the SAP server port is 3201, the SYSNO will have to be specified as ‘01’. Therefore, in the SYSNO text box specify the system number of the SAP server with which the specified client communicates. To know the system number for the ABAP server being monitored, Click Here.

  • If the SAP client with the specified CLIENTNAME exists in a network external to the SAP server, then a router will be used to enable the server-client communication. In such a case, specify the router string of the router in the ROUTER text box. If both the client and the server exist in the same network, then specify ‘none’ against the ROUTER text box. To know what is the SAP Router string for the ABAP server being monitored, Click Here.

  • Provide a comma-separated list of monitor sets for which performance attributes are to be monitored in the SETS text box. For example: SAP CCMS Monitor Templates,Monitor Collection for Certification

  • Provide a comma-separated list of monitors under the configured monitor SETS for which performance attributes are to be monitored. While specifying the list of MONITORS, make sure that you specify them in the same order as that of your monitor SETS specification. For instance, the first monitor in your MONITORS list should belong to the first monitor set in your SETS specification, and so on. This implies that if your SETS specification reads as follows - SAP CCMS Monitor Templates,Monitor Collection for Certification - then the first monitor in your MONITORS specification should belong to the SAP CCMS Monitor Templates set and the second monitor should belong to the Monitor Collection for Certification set. In this case, your MONITORS specification may read as follows: Dialog Overview,Test Monitor Syslog.

    If you want to include more than one monitor from a particular monitor set in your MONITORS specification, then make sure that you repeat that monitor set's name as many times in your SETS specification.

    While configuring the SETS and MONITORS, you may want to know the exact names of the monitors and monitor sets that form part of your specification. To determine this, follow the procedure discussed the Monitoring SAP Environments document.

  • The XMI interface is a general framework for the CCMS external system management interfaces. This interface contains essential function modules and structures that coordinate connections between external system management tools and individual CCMS interfaces, and writes messages in the R/3 XMI log on behalf of the external tool. The XMI log is a table containing English message texts. The messages can have various degrees of detail. The audit level determines the degree of detail to which messages in the XMI log are written - i.e., whether the message should always be logged, or is simply a message which supplies further detail (higher detail degree). The XMI log contains messages from external tools and also messages which arise in SMAPI functions. To indicate to the test the degree of detail to which messages from the eG agent are to be written in the XMI log, you need to specify the XMI AUDIT LEVEL. By default, this parameter is set to 0, which indicates that all calls that modify the database are to be logged. The other values this parameter can take and their implications are discussed below:

    • 1: Logs all calls that modify the database and error messages
    • 2: Logs all calls that read from the database, modify the database, and error messages
    • 3: Logs all calls and all messages (full trace)

  • The eG agent uses the SAP JCO library to connect to the SAP ABAP system and pull out metrics. To enable the eG agent to make this connection and query the metrics, you need to specify the version of the SAP JCO library that the agent needs to use. For instance, to instruct the eG agent to use JCO v2.1.19, it would suffice if you specify the ‘major version number’ alone against JCO VERSION - in the case of this example, this will be 2.x. Note that if you have downloaded the SAP JCO API files for SAP JCO version 3 from the SAP market place, then the JCO VERSION configuration should be 3.x.

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