Siebel System Administration Guide > Configuring the System Architecture > Configuring Siebel Server Load Balancing >

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 on a Siebel Server. It will have a lower workload than other Application Object Managers 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 native load balancing distributes workloads based on logins. Users must terminate existing sessions and log in to the new sessions to cause workloads to be redistributed. For example, you have 1000 concurrent user sessions running on three Siebel Servers. You then add a fourth Siebel Server. Until all of the users end their sessions and log in again, the load is not evenly distributed between all four servers.

Whenever possible, let normal user login behavior rebalance Siebel Server workloads. Intervene only when absolutely necessary. Use one of the following methods to rebalance server workloads:

• Stop SCBroker on a Siebel Server. Doing so directs workload away from that server, but does not affect existing user sessions. However, SISNAPI session reconnect does not work for this server. If the SISNAPI connection times out, and user requests come through a Web server other than the one used for login, then the session is lost.
• Revise the lbconfig.txt file to remove a Siebel Server, as described in Changing the Enterprise Configuration Under Siebel Native Load Balancing. Removing a Siebel Server from load balancing directs its workload to other servers. If you have only one Web server, then removing a Siebel Server from the file terminates all of the user sessions. If you have multiple Web servers, then users making a session request might experience session termination. Use this method only as a last resort.