Bookshelf Home | Contents | Index | Search | PDF

Siebel Server Installation Guide for Microsoft Windows > Clustering Your Siebel Deployment for Failover >

About Clustered Servers

---

Clustering servers allows you to automatically migrate and restart resources, such as Siebel Servers, between two nodes of a cluster.

A logical computer, which is a computer comprised of multiple cluster nodes, can run on only one node at any given time. Should that node fail, the clustering software can be configured to failover the service or application to the secondary node to minimize any application outage. This is comparable to an application restart. As a result, the Siebel eBusiness Application operating at the time of the failover will experience a brief interruption of service.

All users connected to that Application Object Manager (AOM) on that Siebel Server will have to reconnect and login again. See Components that Should be Clustered and Table 13.
If the Siebel Server was hosting a Communications Server, then your CTI toolbar will be disabled. All users will have to reconnect and login again.

Clustering is best suited to promote the availability of those components that must be accessible on a server that is not load balanced and constitute a single point of failure.

NOTE:  You should not install Central Dispatch Software on the same machine where Siebel components are clustered.

In deployments for which high server availability is critical, clustering eliminates any single point of failure within the system.

Bookshelf Home | Contents | Index | Search | PDF