Agents Administration - Tests
 

Configuration of ODataUsrStatTest

Using this test, administrators can also figure out which operation was being frequently performed when requests were being initiated by each user-is it the read property? or read feed? or metadata? or batch operations? or create?

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 for which the test is to be configured has to be specified.

  • In the PORT text box, enter the port number at which the target host being monitored listens.

  • For the eG agent to connect to the target SAP ABAP System and collect metrics, this test should be configured with the IP address of any of the SAP ABAP Instances associated with the target SAP ABAP System. Specify such IP address in the APPLICATION SERVER text box.

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

  • 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 authorization objects: S_BGRFC, S_RFC, S_RFC_ADM, S_RFCACL, S_TCODE, S_ADMI_FCD, S_TABU_DIS, S_TABU_NAM, S_USER_GRP, S_XMI_PROD, S_TOOLS_EX, S_APPL_LOG, 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 authorization objects 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 in the SAP USER text box.

  • Specify the Password of the specific SAP User in the PASSWORD text box.

  • 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, specify the system number of the SAP server with which the specified client communicates in the SYSNO text box . 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 parameter INSTANCE NAME is set to none by default. This implies that the eG agent automatically discovers the instance name at run time.

  • Specify the duration (in seconds) for which this test should wait for a response from the SAP ABAP instance in the TIME OUT list box. By default, this paremeter is set to 120 seconds.

  • 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 in the JCO VERSION list box. 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 CONNECTOR files for SAP JCO version 3 from the SAP market place, then the JCO Version configuration should be 3.x.

  • By default, this parameter is set to none. If you wish to include only a few users in the scope of monitoring, then specify a comma-separated list of users in the INCLUDE USERS text box. You can even include specific patterns in this text box. For example, in an environment where users such as John Adam, John William and John Smith are available, specifying John* in this text box will include all 3 users in the scope of monitoring.

  • To exclude certain users from the scope of monitoring, specify a comma-separated list of users in the EXCLUDE USERS text box. By default, this parameter is set to none. You can even include specific patterns in this text box. For example, in an environment where users such as John Adam, John William and John Smith are available, specifying John* in this text box will exclude all 3 users from the scope of monitoring.

  • By default, this test is capable of pulling out metrics from the target SAP ABAP System irrespective of the number of OData Service requests processed. However, in some environments where large number of requests are processed per minute, the eG backend database may not be able to store such voluminous data. To avoid overheads to the eG backend database, administrators can set a desired value against the RESPONSE TIME parameter. This will ensure that the eG agent collects metrics only for those OData Service requests that returned a response with a time limit (specified in MilliSeconds) greater than the value configured against this parameter.

  • 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 the DD FREQUENCY parameter, 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.