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
How to Verify the Failover DAS Component
How to Verify the Failover Node Agent Component
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
Before you install the HA for Sun Java System Application Server package, verify that the Sun Java System Application Server software is correctly installed and configured to run in a cluster. These procedures do not verify that the Sun Java System Application Server application is highly available because you have not yet installed your data service and the application is not yet under cluster control.
In this procedure, a two-node cluster is used, where the nodes are identified as Node1 and Node2. The following actions were performed in How to Configure and Activate Network Resources.
The failover DAS resource group DAS-resource-group was created.
The failover IP address IP-address was added as a network resource to the resource group.
The resource group was brought online, and the resources were enabled.
Note - The DAS must have been configured to listen on the failover IP address IP-address.
https://IP-address:port
# clresourcegroup online -n Node2 DAS-resource-group
This step takes the resource group offline from Node1 and brings the same resource group online on Node2. The resource group includes the logical IP address IP-address.
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.
In this procedure, a two-node cluster is used, where the nodes are identified as Node1 and Node2. The following actions were performed in How to Configure and Activate Network Resources.
The failover Node Agent resource group NA-resource-group was created.
The failover logical host logical-hostname was added as a network resource to the resource group.
The resource group was brought online, and the resources were enabled.
This step starts the Node Agent and all the server instances that are configured for this Node Agent.
Note - The Node Agent and the server instances are configured to listen on the failover logical host that is configured in the failover resource group NA-resource-group.
http://logical-hostname:instance1-port
http://logical-hostname:instance2-port
Ensure that the server instances and the Node Agent are configured correctly to listen on the logical host logical-hostname.
Ensure that your installation satisfies the restrictions and requirements described in Configuration Restrictions and Requirements.
Ensure that you correctly followed the instructions in How to Install and Configure the Application Server.
This step stops all the server instances that are configured for this Node Agent.
# clresourcegroup online -n Node2 NA-resource-group
This step takes the resource group offline from Node1 and brings the same resource group online on Node2. The resource group includes the logical host logical-hostname.
This step starts the Node Agent and all the server instances that are configured for this Node Agent.
http://logical-hostname:instance1-port
http://logical-hostname:instance2-port
Ensure that the server instances and the Node Agent are configured correctly to listen on the logical host logical-hostname.
Ensure that your installation satisfies the restrictions and requirements described in Configuration Restrictions and Requirements.
Ensure that you correctly followed the instructions in How to Install and Configure the Application Server.