User Sessions By Type Test

By tracking the user logins to the SAP ABAP system, administrators can understand how actively the system is being used and accordingly plan the capacity of the system. In addition, failed login attempts can also be isolated, thus turning the spotlight on unauthorized accesses and malicious attacks. This is why, eG Enterprise periodically executes the User Sessions By Type test. 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.

Target of the test : A SAP ABAP instance

Agent deploying the test : An internal/remote agent

Outputs of the test : One set of results for every user login type - GUI, PLUGIN, SYSTEM and various RFC subtypes such as RFC client, RFC Internal, RFC Server, RFC to App Server, RFC to R/2. One set of summary measures for all types.

Configurable parameters for the test
Parameter Description

Test Period

How often should the test be executed

Host

Host name of the server for which the test is to be configured.

PortNo

Enter the port to which the specified host listens.

ClientName

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, follow the instructions provided in Determining the Client ID/Name for the eG Agent to Connect to the SAP ABAP Instance.

SAPUser

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 with certain authorization objects. 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. The procedure for the same has been provided in Creating a New User Role for Monitoring and Assigning it to a SAP User. Once the new role is assigned to a SAP user, specify the name of this user against SAPUser.

Password

The password of the specified SAPUser.

Confirm Password

Confirm the password by retyping it here.

SysNo

This parameter appears only if the Use SAPControl flag is set to No – i.e., if the test uses SAPJCO to collect measures. 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, follow the procedure detailed in Identifying the SAP Router String and System Number.

Router

This parameter appears only if the Use SAPControl flag is set to No – i.e., if the test uses SAPJCO to collect measures. This parameter appears only if the use sapcontrol flag is set to No – i.e., if the test uses SAPJCO to collect measures.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, follow the procedure detailed in Identifying the SAP Router String and System Number.

InstanceName

This is set to none by default. This implies that the eG agent automatically discovers the instance name at run time. 

Timeout

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.

JCO Version

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 CONNECTOR files for SAP JCO version 3 from the SAP market place (as instructed by Downloading the SAP JCO Connector files Required for Monitoring ), then the JCO Version configuration should be 3.x. 

CutoffMins

Specify the duration of inactivity of a user, beyond which that user will be considered as inactive. Such users will be automatically excluded from the Active users count and the value of the Percentage active users measure.

IsPassive

If the value chosen is Yes, then the server under consideration is a passive server in a SAP ABAP INSTANCE 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.

Include eG SAP User

By default, this 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.   

Show Logged in User DD

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

Detailed Diagnosis

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.
Measurements made by the test
Measurement Description Measurement Unit Interpretation

Logged in users

Indicates the number of users of this type who are currently logged in.

Number

This is a good indicator of the current workload imposed on the SAP ABAP instance. You can compare the value of this measure across login types to know which type of login contributed to the maximum load. 

Use the detailed diagnosis of this measure to know which users of this type are currently logged in, when he/she logged in, the login duration, the status of each user, when last this user session was active, where he/she logged in from (i.e., the client terminal), and whether/not the user is active.

Active users

Indicates the number of users of this login type who created some activity in the instance during the last measure period.

Number

A high value of this measure is indicative of high level of user activity on the ABAP instance. In the event of an overload, you cn compare the value of this measure across login types to know which type of login is generating the maximum activity on the instance.

Percentage active users

Indicates the percentage of logged in users of this type who are currently active.

Percent

 

New users

Indicates the number of users of this login type who logged in during the last measurement period.

Number

 

Logouts

Indicates the number of users of this login type who have successfully logged out in the last measure period.

Number

The detailed diagnosis of this measure shows the activity summary of the logged out user such as name, hostname, login time, duration in minutes etc.

External sessions

Indicates the total number of external sessions created for this login type.

Number

When user logs on to SAP ABAP system, the system creates a new terminal session called external session. In general, each user can open up to six windows in a single SAP GUI session. Each of these windows corresponds to an external session on the application server with its own area of shared memory.

Internal sessions

Indicates the total number of internal sessions created for this login type.

 

Number

Internal sessions are automatically created by the ABAP system when navigating through transactions. Internal sessions are like navigation levels when performing system functions.. A maximum of 9 internal sessions can be created.

The internal session has a memory area that contains the ABAP program and its associated data. Internal sessions proportionately increase the memory consumption of its parent external session. High average number of internal sessions results in higher memory consumption for the same number of external sessions.