Logon load balancing increases the efficiency of various workgroups that have been defined, in terms of performance and system resource consumption, by
distributing users across available application servers based on requirements for workgroup service and load sensitivity.
distributing users across available application servers based on requirements for workgroup service and load sensitivity.
The quality value is calculated locally on each server by two different events:
- each 300 seconds started by the so-called Auto ABAP. The exact point of time depends on the time when the instance was started.
- at each fifth logon at the instance.
Based on the description above you can see that the calculation of the quality will be executed in a shorter interval than five minutes if neccessary (based on the number of logons).
Checking the Logon Load
You can check the logon load by displaying a list of the servers that are available and an overview of load distribution in your system.
Procedure
1. Choose CCMS -> Configuration -> Logon groups -> Goto -> Load distribution.
This list also shows the current performance status of the application servers that are both assigned to logon groups and currently running. Every five minutes, or after every five logons, each application server writes its own performance statistics data to a memory-resident table on the message server. The current logon server is refreshed for each group.
2. To refresh the performance status of an application server, double-click an application server line in the Instance column.
To display which users are logged on:
3. Choose Goto -> Back and then choose Goto -> User list.
The list shows how users are distributed over the different servers, and whether a particular server is full. You can sort this list by:
- user
- instance
- terminal
- time of the last user action.
Notes:
51789 - Poor user distribution in logon distribution
593058 - New RFC load balancing procedure
26317 - Set up for LOGON group for autom. load balancing
1847056 - 'Load balance not working'
118093 - Concepts of defining 'limits' in logon load balancing
The load balancing does not support hard limits for the muber of logged on users as described in the SAP note: 118093. But at least you can use the limit values in SMLG to manipulate the quality value of the instances used in the load balancing.
The maximum number of the Logon grups is 90.