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

Verifying the Oracle Communications ASAP Installation and Configuration

This section contains the procedure to verify the Oracle Communications ASAP installation and configuration.

How to Verify the Oracle Communications ASAP Installation and Configuration for Failover Services

Use this procedure to verify the Oracle Communications ASAP installation and configuration. This procedure does not verify that your application is highly available because you have not yet installed the data service.

1. Ensure that all the logical hostname resources are online.
2. Ensure that weblogic server resources and database resources are online.
3. Assume the root role and log into the node that currently hosts the Oracle Communications ASAP resource group and start the Oracle Communications ASAP.

   If you are configuring the HA for Oracle Communications ASAP deployed on single UNIX machine, the following command would start a single control server and the application processes managed by the Control Server. If you are configuring HA for Oracle Communications ASAP deployed across several UNIX machines, this command would start the Master Control Server, all the configured Slave Control Servers and the application processes managed by all the control servers.

   # su - $Application_User -c “. $ASAP_HOME/Environment_Profile;$ASAP_HOME/scripts/start_asap_sys  -d”   
     

   Application_User

   Installation user of Oracle Communications ASAP

   ASAP_HOME

   Installation directory of Oracle Communications ASAP software

   Environment_Profile

   Default environment script that sets the environment for running ASAP servers.

4. Verify the status of the Oracle Communications ASAP.

   # su - $Application_User -c “. $ASAP_HOME/Environment_Profile;$ASAP_HOME/scripts/status"
   

   Application_User

   Installation user of Oracle Communications ASAP

   ASAP_HOME

   Installation directory of Oracle Communications ASAP software

   Environment_Profile

   Default environment script that sets the environment for running ASAP servers

   Verify that all the server processes you wanted to start appear in the output. For instructions about verifying Oracle Communications ASAP installation, see Oracle Communications ASAP Installation Guide.

5. Stop the Oracle Communications ASAP.

   # su - $Application_User -c “. $ASAP_HOME/Environment_Profile;$ASAP_HOME/scripts/stop_asap_sys  -d”

   If you have deployed ASAP on a single UNIX machine, this command stops the Control Server and the application processes managed by the control server. If you have deployed ASAP over several UNIX machines, this command stops the Master Control Server and all the configured Slave Control Servers and the application processes managed by all the control servers.

6. Switch the Oracle Communications ASAP resource group to another cluster member.

   • Use the following command if you have deployed ASAP on a single unix machine:

     # clresourcegroup switch -n node asap-app-rg

   • Use the following command if you have deployed ASAP on several unix machines:

     Switch the Master Control resource group to another node:

     # clresourcegroup switch -n node asap-app-rg

     Switch all the Slave Control Servers resource groups to another node:

     # clresourcegroup switch -n node asap-slave-rg

     This example displays the commands used for a single Slave Control Server resource group.

7. Repeat all steps until you have tested all the potential nodes where the Oracle Communications ASAP can run.

   If the clients can successfully connect to the Oracle Communications ASAP on each of the potential master nodes, you have successfully configured theOracle Communications ASAP to work with the HA for Oracle Communications ASAP.

8. Stop the Oracle Communications ASAP and proceed to How to Install the HA for Oracle Communications ASAP Package.