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

Revising the Third-Party HTTP Load Balancer Configuration

You must revise the third-party HTTP load balancer configuration or edit the SWSE configuration file (eapps.cfg) if you do either of the following:

• Add or remove a Siebel Server that is load-balanced.
• Enable or disable an Application Object Manager that is load-balanced.

Requirements for Configuring Third-Party Load Balancing

Observe the following requirements for configuring third-party load balancing:

• Verify that all of the Siebel Servers that you want to load-balance are running.
• Verify that the Application Object Managers that you want to load-balance are running. Disable any Application Object Managers that you do not want to load-balance.
• Obtain the virtual IP (VIP) address and port number for the load balancer.
• Review the layout of the load-balancing configuration file.

Several of the steps in the following procedures are about manually modifying the configuration of the load balancer. If a script is available that automatically imports server configurations, then run this script instead.

Revising the Load Balancer Configuration After Adding or Removing a Load-Balanced Siebel Server

Use the following procedure to revise the load balancer configuration after adding or removing a load-balanced Siebel Server.

To revise the load balancer configuration after adding or removing a load-balanced Siebel Server

1. Add or remove the Siebel Server.

   See the Siebel Installation Guide for the operating system you are using.

2. Generate a new lbconfig.txt file.

   Doing so updates the URL mappings in the file to reflect the new or removed server. See the Siebel Installation Guide for the operating system you are using.

3. Place the new lbconfig.txt file in the directory where you store the SWSE logical profile.
4. Use a text editor to view the lbconfig.txt file.

   Use the file to obtain URLs for editing rules in the following steps.

5. Start the load balancer configuration software.
6. Update the resource group definitions to reflect the added or removed server.
7. Revise the component and round-robin rules to reflect the added or removed Application Object Manager running on the server.
8. If you are adding a server, then create a server rule. If you are deleting a server, then delete the server rule.
9. Save the configuration.
10. Apply the SWSE logical profile to Web servers where the SWSE is installed.

    See the Siebel Installation Guide for the operating system you are using.

Revising the Load Balancer Configuration After Enabling or Disabling an Application Object Manager on a Load-Balanced Siebel Server

Use the following procedure to revise the load balancer configuration after enabling or disabling an Application Object Manager on a load-balanced Siebel Server.

To revise the load balancer configuration after enabling or disabling an Application Object Manager on a load-balanced Siebel Server

1. Enable or disable the Application Object Manager.

   For more information, see Configuring the Siebel Server.

2. Generate a new lbconfig.txt file.

   See the Siebel Installation Guide for the operating system you are using.

3. Place the new lbconfig.txt file in the directory where you store the SWSE logical profile.
4. Use a text editor to view the lbconfig.txt file.

   Use the file to obtain URLs for editing rules in the following steps.

5. Start the configuration software for the third-party load balancer.
6. Revise the component and round-robin rules to reflect the added or removed Application Object Manager.
7. Save the configuration.
8. Apply the SWSE logical profile to Web servers where the SWSE is installed.

   See the Siebel Installation Guide for the operating system you are using.

No changes are required to the server rules that manage reconnection requests in the load balancer.