Oracle^® Solaris Cluster Data Service for Oracle Communications ASAP Guide

How to Register and Configure Oracle Communications ASAP for Failover

Use this procedure to configure Oracle Solaris Cluster HA for Oracle Communications ASAP as a failover data service. The following steps assume that you have configured the Oracle Communications ASAP as described in Installing and Configuring the Oracle Communications ASAP Resource.

Before You Begin

Install the data service package during your initial Oracle Solaris Cluster installation. If you did not install the Oracle Communications ASAP package as part of your initial Oracle Solaris installation, go to How to Install the HA for Oracle Communications ASAP Package.

1. On the cluster node that hosts the Oracle Communications ASAP, assume the root role that provides solaris.cluster.modify and solaris.cluster.admin RBAC authorizations.
2. Register the ORCL.asap resource type.

   # clresourcetype register ORCL.asap

3. Create a Oracle Communications ASAP resource in the failover resource group.

   If you are configuring HA for Oracle Communications ASAP deployed on a single unix server, use the following command:

   # clresource create -g asap-app-rg -d \
   -t ORCL.asap \
   -p ASAP_HOME=asap-home-directory \
   -p Control_Server_Type=MASTER \
   -p Master_Control=asap-master-control-server-name \
   -p resource_dependencies=logicalhost-resource,weblogic-rs,db-rs \
   -p resource_dependencies_offline_restart=hasp-rs asap-app-rs

   ASAP_HOME

   Location of ASAP installation

   Control_Server_Type

   Type of control server

   Master_Control

   Name of the Master Control Server

   If you are configuring HA for Oracle Communications ASAP deployed over several unix machines, use the following command:

   # clresource create -g asap-slave-rg -d \
   -t ORCL.asap \
   -p ASAP_HOME=asap-slave-home-directory \
   -p Control_Server_Type=SLAVE \
   -p Master_Control=asap-master-control-server-name \
   -p Slave_Control=asap-slave-control-server-name \
   -p resource_dependencies=slave-logicalhost-resource,weblogic-rs,db-rs \
   -p resource_dependencies_offline_restart=slave-hasp-rs,asap-app-rs asap-slave-rs

   where Slave_Control is the name of the Slave Control Server name. For more information about extension properties, see Appendix A, Oracle HA for Oracle Communications ASAP Extension Properties.

   The ASAP resource with Control_Server_Type=SLAVE should have an offline_restart dependency on the ASAP resource with Control_Server_Type=MASTER. If you are using the scalMountPoint storage resource, you must set the offline-restrat dependency on the scalmnt-rs resource.

4. Enable the Oracle Communications ASAP resource.

   # clresource status
   # clresource enable asap-app-rs
   # clresource enable asap-slave-rs