Use the following procedures to install and configure a data service.
Install the data service packages from the installation medium on which the packages are supplied.
Sun Cluster 3.0 5/02 CD-ROM
Sun Cluster 3.0 5/02 Agents CD-ROM
Install and configure the application to run in the cluster environment.
Configure the resources and resource groups that the data service uses. When you configure a data service, specify the resource types, resources, and resource groups that the Resource Group Manager (RGM) is to manage. The documentation for the individual data services describes these procedures.
Before you install and configure data services, see Sun Cluster Software Installation Guide for Solaris OS, which includes instructions for the following tasks:
Installing the data service software packages
Configuring IP network multipathing groups that the network resources use
You can use Sun Cluster Manager to install and configure the following data services: Sun Cluster HA for Oracle, Sun Cluster HA for Sun JavaTM System Web Server, Sun Cluster HA for Web Server, Sun Cluster HA for Apache, Sun Cluster HA for DNS, and Sun Cluster HA for NFS. See the SunPlex Manager online help for more information.
The following table summarizes the tasks for installing and configuring Sun Cluster data services. The table also provides cross-references to detailed instructions for performing the tasks.
Table 1–1 Tasks for Installing and Configuring Sun Cluster Data Services
Task |
Instructions |
---|---|
Install the Solaris and Sun Cluster software | |
Set up IPMP groups | |
Set up multihost disks | |
Plan resources and resource groups |
Appendix D, Data Service Configuration Worksheets and Examples |
Decide the location for application binaries, and configure the nsswitch.conf file | |
Install and configure the application software |
The appropriate Sun Cluster data services book |
Install the data service software packages |
Sun Cluster Software Installation Guide for Solaris OS or the appropriate Sun Cluster data services book |
Register and configure the data service |
The appropriate Sun Cluster data services book |
This example summarizes how to set up the resource types, resources, and resource groups that a failover data service for the Oracle application requires. For complete instructions for configuring the data service for the Oracle application, see Sun Cluster Data Service for Oracle Guide for Solaris OS.
The principal difference between this example and an example of a scalable data service is as follows: In addition to the failover resource group that contains the network resources, a scalable data service requires a separate resource group (scalable resource group) for the application resources.
The Oracle application has two components, a server and a listener. Sun supplies the Sun Cluster HA for Oracle data service, and therefore these components have already been mapped into Sun Cluster resource types. Both of these resource types are associated with resources and resource groups.
Because this example is a failover data service, the example uses logical hostname network resources, which are the IP addresses that fail over from a primary node to a secondary node. Place the logical hostname resources into a failover resource group, and then place the Oracle server resources and listener resources into the same resource group. This ordering enables all of the resources to fail over as a group.
For Sun Cluster HA for Oracle to run on the cluster, you must define the following objects.
LogicalHostname resource type – This resource type is built in, and therefore you do not need to explicitly register the resource type.
Oracle resource types – Sun Cluster HA for Oracle defines two Oracle resource types—a database server and a listener.
Logical hostname resources – These resources host the IP addresses that fail over in a node failure.
Oracle resources – You must specify two resource instances for Sun Cluster HA for Oracle — a server and a listener.
Failover resource group – This container is composed of the Oracle server and listener and logical hostname resources that will fail over as a group.