Bookshelf Home | Contents | Index | PDF |
Siebel System Administration Guide > Configuring the System Architecture > Configuring Siebel Server Load Balancing > Optimizing the Siebel Load-Balancing PerformanceBy default, Siebel load balancing maps all Siebel Servers to a single virtual server after generating the 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 For example, you have two Siebel Servers, Sieb1 and Sieb2. They run the AOMs shown in Table 9. To minimize retries, delete the existing definition, VirtualServer, in #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 connect strings in the SWSE configuration file ( Call Center: ConnectString = siebel.TCPIP.none.none://CallCenterVirtualServer/siebel/sscObjMgr_enu Sales: ConnectString = siebel.TCPIP.none.none://SalesVirtualServer/siebel/sseObjMgr_enu eChannel: ConnectString = siebel.TCPIP.none.none://eChannelVirtualServer/siebel/eChannelObjMgr_enu Marketing: ConnectString = siebel.TCPIP.none.none://MarketingVirtualServer/siebel/smeObjMgr_enu NOTE: If you optimize To optimize the load balancing configuration file
|
Siebel System Administration Guide |