SAP Logon Load Balancing
Logon load balancing increases efficiency with respect to performance and the use of system resources for variously defined workgroups by distributing users across available application servers based on requirements for workgroup service and utilization.
In a system landscape where there are multiple application server instances, specific servers are best assigned to a particular application workgroup, with the available resources and buffers of that server tuned specifically to that application and not shared with other applications. This is highlighted in the following sections:
Recommended:
With logon load balancing and servers assigned to specific applications:
Logon Group FI/CO - Server A FI/CO & Server B FI/CO
Logon Group SD - Server C SD & Server D SD
With logon load balancing and shared, or homogeneous, properties of servers across logon groups:
Logon Group FI/CO - Server A FI/CO,Server B FI/CO & Server C FI/CO
Logon Group SD - Server C SD,Server D SD & Server E SD
Not recommended:
With logon load balancing and servers available to all applications:
Logon Group PUBLIC - Server A FI/CO + SD,Server B FI/CO + SD,Server C FI/CO + SD,Server D FI/CO + SD
With only two servers with logon load balancing and servers assigned to specific groups:
Logon Group FI/CO - Server A
Logon Group SD - Server B
Logon Groups
Each SAP application has different resource requirements. Certain applications may therefore require more servers and logon groups. For example, you should assign separate servers for the application component PP.
Generally, each logon group should have two servers. If one server is not available, the users are automatically connected to the second server. Servers can be added or removed while the SAP system is running.
If it is not practical for you to assign separate servers to integrated applications such as the application components SD-MM and FI-CO, you should assign common logon groups to these applications.
No comments:
Post a Comment