Bookshelf Home | Contents | Index | Search | PDF |
Siebel Server Installation Guide for UNIX > Clustering Your Siebel Deployment for Failover >
Clustering Guidelines
Clustering is a form of high availability (HA) system architecture designed to maximize availability of data and application services for users. Clustering creates a layer of redundancy so that when a function fails, other resources are available to take over the failed function. This process needs to be:
- Automatic—no operator intervention should be needed.
- Transparent—the users should not need to change anything.
Siebel eBusiness Applications can be deployed using a highly available architecture by employing both load-balancing techniques and failover clustering technologies.
Following the guidelines below will help promote successful failover protection in your system. However, these guidelines are in no way meant to be exhaustive or all-inclusive.
- You should install and have running Siebel Gateway Name Server (without Central Dispatch Software).
- You should have multiple running Siebel Servers within the same Siebel Enterprise. If you have multiple Siebel Servers running that are not clustered, these should be load balanced using Central Dispatch.
- It is important to cluster the Siebel Database Server as it is a single point of failure. If you intend to cluster the Siebel Database Server, you should have installed it and it should be running within its own cluster node. The Siebel Database Server should be the first server to be clustered.
NOTE: You can cluster Siebel eBusiness Applications if the Siebel supported db platform has cluster support from the database vendor; see your database vendor documentation on how to cluster your database.
Bookshelf Home | Contents | Index | Search | PDF |
Siebel Server Installation Guide for UNIX Published: 24 June 2003 |