Deployment Planning Guide > Server Clustering Planning >
Where to Use Server Clustering
The Siebel application supports server clustering for the following parts of a Siebel deployment:
- Siebel Gateway Name Server
- Siebel Servers. Individual server components can be clustered, load-balanced, or both. Some Siebel Application Object Managers do not support or require clustering.
- Siebel File System
- Siebel Database Server. Subject to limitations of third-party RDBMS software.
- Web server on which the Siebel Web Server Extension (SWSE) is installed.
In addition, server clustering is the preferred method for providing high availability for the following Siebel Server components:
- Dynamic Assignment
- Email Agent
- MQ Series Receiver
- Replication agent
- SAP BAPI integration
- SAP IDOC Receiver
- SAP IDOC Receiver for MQ
- Siebel Remote. Make sure that the DockString parameter in the remote client configuration file is referencing the virtual server name. This must be configured correctly for remote synchronization to work after failover.
- Workflow Monitor
Server Clustering for Some Components Is Not Supported
Siebel does not support server clustering for the following Siebel Server components:
- Siebel Corba Object Manager
- LDAP/ADSI Directory Server. Vendor may provide built-in replication.
- Universal Queuing Server
- Documents Server (Microsoft server-side integration)
- Hummingbird Search Server
- First Logic Data Quality
- CTI hardware/switch
Server Clustering and Load Balancing Can Be Used Together
You can set up server clustering and load balancing on the same Siebel Server. For example, you have three Application Object Managers, AOM1, AOM2, and AOM3 running on a Siebel Server. You can set up server clustering for AOM1 and AOM2, and set up load balancing for AOM3.