Siebel Deployment Planning Guide > Server Clustering Planning >

Where to Use Server Clustering

Siebel Business Applications support 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 Application Object Managers do not support or require clustering.

  • Siebel File System
  • Siebel Database

    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 or component groups:

  • Workflow Monitor Agent
  • Siebel Remote

    The DockString parameter in the Mobile Web Client configuration file must reference the virtual server name for remote synchronization to work after failover.

  • Replication Agent
  • MQSeries Server Receiver
  • SAP BAPI integration
  • SAP IDOC Receiver
  • SAP IDOC Receiver for MQ

Server Clustering for Some Components Is Not Supported

Siebel Business Applications do not support server clustering for the following components:

  • LDAP or ADSI directory server. Vendor may provide built-in replication.
  • Siebel Document Server (Microsoft server-side integration)
  • CTI hardware/switch
  • Siebel Charts Server

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 running on a Siebel Server: AOM1, AOM2, and AOM3. You can set up server clustering for AOM1 and AOM2, and set up load balancing for AOM3.

Siebel Deployment Planning Guide Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices.