Bookshelf Home | Contents | Index | Search | PDF | ![]() ![]() ![]() ![]() |
Siebel Server Installation Guide for Microsoft Windows > Implementing Load-Balancing with Central Dispatch > Planning Your Central Dispatch Site >
Central Dispatch Deployment Considerations
- If your site has a large number of concurrent users (1000 or more), consider installing the Central Dispatch primary and backup schedulers on dedicated machines. This will provide for optimal performance during normal operation and when the primary scheduler goes down. If the performance during primary failure is not critical, a regular server node in the Central Dispatch site could be used as the backup scheduler.
- You cannot install Central Dispatch on any machine that is part of a cluster.
- Install Central Dispatch on the same machine as a Web server only if you are using Central Dispatch to load-balance the Web server. If you use Central Dispatch for Web server load-balancing, then the Web servers must belong to a different VIP than the application servers.
A server cannot make requests to the same virtual IP address that it is listening or receiving traffic on, which results in the following deployment limitations:
- The Web server and Central Dispatch Scheduler cannot reside on the same machine, because the Web server makes requests to the virtual IP address that the Scheduler listens on.
- The Web server and a load-balanced Siebel Server cannot reside on the same machine. The Web server and Siebel Server can reside on the same machine if the Siebel Server is not part of the Central Dispatch load-balanced site.
CAUTION: To install Central Dispatch on a computer with Compaq Teaming NIC, see TechNote 321 on SupportWeb before proceeding.
For more information on deployment planning with Central Dispatch, see TechNote 349, posted on SupportWeb.
Bookshelf Home | Contents | Index | Search | PDF | ![]() ![]() ![]() ![]() |
Siebel Server Installation Guide for Microsoft Windows Published: 25 June 2003 |