Agents Administration - Tests
 

Configuration of AsAbapUsrLgnTest

For every type of login, this test reports the number of users who are logged in, measures the activity levels of the users, and reports login failures. This way, the test indicates how well the ABAP system is being utilized, proactively reveals a consistent rise in user activity on the system, and pre-emptively points to dubious login attempts.

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 that is connecting to the R/3 server. To view the complete list of client IDs to choose from, do the following:

    • From any SAP client, execute the SAPlogon tool using the menu sequence: Start -> Programs -> SAP Front End -> SAPlogon.

    • Click on the Logon button in the dialog box that appears, and login to the SAP R/3 server using a valid user name and password.

    • Using the tree-structure in the SAP Easy Access console, navigate to the Client Maintenance node. The node sequence to be used is: SAP menu -> Tools -> Administration -> Client Administration -> Client Maintenance.

    • Double-click on the Client Maintenance node.

    • A Display View "Clients" page will appear, which will display the details of SAP clients. Any of the values of the Client column in this page, can be provided as the value of the CLIENTNAME parameter.

  • In the SAPUSER text box, provide a valid user name for logging into the SAP R/3 server. In order to enable the eG Enterprise suite to effectively monitor SAP, the name of a SAPUSER with either of the following profiles need to be specified: S_A.SYSTEM (super administrator) or SAP_ALL (all authorizations for SAP).

  • Specify the password of the specified SAPUSER in the PASSWORD text box.

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

  • The SYSNO is 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.

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

  • In the INSTANCENAME text box, specify the name of the SAP R/3 instance to be monitored. To view the complete list of instances to choose from, do the following:

    • From any SAP client, execute the SAPlogon tool using the menu sequence: Start -> Programs -> SAP Front End -> SAPlogon.

    • Click on the Logon button in the dialog box that appears, and login to the SAP R/3 server using a valid user name and password.

    • Using the tree-structure in the SAP Easy Access console, navigate to the CCMS tool available under the TOOLS option. The node sequence to be used is: SAP menu -> Tools -> CCMS -> Control/Monitoring -> Control Panel.

    • Double-click on the Control Panel node.

    • A Display Server Statuses and Alerts page will appear, which will display the details of the SAP Servers. Any of the values of the Server Name column in this page, can be provided as the value of the INSTANCENAME parameter.

  • Specify the duration (in seconds) for which this test should wait for a response from the SAP R/3 server, in the TIMEOUT text box. By default, this 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. 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.

  • Specify the duration of inactivity of a user, beyond which that user will be considered as inactive, in the CUTOFFMINS text box. Such users will be automatically excluded from the active count and the value of the activePct measure.

  • If the value chosen for the ISPASSIVE parameter is YES, then the server under consideration is a passive server in a SAP R/3 cluster. No alerts will be generated if the server is not running. Measures will be reported as “Not applicable” by the agent if the server is not up.

  • By default, the INCLUDE EG SAP USER flag is set to No. This means that the measures reported by this test will not, by default, consider the sessions launched by the eG agent on the SAP ABAP instance, as the configured SAPUSER. If you want the test to consider these sessions too when reporting metrics, set this flag to Yes.

  • By default, this test collects detailed metrics for the Logged in users measure, where the complete details of all the currently logged in users will be provided. In SAP ABAP installations where numerous users are logged in most of the time, collecting detailed diagnostics for the Logged in users measure may strain the eG database. To avoid this, you may want to set the SHOW LOGGED IN USER DD flag to No and turn off the detailed diagnosis capability of this measure.

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