distributing users across available application servers based on requirements for workgroup service and load sensitivity.
- 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.
The list of available servers for load balancing is controlled by program RSRZLLG0. The scheduling of this program is controlled by rdisp/autoabaptime. The default is 300 (5 minutes). Details of the scheduling of RSRZLLG0 can be found in note 16201.
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.
771708 - SMLG: Newly added logon group do not work
593058 - New RFC load balancing procedure
1729172 - Correction: Unequal RFC load balancing
26317 - Set up for LOGON group for autom. load balancing
1847056 - Load balance not working
118093 - Concepts of defining 'limits' in logon load balancing
It is not possible to differ between using a logon group or logging on directly to an application server (because using a logon group causes
SAPlogon to request the logon group information from the message server and to start then a direct logon, too).
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.
Please note that you will have a favourite server for *each* logon group. As described in note 113440 there always exists the logon groupSPACE although you don't see it defined in SMLG. The maximum number of the Logon grups is 90.
Recommendations for Logon Load Balancing and Logon Groups - Configuration - SAP Library