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

Changing the Enterprise Configuration Under Siebel 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 Managers (AOMs)

These changes require that you edit the load balancing configuration file (lbconfig.txt).

Adding or Removing Siebel Servers

If you add or remove Siebel Servers that are being load-balanced, you must revise the load balancing configuration file (lbconfig.txt) to add or remove the servers from the VirtualServer definition. After you revise the file, restart the Web server.

Do this for all Web servers on which the Siebel Web Server Extension (SWSE) is installed. You do not need to revise the SWSE configuration file (eapps.cfg).

Use one of the following methods to revise the file:

• The recommended method for revising the lbconfig.txt file is to regenerate it.
• If you have optimized the file, consider editing the file instead. This preserves your existing settings.

Enabling or Disabling Application Object Managers (AOMs)

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

• You are enabling an AOM 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 AOM on a server, and the AOM 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. Do this for all Web servers on which the Siebel Web Server Extension (SWSE) is installed. You do not need to edit the SWSE configuration file (eapps.cfg).