Siebel Installation Guide for UNIX > Requirements for Installing and Configuring Siebel Business Applications > Planning Your Siebel Deployment >
Planning Siebel Server Load Balancing
This topic is part of Planning Your Siebel Deployment.
Before you install your Siebel Enterprise Server components, determine your load balancing strategy for Siebel Servers. For more information, see Process of Configuring Load Balancing for Siebel Business Applications. See also Siebel Deployment Planning Guide and Siebel System Administration Guide.
Requirements for Generating the Load Balancing Configuration File
Generating the load balancing configuration (lbconfig.txt) file has the following requirements:
- Verify that all of the Siebel Servers for which you want to provide load balancing are running.
- On each Siebel Server, verify that the Application Object Managers that you want to load balance are enabled. Disable any Application Object Managers that you will not use. Note the Application Object Managers that are to be load balanced, so that you can later remove or comment out any disabled Application Object Managers that appear in the lbconfig.txt file that you generate.
Requirements for Setting Up a Third-Party HTTP Load Balancer
Observe the following requirements for setting up a third-party HTTP load balancer:
- The third-party HTTP load balancer must be validated for use with Siebel Business Applications. For more information, see 477835.1 (Article ID) on My Oracle Support. This document was previously published as Siebel Technical Note 540.
- Your third-party load balancer must have the following characteristics:
- It must be an HTTP load balancer capable of level 7 HTTP routing. It must be able to parse URLs in HTTP headers.
- It must allow end-points to manage TCP connections. Specifically, it must allow one-to-one mapping between client and server TCP sessions. Also, it must not do back-end connection pooling, such as reverse proxy server pooling.
- Verify that all of the Siebel Servers for which you want to provide load balancing are running. At least one Siebel Server must be running.
- On each Siebel Server, verify that the Application Object Managers that you want to load balance are enabled. Disable any Application Object Managers that you will not use.
- Select an unallocated, static virtual IP address and virtual port number for the load balancer.
- Generate the load-balancing configuration file (lbconfig.txt), as described in Generating the Load Balancing Configuration File (lbconfig.txt).
- Review the HTTP load balancer rule types: component rules, server rules, and round-robin rules.
- Configure the SWSE. The SWSE Configuration Wizard will ask you to choose Siebel load balancing or third-party load balancing. Choose third-party load balancing and enter the virtual IP address and virtual port number for the load balancer. For more information, see Process of Configuring the Siebel Web Server Extension.