Multiple User Logons Test

Whenever a user attempts to log on more than once to the SAP system (dialog logon attempt only), the system informs the user with a dialog box that he or she is already logged on. The user then has the following choices:

  • He or she can continue with the current logon and end all other user sessions.
  • If multiple logons are allowed, he or she can continue with the current logon and keep the other user sessions. (If multiple logons are not allowed, this option is not offered.)
  • He or she can cancel the current logon attempt.

The user is informed of the consequences of his or her decision. If the user ends existing user sessions, data that has not been saved is lost. If the user continues with his or her current logon attempt without ending existing user sessions, then the system records his or her decision.

If the multiple dialog logon capability is not used wisely, it can adversely impact the performance of the SAP system. For instance, if a user logs in multiple times to the same SAP system at around the same time window for no palpable reason, you could have a situation where many sessions on the SAP system are idle, thereby unnecessarily increasing the load on the SAP system and wasting resources. Moreover, the risk of corruption and instability is also high in such cases, as SAP administrators cannot control nor track the changes effected during the simultaneous logins. If such adversities are to be averted, administrators need to be instantly alerted when an unusually large number of multiple dialog logon sessions are noticed on the SAP Netweaver application server. This is exactly what the Multiple User Logons test does!

The test promptly captures the count of users who are logged on multiple times to the target SAP system (dialog logon attempts only), reports the total session load that is imposed by these users on the SAP system, and notifies administrators if these counts are more than normal. Additionally, the test also reveals the count of sessions that are active on the SAP system, thus indicating how many sessions are inactive/idle. Detailed diagnostics provided by the test also help administrators accurately isolate the idle sessions and the users who launched those sessions. Administrators can then pull up those user sessions for scrutiny during an audit.

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 the SAP ABAP instance being monitored.

Configurable parameters for the test
Parameter Description

Test Period

How often should the test be executed


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


Enter the port to which the specified host listens.


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.


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.


The password of the specified SAPUser.

Confirm Password

Confirm the password by retyping it here.


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.


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.


This parameter appears only if the Use SAPControl flag is set to No – i.e., if the test uses SAPJCO to collect measure. This is set to none by default. This implies that the eG agent automatically discovers the instance name at run time. 


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. 


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.


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.

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

Multiple logon users

Indicates the number of users who are currently logged in to SAP ABAP multiple times.


A high value could be a cause for concern. Under such circumstances, use the detailed diagnosis of this measure to figure out which users have multiple sessions open on the SAP ABAP instance currently, which client each user is connecting from, the total number of multiple dialog logon sessions launched by each user, and the number of such sessions that are currently active for each user. By comparing the active and total session counts for a user, you can understand whether/not too many sessions of that user are idle. Since idle/inactive sessions are a serious resource-drain, you may have to closely scrutinize such sessions.

Multiple logon sessions

Indicates the total number of sessions of all users who are currently logged into the SAP system multiple times.


This is a good indicator of the total session load imposed by the multiple dialog logons on the SAP ABAP instance.

In the event of an overload on the monitored instance, you can use the detailed diagnosis of this measure to know which users have logged into the instance the maximum number of times and has hence contributed the most to the load, where these users are connecting from, and the nature of the sessions launched by these users – i.e., whether active or inactive. If most of the sessions launched by these users are found to be inactive, you can conclude that such users are responsible for unnecessarily increasing the server load and for draining the server resources. During a SAP audit, these idle sessions should be subjected to close scrutiny.

Multiple active sessions

Indicates the number of sessions actively used by all users who have logged into the SAP ABAP server multiple times.


By comparing the value of this measure with that of the Multiple logon sessions measure, you can accurately compute the number of inactive/idle sessions on the SAP ABAP instance. Idle sessions unnecessarily increase the load on the instance and lock resources. To know which sessions are idle, use the detailed diagnosis of the Multiple logon sessions measure. To avoid such sessions, you can disable multiple dialog logons.