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
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
The following procedures explain how to use the Oracle Solaris Cluster maintenance commands to register and configure the Oracle Solaris Cluster HA for Sun Java System Application Server. These instructions explain how to set the extension properties described in Appendix A, Extension Properties for HA for Sun Java System Application Server Supported Versions as of 9.1.
Both the DAS component and the Node Agent (NA) component are configured as failover services.
Note - See Tools for Data Service Resource Administration in Oracle Solaris Cluster Data Services Planning and Administration Guide for general information about registering and configuring data services.
The sections that follow contain instructions for registering and configuring resources. These instructions explain how to set only extension properties that Oracle Solaris Cluster HA for Sun Java System Application Server requires you to set. For information about all Oracle Solaris Cluster HA for Sun Java System Application Server extension properties, see Appendix A, Extension Properties for HA for Sun Java System Application Server Supported Versions as of 9.1. You can update some extension properties dynamically. You can update other properties, however, only when you create or disable a resource. The Tunable entry indicates when you can update a property.
To set an extension property of a resource, include the following option in the clresource(1CL) command that creates or modifies the resource:
-p property=value
Identifies the extension property that you are setting.
Specifies the value to which you are setting the extension property.
You can also use the procedures in Chapter 2, Administering Data Service Resources, in Oracle Solaris Cluster Data Services Planning and Administration Guide to configure resources after the resources are created.
Note that in How to Configure and Activate Network Resources you previously created the failover resource groups for the DAS component and for the NA component, added failover IP addresses and logical hosts to the resource groups, and brought the resource groups online.
# clresourcetype register SUNW.jsas
See SUNW.jsas Extension Properties for a detailed description of the extension properties for this resource type.
# clresource create DAS-resource-group \ -t SUNW.jsas \ -p Network_resources_used=logical-hostname \ -p Adminuser=DAS-admin-username \ -p Domain_name=domain-name \ -p Passwordfile=password-file \ -p Confdir_list=install-directory \ -p Domaindir=domain-directory DAS-resource
Specifies the resource group for the DAS component.
Specifies the resource type for the DAS component.
Specifies the failover IP address that is used by DAS.
Specifies DAS administrative user name.
Specifies the domain name.
Specifies the full path to the file containing the DAS administrative password and master password.
Specifies the complete path to the Application Server installation directory. The default value for this extension property is /opt/SUNWappserver, which is the standard installation directory.
Specifies the full path to the domain directory. This extension property is optional if the domain directory is the default directory that was specified at the installation of the Application Server.
Specifies the DAS resource name.
The resource is created in the enabled state.
# clresourcetype register SUNW.jsas-na
SeeSUNW.jsas-na Extension Properties for a detailed description of the extension properties for this resource type.
# clresource create -g NA-resource-group \ -t SUNW.jsas-na \ -p Resource_Dependencies=DAS-resource \ -p Adminuser=DAS-admin-username \ -p Confdir_list=install-directory \ -p Adminhost=DAS-hostname \ -p Adminport=DAS-port \ -p Agentdir=NA-directory \ -p Passwordfile=password-file NA-resource
Specifies the resource group for the Node Agent component.
Specifies the resource type for the Node Agent component.
Specifies that the DAS resource must be online before the Node Agent resource can start.
Specifies DAS administrative user name.
Specifies the complete path to the Application Server installation directory. The default value for this extension property is /opt/SUNWappserver, which is the standard installation directory.
Specifies the host name of the DAS.
Specifies the port where DAS listens.
Specifies the full path to the Node Agents directory.
Specifies the full path to the file containing the DAS administrative password and master password.
Specifies the Node Agent resource name.
The resource is created in the enabled state.
These examples assume that the DAS resource group has already been created, the failover IP address has been added to the resource group, and the resource group has been brought online.
Example 1-1 Creating a Simple DAS Resource
In this example, the default values for the extension properties are used.
# clresourcetype register SUNW.jsas
# clresource create -g das-rg \ -t SUNW.jsas \ -p Network_resources_used=IP1 \ -p Adminuser=admin \ -p Domain_name=domain1 \ -p Passwordfile=/global/disk1/passwordfile das-rs
In this example, the following values are set.
The resource name is das-rs.
The resource group is das-rg.
The administrative user is admin.
The domain name is domain1.
The full path to the password file is /global/disk1/passwordfile.
The Application Server is assumed to be installed in the standard location /opt/SUNWappserver, which is the default value of the extension property Confdir_list.
The domain is assumed to be installed in the path that you set at the time of installation. This path is defined by the variable AS_DEF_DOMAINS in the file /opt/SUNWappserver/appserver/config/asenv.conf. The binaries can be stored in the local file system, but the domain directory must be in the global file system.
Example 1-2 Creating a DAS Resource by Specifying the Installation Directory and the Domain Directory
In this example, the Application Server is not installed in the default location and the domain directory is not the default.
# clresourcetype register SUNW.jsas
# clresource create -g das-rg \ -t SUNW.jsas \ -p Network_resources_used=IP1 \ -p Adminuser=admin \ -p Domain_name=domain1 \ -p Passwordfile=/global/disk1/passwordfile \ -p Confdir_list=/global/disk1/SUNWappserver \ -p Domaindir=/global/disk1/my-domain das-rs
In this example, the following values are set.
The resource name is das-rs.
The resource group is das-rg.
The administrative user is admin.
The domain name is domain1.
The full path to the password file is /global/disk1/passwordfile.
The Application Server is installed in the directory /global/disk1/SUNWappserver.
The domain directory is /global/disk1/my-domain.
Example 1-3 Creating a DAS Resource and Specifying a List of URIs to be Monitored
In this example, the extension property Monitor_Uri_List specifies the URI that is serviced by applications on the Application Server. The fault monitor probe monitors this URI to test the functionality of the Application Server.
# clresourcetype register SUNW.jsas
# clresource create -g das-rg \ -t SUNW.jsas \ -p Network_resources_used=IP1 \ -p Adminuser=admin \ -p Domain_name=domain1 \ -p Passwordfile=/global/disk1/passwordfile \ -p Confdir_list=/global/disk1/SUNWappserver \ -p Domaindir=/global/disk1/my-domain \ -p Monitor_Uri_List=http://IP1:4848/web-service das-rs
In this example, the following values are set.
The resource name is das-rs.
The resource group is das-rg.
The administrative user is admin.
The domain name is domain1.
The full path to the password file is /global/disk1/passwordfile.
The Application Server is installed in the directory /global/disk1/SUNWappserver.
The domain directory is /global/disk1/my-domain.
The URI to be monitored is http://IP1:4848/web-service.
The example in this section assumes the following configuration, where failover IP addresses are represented by logical host names.
Node Agent NA1 and its associated server instances I1 and I2 are configured to listen on failover IP address IP1.
Node Agent NA2 and its associated server instances I3 and I4 are also configured to listen on failover IP address IP1.
Node Agent NA3 and its associated server instances I5 and I6 are configured to listen on failover IP address IP2.
Node Agent NA4 and its associated server instances I7 and I8 are also configured to listen on failover IP address IP2.
Example 1-4 Creating Failover Node Agent Resources
To register the resource type for the Node Agents, the following command is run.
# clresourcetype register SUNW.jsas-na
To create the failover resource group na-rg1 to contain the failover IP address IP1 and the Node Agent resource for Node Agents NA1 and NA2, the following command is run.
# clresourcegroup create na-rg1
To create the failover resource group na-rg2 to contain the failover IP address IP2 and the Node Agent resource for Node Agents NA3 and NA4, the following command is run.
# clresourcegroup create na-rg2
To add the failover IP address resource IP1 to the resource group na-rg1, the following command is run.
# clreslogicalhostname create -g na-rg1 -h IP1 IP1
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.
To add the failover IP address resource IP2 to the resource group na-rg2, the following command is run.
# clreslogicalhostname create -g na-rg2 -h IP2 IP2
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.
To create the Node Agent resource na-rs1 in resource group na-rg1, the following command is run.
Note - Only one Node Agent resource is created for all the Node Agents configured for one failover IP address. The data service automatically detects the Node Agents that are configured on the failover IP address that is created in the failover resource group.
In this example, Node Agents NA1 and NA2 and all their server instances (I1, I2, I3, and I4) are configured on IP1, and therefore only one resource, na-rs1 is created for NA1 and NA2.
Run this command if you use the default values for the extension properties.
# clresource create -g na-rg1 \ -t SUNW.jsas-na \ -p Resource_Dependencies=das-rs \ -p Adminhost=host-1 \ -p Adminuser=admin \ -p Agentdir=/global/dg1/na-dir \ -p Passwordfile=/global/dg1/p na-rs1
Run this command if the installation is not in the default location, and the administrative port is not the default value.
# clresource create -g na-rg1 \ -t SUNW.jsas-na \ -p Resource_Dependencies=das-rs \ -p Adminhost=host-1 \ -p Adminuser=admin \ -p Agentdir=/global/dg1/na-dir \ -p Passwordfile=/global/dg1/p \ -p Confdir_list=/global/disk1/appserver-install-dir \ -p Adminport=6162 na-rs1
The resource is created in the enabled state.
To create the Node Agent resource na-rs2 in resource group na-rg2, the following command is run.
Note - Only one Node Agent resource is created for all the Node Agents configured for one failover IP address. The data service automatically detects the Node Agents that are configured on the failover IP address that is created in the failover resource group.
In this example, Node Agents NA3 and NA4 and all their server instances (I5, I6, I7, and I8) are configured on IP2, and therefore only one resource, na-rs2 is created for NA3 and NA4.
Run this command if you use the default values for the extension properties.
# clresource create -g na-rg2 \ -t SUNW.jsas-na \ -p Resource_Dependencies=das-rs \ -p Adminhost=host-1 \ -p Adminuser=admin \ -p Agentdir=/global/dg1/na-dir \ -p Passwordfile=/global/dg1/p na-rs2
Run this command if the installation is not in the default location, and the administrative port is not the default value.
# clresource create -g na-rg2 \ -t SUNW.jsas-na \ -p Resource_Dependencies=das-rs \ -p Adminhost=host-1 \ -p Adminuser=admin \ -p Agentdir=/global/dg1/na-dir \ -p Passwordfile=/global/dg1/p \ -p Confdir_list=/global/disk1/appserver-install-dir \ -p Adminport=6162 na-rs2
The resource is created in the enabled state.
To bring the Node Agent resource group na-rg1 online, the following command is run.
# clresourcegroup online na-rg1
By bringing online the resource group na-rg1, you enable the following resources.
Node Agent NA1 and server instances I1 and I2, which are configured under NA1.
Node Agent NA2 and server instances I3 and I4, which are configured under NA2.
To bring the Node Agent resource group na-rg2 online, the following command is run.
# clresourcegroup online na-rg2
By bringing online the resource group na-rg2, you enable the following resources.
Node Agent NA3 and server instances I5 and I6, which are configured under NA3.
Node Agent NA4 and server instances I7 and I8, which are configured under NA4.