Skip Navigation Links | |
Exit Print View | |
Oracle Solaris Cluster Data Service for Sun Java System Application Server Guide Oracle Solaris Cluster |
Oracle Solaris Cluster HA for Sun Java System Application Server Overview
Highly Available Message Queue and HADB
Configuration Restrictions and Requirements
Installing and Configuring Application Server
How to Configure and Activate Network Resources
How to Install and Configure the Application Server
Verifying the Application Server Supported Versions as of 9.1 Installation and Configuration
How to Verify the Installation and Configuration of the Domain Administration Server (DAS)
Configuring the Sun Java System Web Server Plug-in
Using the Application Server With HADB
Installing the HA for Sun Java System Application Server Packages
How to Install the HA for Sun Java System Application Server Packages
Setting Oracle Solaris Cluster HA for Sun Java System Application Server Extension Properties
Configuring the SUNW.HAStoragePlus Resource Type
Tuning the Fault Monitor for Oracle Solaris Cluster HA for Sun Java System Application Server
Operations by the Fault Monitor for the DAS Component During a Probe
Fault Monitor Operations When the Monitor_Uri_List Property Is Set
Fault Monitor Operations When the Monitor_Uri_List Property Is Not Set
A. Extension Properties for HA for Sun Java System Application Server Supported Versions as of 9.1
B. Extension Properties for HA for Sun Java System Application Server Supported Versions Before 8.1
This section describes how to verify that Oracle Solaris Cluster HA for Sun Java System Application Server has been correctly installed and configured so that the Sun Java System Application Server runs as a highly available data service under Oracle Solaris Cluster.
Note - After installation, use only the cluster administration command clresourcegroup(1CL) to manually start and stop Application Server. After you start Application Server, it runs under the control of Oracle Solaris Cluster software.
The DAS resource group was created in How to Configure and Activate Network Resources.
Perform this procedure on all of the potential primary nodes or zones of the DAS component. This procedure requires a pair of nodes, indicated as Node1 and Node2.
# clresourcegroup online -n Node1 DAS-resource-group
https://IP-address:port
# clresourcegroup online -n Node2 DAS-resource-group
https://IP-address:port
If you are not able to connect to the administrative console from the browser, perform the following actions.
Ensure that your installation satisfies the restrictions and requirements in Configuration Restrictions and Requirements.
Ensure that you correctly followed the instructions in How to Install and Configure the Application Server.
The DAS fault monitor detects the unavailability of the process and restarts it locally.
Note the values of the standard resource properties Retry_count and Retry_interval. Kill the DAS process manually a number of times equal to Retry_count and within the time period Retry_interval. The DAS resource fails over to another cluster member.
If the DAS resource has not failed over, perform the following actions.
Check the values of the standard resource properties Retry_count and Retry_interval.
Ensure that you correctly followed the instructions in Installing the HA for Sun Java System Application Server Packages and in Registering and Configuring Oracle Solaris Cluster HA for Sun Java System Application Server Supported Versions as of 9.1.
This procedure is based on a configuration with four Node Agents in two resource groups, as described in Example of Creating the Failover Node Agent Component in the Oracle Solaris Cluster HA for Sun Java System Application Server. The resource groups are na-rg1 and na-rg2, the failover IP addresses are IP1 and IP2, and the eight server instances are Instance1 through Instance8. The failover IP addresses are represented by logical host names.
Perform this procedure on all of the potential primary nodes or zones of the Node Agent component. This procedure requires a pair of nodes, indicated as Node1 and Node2.
# clresourcegroup online -n Node1 na-rg1
# clresourcegroup online -n Node1 na-rg2
http://IP1:Instance1–port http://IP1:Instance2–port http://IP1:Instance3–port http://IP1:Instance4–port http://IP2:Instance5–port http://IP2:Instance6–port http://IP2:Instance7–port http://IP2:Instance8–port
If you are not able to connect to the instances from the browser, perform the following actions.
Ensure that your installation satisfies the restrictions and requirements in Configuration Restrictions and Requirements.
Ensure that you correctly followed the instructions in How to Install and Configure the Application Server.
# clresourcegroup online -n Node2 na-rg1 # clresourcegroup online -n Node2 na-rg2
When the Node Agent Process is killed, the Node Agent and all its associated server instances are restarted.
When the application server instances are killed, the Node Agent restarts them. The data service monitors the health of the Node Agent only.
Note the values of the standard resource properties Retry_count and Retry_interval. Kill the Node Agent process manually a number of times equal to Retry_count and within the time period Retry_interval. The Node Agent resource fails over to another cluster node.