Deployment Planning Guide > Managing Siebel Load Balancing >
Manually Rebalancing Siebel Server Loads
Server loads can become unevenly distributed for several reasons:
- You have just added a new Siebel Server to the network. It will have a low workload compared to other Siebel Servers.
- You have just enabled an Application Object Manager (AOM) on a Siebel Server. It will have a lower workload than other AOMs on different Siebel Servers.
- There was a server configuration or request routing problem that prevented even distribution of workloads. When this problem is corrected, one or more Siebel Servers will have low workloads.
Siebel load balancing distributes workloads based on logins. Users must terminate existing sessions and log in to new sessions to cause workloads to be redistributed. For example, you have a 1000 concurrent user sessions running on three Siebel Servers. You then add a fourth Siebel Server. Until all the users end their sessions and log in again, the load will not be evenly distributed between all four servers.
Whenever possible, let normal user login behavior rebalance Siebel Server workloads. Manually intervene only when absolutely necessary. Use one of the following methods to manually rebalance server workloads:
- Stop SCBroker on a Siebel Server. This directs workload away from that server. This does not impact existing user sessions. However, SISNAPI session reconnect does not work for this server. If the SISNAPI connection times out, and user requests are coming through a Web server other than the one used for log in, the session will be lost.
- Modify the Siebel load balancing configuration file (lbconfig.txt) to remove a Siebel Server. Then restart the Web server. This removes the Siebel Server from load balancing and directs its workload to other servers. If you have only one Web server, this terminates all user sessions. If you have multiple Web servers, users making a session request may experience session termination. Use this method only as a last resort.