Agents Administration - Tests
 

Configuration of AsAbapUsrLdTest

This test monitors the transactions of every user to the SAP ABAP system and reports the following:

  • Which user is executing resource-intensive transactions on the ABAP system?

  • Which user is overloading the system?

  • Which user is experiencing slowness when running transactions on the system? Where did this delay occur? - in the dispatcher queue? when loading/generating objects? when rolling-in/rolling out user contexts? in the database? when performing enqueue operations? or when waiting for RFC calls to complete?

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, specify the host for which this test is to be configured.

  • Specify the port at which the specified HOST listens to 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.

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

  • To report workload metrics, the eG agent will have to typically analyze numerous dialog steps of activity on the SAP ABAP system. To reduce the stress on the eG agent, you can limit the number of dialog steps the eG agent needs to process in order to make a fair assessment of the workload and the processing ability of the ABAP system. This limit can be specified against MAXIMUM STEPS. By default, this limit is set to 5000.

  • By default, this test monitors only those users who are currently logged into the SAP ABAP system. This is why, the INCLUDE USERS parameter is set to none by default. If you want a few specific users to be monitored regardless of whether they are logged in or not, specify the names of those users as a comma-separated list against this parameter. If this is done, then such users alone will be monitored irrespective of their login status, while all other users will be monitored only if they are currently logged in.

  • By default, the INCLUDE EG SAP USER flag is set to No. This means that, by default, this test will disregard all user sessions launched by the eG agent as the configured SAPUSER. If you want the test to report metrics for the SAPUSER sessions too, set this flag to Yes.

  • 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, eG 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, by default, 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.