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

Optimizing Performance for Siebel Native Load Balancing

By default, Siebel native load balancing maps all of the Siebel Servers to a single virtual server after generating the lbconfig.txt file. All of the Application Object Manager connection strings receive the virtual server name in the SWSE configuration file (eapps.cfg). This configuration allows the SWSE to distribute requests for all of the Application Object Managers to all of the participating Siebel Servers.

When the SWSE sends a request for an Application Object Manager to a Siebel Server on which the Application Object Manager is not running, these requests fail. When this situation occurs, the SWSE automatically sends the failed request to another Siebel Server. Typically, users do not notice these retries unless the allowed maximum number of retries is exceeded.

The allowed maximum number of retries is five. Therefore, if there are more than five load-balanced Siebel Servers on which an Application Object Manager is not running, then you might consider optimizing the load balancing configuration file. This configuration prevents users from experiencing failed attempts to start applications.

You optimize lbconfig.txt by adding additional virtual server definitions that define the groups of Siebel Servers on which particular Application Object Managers run. You then edit the Application Object Manager connection strings in the SWSE configuration file (eapps.cfg) to include the virtual server specific to each Application Object Manager. You edit the connection strings in the eapps.cfg file after you apply an SWSE logical profile. Reapplying an SWSE logical profile updates the eapps.cfg file, and you lose the changes that you made to the connection strings.

For example, you have two Siebel Servers, Sieb1 and Sieb2, which run the Application Object Managers for Japanese that are shown in Table 10.

To minimize retries, delete the existing VirtualServer definition in lbconfig.txt and define four virtual servers as shown in the following examples:

#Section one -- Session Manager Rules:
CallCenterVirtualServer=1:sieb1:2321;2:sieb2:2321;
SalesVirtualServer=1:sieb1:2321;2:sieb2:2321;
eChannelVirtualServer=1:sieb1:2321;
MarketingVirtualServer=2:sieb2:2321;

Then edit the connection strings in the SWSE configuration file (eapps.cfg) as in the following examples for version 8.1.1.x, for Japanese:

• Call Center Object Manager (JPN). ConnectString = siebel.TCPIP.none.none://CallCenterVirtualServer/SBA81/SCCObjMgr_jpn
• Sales Object Manager (JPN). ConnectString = siebel.TCPIP.none.none://SalesVirtualServer/SBA81/SSEObjMgr_jpn
• eChannel Object Manager (JPN). ConnectString = siebel.TCPIP.none.none://eChannelVirtualServer/SBA81/eChannelObjMgr_jpn
• Marketing Object Manager (JPN). ConnectString = siebel.TCPIP.none.none://MarketingVirtualServer/SBA81/SMObjMgr_jpn

NOTE:  If you optimize lbconfig.txt by creating multiple virtual server definitions, then you lose these changes if you generate the file again. To prevent this situation, save the file under another name before generating it. Then copy your additional virtual server definitions to the new file.

To optimize the load balancing configuration file

1. Start Siebel Server Manager and enter the following command to obtain Siebel Server IDs.

   list server show SBL_SRVR_NAME, SV_SRVRID

   Write down the Siebel Server IDs of the servers that you want to add to virtual server definitions.

2. Navigate to the directory where you store the SWSE logical profile and open the lbconfig.txt file with a text editor.
3. In Section One, add additional virtual server definitions. Save the file.
4. Apply the SWSE logical profile to the Web server that hosts the SWSE.
5. Open the SWSE configuration file, eapps.cfg, with a text editor.

   Its default location is in SWSE_ROOT\bin, where SWSE_ROOT is the installation directory for the SWSE.

6. Change the virtual server name in the Application Object Manager connection strings, then save the file.
7. Restart the Web server.