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

Changing the Enterprise Configuration Under Siebel Native Load Balancing

The most common configuration changes that affect load balancing performance are as follows:

• Adding or removing Siebel Servers
• Enabling or disabling Application Object Manager components

Update your lbconfig.txt file to reflect post-configuration changes in your Siebel environment. The recommended method of updating the lbconfig.txt file is to regenerate it and reapply the SWSE logical profile, as described in Enabling Siebel Native Load Balancing. This topic describes how to manually edit the lbconfig.txt file to reflect post-configuration changes.

Adding or Removing Siebel Servers

If you add or remove Siebel Servers that are being load-balanced, then you must revise the lbconfig.txt file to add or remove the servers from the VirtualServer definition. You can revise the lbconfig.txt file, as described in Enabling Siebel Native Load Balancing. Alternatively, if you have optimized the lbconfig.txt file, as described in Optimizing Performance for Siebel Native Load Balancing, then you might consider editing the file instead. Editing the file preserves your existing settings. After you edit the lbconfig.txt file, restart the Web server. Repeat these steps for all of the Web servers on which the SWSE is installed. You do not have to revise the SWSE configuration file (eapps.cfg).

Enabling or Disabling Application Object Managers

If you enable or disable a load-balanced Application Object Manager, then you must edit the lbconfig.txt file if either of the following is true:

• You are enabling an Application Object Manager on a Siebel Server that is not included in the VirtualServer definition in lbconfig.txt. Edit the definition to add the server.
• You are disabling an Application Object Manager on a server, and the Application Object Manager is the only one being load-balanced on the server. To prevent failed connection attempts, remove the Siebel Server from the VirtualServer definition in lbconfig.txt.

After you save the file, restart the Web server. Repeat these steps for all of the Web servers on which the SWSE is installed. You do not have to edit the SWSE configuration file (eapps.cfg).