Overview of the Installation and Configuration Process

Use the following procedures to install and configure data services.

• Install the data-service packages from the Sun Cluster Agents CD.

• 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) will manage. The chapters for the individual data services describe these procedures.

Before you install and configure data services, see the Sun Cluster 3.0 U1 Installation Guide, which includes procedures on how to install the data service software packages and how to configure Network Adapter Failover (NAFO) groups that the network resources use.

---

Note -

You can use SunPlex Manager to install and configure the following data services: Sun Cluster HA for Oracle, Sun Cluster HA for iPlanet Web Server, Sun Cluster HA for Netscape Directory 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.

---

Installation and Configuration Task Flow

The following table shows a task map of the procedures to install and configure a Sun Cluster failover data service.

Table 1-2 Task Map: Sun Cluster Data Service Installation and Configuration

Task	For Instructions, Go to
Install the Solaris and Sun Cluster software	Sun Cluster 3.0 U1 Installation Guide
Set up NAFO groups	Sun Cluster 3.0 U1 Installation Guide
Set up multihost disks	Sun Cluster 3.0 U1 Installation Guide
Plan resources and resource groups	Sun Cluster 3.0 U1 Release Notes
Decide the location for application binaries, and configure the nsswitch.conf file	Chapter 1, Planning for Sun Cluster Data Services
Install and configure the application software	The chapter for each data service in this book
Install the data-service software packages	Sun Cluster 3.0 U1 Installation Guide or the chapter for each data service in this book
Register and configure the data service	The chapter for each data service in this book

Example

The example in this section shows how you might set up the resource types, resources, and resource groups for an Oracle application that has been instrumented to be a highly available failover data service.

The main difference between this example and an example of a scalable data service is that, in addition to the failover resource group that contains the network resources, a scalable data service requires a separate resource group (called a scalable resource group) for the application resources.

The Oracle application has two components, a server and a listener. The Sun Cluster HA for Oracle data service is supplied by Sun, 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.

To have the Sun Cluster HA for Oracle data service run on the cluster, you must define the following objects.

• LogicalHostname resource type - This resource type is built in, and therefore you need not explicitly register the resource type.

• Oracle resource types - The Sun Cluster HA for Oracle data service 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 the Sun Cluster HA for Oracle data service: 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.