| Bookshelf Home | Contents | Index | Search | PDF | |
Siebel Server Installation Guide for Microsoft Windows > Clustering Your Siebel Deployment for Failover > About Clustered Servers >
Components that Should be Clustered
Consider enabling clustering on those servers on which you will operate components or server software, such as:
- Siebel Gateway Name Server (without Central Dispatch components)
- Siebel Servers hosting components not managed by Central Dispatch
NOTE: Most components not load balanced by Central Dispatch should be clustered. Exceptions to this are components such as Server Request Processor which can run on all servers, Business Integration Manager, Work Flow Process Manager, and Server Request Broker which can run on multiple nodes for redundancy.
- Siebel File System
- Siebel Database Server
NOTE: Siebel eBusiness Applications can be high availability (HA) enabled by employing both load-balancing techniques and failover clustering technologies. These technologies are complementary and mutually exclusive in a Siebel environment. Clustered Siebel object managers must be run either as a single instance or statically load-balanced.
Figure 7 shows a representative grouping of clustered components.
| Bookshelf Home | Contents | Index | Search | PDF | |
Siebel Server Installation Guide for Microsoft Windows Published: 25 June 2003 |
