|Bookshelf Home | Contents | Index | PDF|
By default, Siebel native load balancing maps all Siebel Servers to a single virtual server after generating the lbconfig.txt file. All Application Object Manager (AOM) connect strings receive the virtual server name in the SWSE configuration file (eapps.cfg). This configuration allows the SWSE to distribute requests for all AOMs to all Siebel Servers.
When the SWSE sends a request for an AOM to a Siebel Server on which the AOM 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 AOM is not running, you should 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 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. Edit the AOM connection strings the eapps.cfg file after you apply a SWSE logical profile. If you reapply a SWSE logical profile, you update the eapps.cfg file and lose the changes you made the to the connection strings.
For example, you have two Siebel Servers, Sieb1 and Sieb2. They run the AOMs shown in Table 10.
NOTE: If you optimize lbconfig.txt by creating multiple virtual server definitions, 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.
|Siebel System Administration Guide||Copyright © 2010, Oracle and/or its affiliates. All rights reserved. Legal Notices.|