Agents Administration - Tests
 

Configuration of AsAbapSyslgTest

This test monitors the syslog file and for each event type logged into the file, this test reports the numerical statistics of the total number of messages logged, the messages that were entered due to transaction problems, application server and memory related isssues. In addition, this test reports the error messages and the warings that were entered.

The default parameters associated with this test are:

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

  • Specify the the host name of the server for which the test is to be configured in the HOST text box.

  • Specify the port number at which the specified HOST listens in the PORT text box.

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

  • If the ISPASSIVE parameter is set to YES, then it means that by default all the SAP ABAP instances are passive servers in a SAP ABAP instance. 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.

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

  • Specify a comma separated list of custom patterns for which this test should report metrics for in the CUSTOMPATTERN text box. You can specify the patterns in the PatternName:Patternstring format. However, the PatternName is optional. If the PatternName is specified, then this PatternName is displayed as the descriptor of this test in the eG monitor interface. If the PatternName is not specified, then the PatternString alone is specified as the descriptor of this test. By default, none will be displayed against this parameter.

  • By default, this test monitors all the syslog messages logged in the syslog file. If you wish to monitor only those syslog messages for which alerts were generated in the SAP ABAP server instance, then set the SHOWALERTSONLY flag to Yes.

  • By default, each syslog message is mapped to a severity value. Specify a severity value against the SEVERITYCUTOFF text box beyond which all syslog messages are included in the scope of montoiring. By default, the value of this parameter is 49.

  • The DD FREQUENCY refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD FREQUENCY.

  • 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 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 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 “$” or contain a series of “*”. A value of "none" in the parameter value indicates that the corresponding parameter value can be changed if required.