|Skip Navigation Links|
|Exit Print View|
|Oracle Solaris Cluster Data Service for Sun Java System Application Server Guide Oracle Solaris Cluster|
This section describes installation of the 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 Application Server documentation for detailed installation instructions, including patch requirements.
If you configure Application Server as a failover service, you must set up the network resources before you install and configure the Application Server. The failover service uses these network resources after installation and configuration in order to run in a cluster.
To perform this procedure, you need the following information about your configuration.
The names of the cluster nodes that can master the data service.
The hostnames that are used for configuring the network resource that clients use to access the Application Server. Normally, you set up this hostname when you install the cluster. See the Solaris Cluster Concepts Guide for Solaris OS for details on network resources.
Note - Perform this procedure on any cluster member.
You should have performed this verification during the Oracle Solaris Cluster installation. See the planning chapter in the Solaris Cluster Software Installation Guide for Solaris OS.
Note - To avoid name service look-up failures, ensure that all of the logical hostnames are present in the /etc/inet/hosts file on all of the cluster nodes. Configure name service mapping in the /etc/nsswitch.conf file on the servers to check the local files before trying to access NIS, NIS+, or DNS.
# clresourcegroup create [-n node-zone-list] resource-group
Specifies the name of the 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 a logical hostname to a resource group.
# clreslogicalhostname create -g resource-group -h hostname,…[-N netiflist]
Specifies the name of the resource group.
Specifies a comma-separated list of network resources.
Specifies an optional, comma-separated list that identifies the IPMP groups that are on each node or zone. The format of each entry in the list is netif@node. The replaceable items in this format are as follows:
Specifies an IPMP group name, such as sc_ipmp0, or a public network interface card (NIC). If you specify a public NIC, Oracle Solaris Cluster attempts to create the required IPMP groups.
Specifies the name or ID of a node. 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, Oracle Solaris Cluster attempts to create the required IPMP groups.
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.
Note - Oracle Solaris Cluster does not currently support the use of the adapter name for netif.
# clresourcegroup online resource-group
You can either create a link to the server configuration directory or specify the full path to the location on the global file system when you create the Application Server domains in Step 3.
# ln -s /global/appserver /var/opt/SUNWappserver7
# asadmin create-domain --path /global/appserver/domains \ --adminport=4848 --adminuser admin --adminpassword password scdomain
For the Application Server instance to work correctly, the log directory must be located on each node of the cluster, not on the cluster file system. Choose a location on the local disk that is the same for all the nodes in the cluster.
schost-1# mkdir -p /var/pathname/domain/instance/logs/
Note - If you anticipate large log files, ensure that the file system containing the directory has enough space to handle the files.
This operation must be performed on the primary node of the logical host.
The correct server name is usually the hostname that clients will use to access the resources on the application server.
If the administrative server is to be made highly available, configure only the HTTP listener, the administrative server does not have an IIOP listener.
If the server does not start, correct the problem. See the Application Server documentation for details.
You must stop the server before you proceed to the next part of the installation and configuration process.