|Bookshelf Home | Contents | Index | PDF|
By default, when the lbconfig.txt file is generated, all Siebel Servers are mapped to a single virtual server. This virtual server name is then added to all Application Object Manager (AOM) connect strings in the Siebel Web Server Extension configuration file (eapps.cfg). This means that the Siebel Web Server Extension (SWSE) will distribute requests for all AOMs to all Siebel Servers.
When requests for an AOM are sent to a Siebel Server on which the AOM is not running, these requests fail. When this 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 AOM is not running, you should consider optimizing the load balancing configuration file. This will prevent 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 AOMs run. You then edit the AOM connection strings in the SWSE configuration file (eapps.cfg) to include the virtual server specific to that AOM.
For example, you have two Siebel Servers, Sieb1 and Sieb2. They run the AOMs shown in Table 10.
For more information on the layout of the lbconfig.txt file, see, About the Load Balancing Configuration File (lbconfig.txt).
NOTE: If you optimize lbconfig.txt by creating multiple virtual server definitions, you will lose these changes if you generate the file again. To prevent this, save the file under another name before generating it. Then copy your additional virtual server definitions to the new file. For information on generating lbconfig.txt, see Generating the Load Balancing Configuration File (lbconfig.txt).
|Deployment Planning Guide|