Verifying the Oracle Solaris Cluster HA for WebLogic Server Installation and Configuration

This section describes the procedure to verify if you have installed and configured your data service correctly.

How to Verify the Oracle Solaris Cluster HA for WebLogic Server Installation and Configuration for Failover Services

To verify that you have installed and configured Oracle Solaris Cluster HA for WebLogic Server correctly for a failover configuration, perform the following steps:

1. Make sure that you can successfully connect to the WebLogic Servers from a client and that both the Administration Server and the Managed Server are in the RUNNING mode.
2. Switch the resource groups to cluster-node2.

   # clresourcegroup switch cluster-node2 RG1
   # clresourcegroup switch cluster-node2 RG2

   The WebLogic Administration and Managed Servers must go offline on cluster-node1 and go online on cluster-node2. Ensure that the WebLogic Server processes on cluster-node1 are stopped. Because smooth shutdown is not enabled, the WebLogic Server process will be killed by the Oracle Solaris Cluster HA for WebLogic Server STOP method instead of being shut down smoothly. Refer to Creating a Resource That Shuts Down Smoothly for the configuration that enables smooth shutdown. For more information, see STOP Method for the configuration that enables smooth shutdown.

3. Make sure that you can successfully connect to the WebLogic Servers from the client and that both the Administration Server and the Managed Server are in the RUNNING mode.

   ---

   Note - The client sessions might be lost when the WebLogic Servers go offline on cluster-node1 and come online on cluster-node2.

   ---

4. On cluster-node2, kill the Administration Server process.

   The Fault Monitor must detect the killed process and restart the Administration Server.

5. Kill the Administration Server process repeatedly.

   The Administration Server Resource group fails over after the number of retries exceeds the retry count within the retry interval.

6. On cluster-node2, kill the Managed Server process.

   The Fault Monitor must detect the killed process and restart the Managed Server.

7. Kill the Managed Server process repeatedly.

   The Managed Server Resource group fails over after the number of retries exceeds the retry count within the retry interval.

   If the previous steps are successful, you have correctly configured Oracle Solaris Cluster HA for WebLogic Server.

Troubleshooting

After the WebLogic Administration and Managed servers are in production under Oracle Solaris Cluster control, do not start or stop the servers manually or through the Administration Console. If you need to perform maintenance on the servers, you must first disable their associated resources.

How to Verify the Oracle Solaris Cluster HA for WebLogic Server Installation and Configuration in a Multi-Master Configuration

To verify that you have installed and configured Oracle Solaris Cluster HA for WebLogic Server correctly for a multi-master configuration, perform the following steps:

1. Ensure that you can successfully connect to the WebLogic Servers from a client and that all the Managed Servers are in the RUNNING mode.
2. On one of the cluster nodes, kill the Managed Server process.

   The Fault Monitor must detect the killed process and restart the Managed Server.

3. On the WebLogic Server cluster, deploy a sample application that consists of the WebLogic servers.
4. Use a proxy web server to try to access the sample application.
5. Shut down one of the nodes and try to access the application using the proxy web server address.

   You should still be able to access the application.

   If the previous steps are successful, you have correctly configured Oracle Solaris Cluster HA for WebLogic Server in a multi-master configuration.

Troubleshooting

After the WebLogic Server managed servers are in production under Oracle Solaris Cluster control, do not start or stop the servers manually or through the Administration Console. If you need to perform maintenance on the servers, you must first disable their associated resources.