Sun Cluster Data Service for Siebel Guide for Solaris OS

Sun Cluster HA for Siebel Overview

Sun Cluster HA for Siebel provides fault monitoring and automatic failover for the Siebel application. High availability is provided for the Siebel gateway and Siebel server. With a Siebel implementation, any physical node running the Sun Cluster agent cannot be running the Resonate agent as well. Resonate and Sun Cluster can coexist within the same Siebel enterprise, but not on the same physical server.

Note –

If you are using the Solaris 10 OS, install and configure this data service to run only in the global zone. At publication of this document, this data service is not supported in non-global zones. For updated information about supported configurations of this data service, contact your Sun service representative.

For conceptual information about failover services, see the Sun Cluster Concepts Guide for Solaris OS.

Table 1 Protection of Siebel Components


SiebelComponent	Protected by
Siebel gateway	Sun Cluster HA for Siebel The resource type is `SUNW.sblgtwy`.
Siebelserver	Sun Cluster HA for Siebel The resource type is `SUNW.sblsrvr`.

Note –

Before you upgrade the Sun Cluster HA for Siebel data service from Sun Cluster 3.1 10/03 or 3.1 4/04 or 3.1 9/04 to Sun Cluster 3.2, you need to manually remove the link to the SUNW.sblsrvr resource type from the /usr/cluster/lib/rgm/rtreg/SUNW.sblsrvr file, using the following command:

# rm -f /usr/cluster/lib/rgm/rtreg/SUNW.sblsrvr

If you are upgrading the Sun Cluster HA for Siebel data service from Sun Cluster 3.1 8/05 to Sun Cluster 3.2, you do not have to manually remove the link. The Siebel postremove script automatically removes the link to the SUNW.sblsrvr resource type, when you do the upgrade.