This section contains the information you need to plan your Sun Cluster HA for Siebel installation and configuration.
Your data service configuration might not be supported if you do not observe these restrictions.
Use the restrictions in this section to plan the installation and configuration of Sun Cluster HA for Siebel. This section provides a list of software and hardware configuration restrictions that apply to Sun Cluster HA for Siebel.
For restrictions that apply to all data services, see the release notes for your release of Sun Cluster.
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.
If you are using Sun Cluster HA for Siebel with Sun Cluster HA for Sun Java System Web Server, you must configure Sun Cluster HA for Sun Java System Web Server as a failover data service. Scalable Sun Cluster HA for Sun Java System Web Server cannot be used with Sun Cluster HA for Siebel.
Your data service configuration might not be supported if you do not adhere to these requirements.
Use the requirements in this section to plan the installation and configuration of Sun Cluster HA for Siebel. These requirements apply to Sun Cluster HA for Siebel only. You must meet these requirements before you proceed with your Sun Cluster HA for Siebel installation and configuration.
For requirements that apply to all data services, see Configuration Guidelines for Sun Cluster Data Services in Sun Cluster Data Services Planning and Administration Guide for Solaris OS.
Install each Siebel gateway and each Siebel server in its own Siebel root environment (each instance has its own siebenv.sh file). This allows each instance to be independent of others, making failovers and problem diagnosis easier.
If more than one Siebel server will use the Siebel Filesystem, install the Siebel Filesystem on a global file system. This will ensure that all Siebel server resources have access to the same Filesystem from any node in the cluster.
Do not use the Autostart feature. When prompted to configure this parameter during the Siebel gateway or Siebel server installation, configure Autostart=NO.
Use the standard configuration in this section to plan the installation and configuration of Sun Cluster HA for Siebel. Sun Cluster HA for Siebel supports the standard configuration in this section. Sun Cluster HA for Siebel might support additional configurations. However, you must contact your Sun service provider for information on additional configurations.
Figure 1 illustrates a possible configuration using Sun Cluster HA for Siebel. The Siebel server and the Siebel gateway are configured as failover data services.
Use the questions in this section to plan the installation and configuration of Sun Cluster HA for Siebel. Insert the answers to these questions into the data service worksheets in Appendix C, Data Service Configuration Worksheets and Examples, in Sun Cluster Data Services Planning and Administration Guide for Solaris OS.
What is the logical hostname for the following resources: Siebel gateway and Siebel server?
Where will the system configuration files reside?
See Configuration Guidelines for Sun Cluster Data Services in Sun Cluster Data Services Planning and Administration Guide for Solaris OS for the advantages and disadvantages of placing the Siebel binaries on the local file system as opposed to the cluster file system.