Skip Navigation Links | |
Exit Print View | |
Oracle Solaris Cluster Data Service for Sun Java System Application Server Guide |
Oracle Solaris Cluster HA for Sun Java System Application Server Overview
Highly Available Message Queue and HADB
Configuration Restrictions and Requirements
Installing and Configuring Sun Java System Application Server
How to Configure and Activate Network Resources
How to Install and Configure the Sun Java System Application Server
How to Verify the Installation and Configuration of the Domain Administration Server (DAS)
Configuring the Sun Java System Web Server Plugin
Using the Sun Java System Application Server With HADB
Installing the Solaris Cluster HA for Sun Java System Application Server Packages
How to Install the Solaris Cluster 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
This section describes installation and configuration of the Sun Java System Application Server. Only the information that is specific to the Oracle Solaris Cluster HA for Sun Java System Application Server is included here. See the Sun Java System Application Server documentation for detailed installation instructions, including patch requirements.
Note - The Sun Java System Application Server can be configured to run in a whole root or a sparse root non-global zone, if required.
Note - Before starting your installation, set the JMS-service entry in the domain.xml file to REMOTE.
To enable the components in Sun Java System Application Server to run in Oracle Solaris Cluster, you must set up the network resources for those components.
The failover IP address is the network resource for the DAS resource.
# clresourcegroup create [-n node-zone-list] DAS-resource-group
Specifies the name of the DAS resource group. This name can be your choice.
Specifies a comma-separated, ordered list of zones that can master this resource group. The format of each entry in the list is node. In this format, node specifies the node name and zone specifies the name of a non-global Solaris zone. To specify the global zone, or to specify a node without non-global zones, specify only node.
This list is optional. If you omit this list, the global zone of each cluster node can master the resource group.
Use the following command to add the failover IP address to the DAS resource group.
# clreslogicalhostname create -g DAS-resource-group -h IP-address IP-address
Specifies the name of the DAS resource group.
Specifies the failover IP address that is the network resource in this resource group.
Note - If you require a fully qualified hostname, you must specify the fully qualified name with the -h option and you cannot use the fully qualified form in the resource name.
Bringing online this resource group enables the failover IP address resource for DAS.
# clresourcegroup online DAS-resource-group
Specifies the name of the DAS resource group.
To create a failover resource group for Node Agent, run the following command.
# clresourcegroup create [-n node-zone-list NA-resource-group]
# clreslogicalhostname create -g NA-resource-group -h logical-hostname logical-hostname
Note - If you require a fully qualified hostname, you must specify the fully qualified name with the -h option and you cannot use the fully qualified form in the resource name.
Bringing online these resource groups enables the failover logical host resources for the Node Agents.
# clresourcegroup online NA-resource-group
The Sun Java System Application Server can be installed on the local file system or on the global file system.
The extension property Domaindir for the SUNW.jsas resource type specifies the path to the domain directory. See SUNW.jsas Extension Properties.
In the server-config entry in the file domain.xml, change the DAS HTTP, HTTPS, IIOP, and all other listener addresses to the failover IP address that you intend to use in the Oracle Solaris Cluster DAS resource.
Note - Before you modify the file domain.xml, remember to stop all the instances of DAS and Node Agents.
When the Node Agents and Sun Java System Application Server instances are created, the physical node addresses are set by default in the file domain.xml. Therefore, you must change the physical addresses to the failover logical host names that you plan to use for the Node Agents.
The file nodeagent.properties in the Node Agent configuration directory contains the entry agent.client.host=hostname, where hostname specifies the Oracle Solaris Cluster node on which Node-Agent-name is configured to run, and where Node-Agent-name is the name of a particular Node Agent.