Bookshelf Home | Contents | Index | PDF |
Deployment Planning Guide > Load Balancing and Resilient Processing Planning > About Load BalancingLoad balancing distributes workload across multiple servers. Each server runs an instance of the service you want to load-balance. Load balancing also provides failover. Should one server fail, then requests are automatically routed to the remaining servers. Load balancing can be used when the Siebel Enterprise Server has two or more Siebel Servers that are not clustered. Load balancing is the preferred method for providing high availability for the following server components:
Prior to Siebel 7.7Prior to Siebel 7.7, Siebel Systems implemented server load balancing using a third-party software product, Resonate Central Dispatch. When multiple Siebel Servers ran the same Application Object Manager, Central Dispatch distributed server requests across the Siebel Servers. Siebel Servers were integrated with Central Dispatch to maintain session continuity. Siebel 7.7 and LaterFor Siebel 7.7 and later releases, Siebel supports two methods for implementing Siebel Server load balancing:
Siebel Connection Broker. On each Siebel Server, the Siebel Connection Broker (SCBroker), provides intraserver load balancing. SCBroker distributes server requests across multiple instances of Application Object Managers running on the server. Resonate support discontinued. Automatic registration of Resonate rules is no longer supported. Siebel Server parameters for Resonate registration are no longer supported. For Siebel Servers, Resonate is classified as an uncertified third-party load balancer. Figure 5 shows an example of third-party load balancing. |
Deployment Planning Guide |