Agents Administration - Tests
 

Default Parameters for AsAbapQrfcTest

For each type (inbound and outbound) of queue, this test reports the number of queues that are experiencing errors currently and the count of queues that took too long to complete. In the process, the test turns the spotlight on those queues that may be responsible for unexpected breaks or prolonged delays (if any) in inter-system communication, and also reveals what could be causing such queues to perform poorly.

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

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

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

  • This test reports the longReadyQueues measure, which is the number of queues stuck in the Ready state for a long time. To report this measure, this test counts all queues that have been in the Ready state in excess of the duration (in hours) specified against LONGREADYCUTOFF (HRS).

  • This test reports the longRunningQueues measure, which is the number of queues that have been running for a long time. To report this measure, this test counts all queues that have been running for over a period of time (in hours) specified against LONGRUNNINGCUTOFF (HRS).

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

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