eG Monitoring
 
Measures reported by AsAbapMultLgnTest

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

The measures made by this test are as follows:

Measurement Description Measurement Unit Interpretation
Multi_Lgns Indicates the number of users who are currently logged in to SAP ABAP multiple times. Number 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.
Multi_Lgns_Sess Indicates the total number of sessions of all users who are currently logged into the SAP system multiple times. Number 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. Number By comparing the value of this measure with that of the Multi_Lgns_Sess 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 Multi_Lgns_Sess measure. To avoid such sessions, you can disable multiple dialog logons.