Skip Navigation Links | |
Exit Print View | |
Oracle Solaris Cluster Data Service for Siebel Guide Oracle Solaris Cluster 3.3 3/13SPARC Platform Edition |
Installing and Configuring HA for Siebel
Installing and Configuring HA for Siebel
Planning the HA for Siebel Installation and Configuration
Standard Data Service Configurations
Configuration Planning Questions
Installing and Configuring the Siebel Application
How to Install the Siebel Gateway on the Global File System
How to Install the Siebel Gateway on Local Disks of Physical Hosts
Installing the Siebel Server and Siebel Database
How to Install the Siebel Server and Siebel Database on the Global File System
How to Install the Siebel Server and Siebel Database on Local Disks of Physical Hosts
Verifying the Siebel Installation and Configuration
How to Verify the Siebel Installation and Configuration
Installing the HA for Siebel Packages
How to Install the HA for Siebel Packages
Registering and Configuring HA for Siebel
Setting HA for Siebel Extension Properties
How to Register and Configure HA for Siebel as a Failover Data Service
How to Register and Configure the Siebel Server
Verifying the HA for Siebel Installation and Configuration
How to Verify the HA for Siebel Installation and Configuration
Tuning the HA for Siebel Fault Monitors
Operation of the Siebel Server Fault Monitor
Operation of the Siebel Gateway Fault Monitor
Upgrading the HA for Siebel Resource Types
How to Upgrade to a New Version of HA for Siebel
This section contains guidelines for maintaining HA for Siebel.
To maintain a Siebel resource, you must disable the Siebel resource or bring the Siebel resource group to an unmanaged state using one of the following commands.
clresource disable resource
clresourcegroup unmanage resource_group
To start a Siebel resource, disable the resource, but keep the logical hostname online, before starting the Siebel resource manually.
Caution - If the Siebel server is started manually without disabling the resource or bringing the resource group to an unmanaged state, the Siebel resource start method might “reset” the service on the node where the resource is attempting to be started under Oracle Solaris Cluster control. This may lead to unexpected results. |