Bookshelf Home | Contents | Index | PDF |
Deployment Planning Guide > Siebel Architecture Overview > 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. If one server fails, then requests are automatically routed to the remaining servers. You can use load balancing 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:
Load Balancing Before Siebel 7.7Before 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. Load Balancing as of Siebel 7.7 and LaterFor Siebel 7.7 and later releases, Siebel Systems supports two methods for implementing Siebel Server load balancing:
Siebel Connection BrokerOn 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. Discontinuation of Resonate SupportFor Siebel Servers, Resonate is classified as an uncertified third-party load balancer, and the following are no longer supported: Figure 2 shows an example of third-party load balancing. |
Deployment Planning Guide |