Siebel Deployment Planning Guide > Siebel Architecture Overview >

About Siebel Server Load Balancing

Load balancing distributes workload across multiple Siebel Server computers. Each Siebel Server runs an instance of the service that you want to load balance. Load balancing also provides failover. If one Siebel Server fails, then requests are automatically routed to the remaining Siebel Servers.

The Siebel Gateway and Siebel Application Interface work together to provide Siebel Server load balancing. When a user requests a new application connection, Siebel Application Interface sends a request to Siebel Gateway, which returns a connect string for the least-loaded Application Object Manager from among the Siebel Servers supporting that component. The user session will use this Application Object Manager.

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:

• Application Object Managers
• Siebel Product Configurator (uses own load balancing method)
• Siebel EAI (whenever possible)

(On each Siebel Server, Siebel Connection Broker (SCBroker) provides intraserver load balancing. SCBroker distributes connection requests across multiple instances of Application Object Manager processes running on the same server computer. For more information, see About the Siebel Connection Broker.)

Siebel CRM also supports load balancing across multiple installed instances of Siebel Application Interface. For more information, see Recommendations for High Availability Deployments.