JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris Cluster Data Service for Sun Java System Application Server Guide     Oracle Solaris Cluster
search filter icon
search icon

Document Information

Preface

1.  Installing and Configuring Oracle Solaris Cluster HA for Sun Java System Application Server Supported Versions as of 9.1

2.  Installing and Configuring Oracle Solaris Cluster HA for Sun Java System Application Server Supported Versions Before 8.1

Oracle Solaris Cluster HA for Sun Java System Application Server Overview

Failover Configuration Overview

Multiple Masters Configuration Overview

Overview of the Installation and Configuration Process for Oracle Solaris Cluster HA for Sun Java System Application Server

Planning the Oracle Solaris Cluster HA for Sun Java System Application Server Installation and Configuration

Configuration Restrictions

Configuration Planning Questions

Installing and Configuring Application Server

How to Configure and Activate Network Resources for a Failover Configuration

How to Install and Configure the Application Server

Using the Application Server With HADB

Configuring the Sun Java System Web Server Plug-in

Installing the HA for Sun Java System Application Server Packages

Registering and Configuring Oracle Solaris Cluster HA for Sun Java System Application Server Supported Versions Before 8.1

Setting Oracle Solaris Cluster HA for Sun Java System Application Server Extension Properties

How to Register and Configure the Oracle Solaris Cluster HA for Sun Java System Application Server as a Failover Data Service

How to Register and Configure the Oracle Solaris Cluster HA for Sun Java System Application Server as a Data Service Mastered on Multiple Nodes

Configuring the SUNW.HAStoragePlus Resource Type

Tuning the Fault Monitor for Oracle Solaris Cluster HA for Sun Java System Application Server

Operations by the Oracle Solaris Cluster HA for Sun Java System Application Server Fault Monitor During a Probe

Verifying the Oracle Solaris Cluster HA for Sun Java System Application Server Installation and Configuration

How to Verify the Oracle Solaris Cluster HA for Sun Java System Application Server Installation and Configuration

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

Index

Installing and Configuring Application Server

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.

How to Configure and Activate Network Resources for a Failover Configuration

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.


Note - Perform this procedure on any cluster member.


  1. On a cluster member, become superuser or assume a role that provides solaris.cluster.modify and solaris.cluster.admin RBAC authorization.
  2. Verify that all of the network addresses that you use have been added to your name service database.

    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.


  3. Create a failover resource group to contain the network and application resources.
    # clresourcegroup create [-n node-zone-list] resource-group
    resource-group

    Specifies the name of the resource group. This name can be your choice.

    [-n node-zone-list]

    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.

  4. Add network resources to 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]
    -g resource-group

    Specifies the name of the resource group.

    -h hostname, …

    Specifies a comma-separated list of network resources.

    -N netiflist

    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:

    netif

    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.

    node

    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.


  5. Bring the resource group online.
    # clresourcegroup online resource-group

How to Install and Configure the Application Server

  1. On a cluster member, become superuser or assume a role that provides solaris.cluster.admin RBAC authorization.
  2. (Optional) On all nodes, create a link to the server configuration directory on the global file system from the default configuration directory.

    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
  3. Create a domain with configuration information on the global file system.
    # asadmin create-domain --path /global/appserver/domains \
    --adminport=4848 --adminuser admin --adminpassword password scdomain
  4. Start the domains administrative server.
    # /global/appserver/domains/scdomain/admin-server/bin/startserv
  5. Create new application server instances to be made highly available by using the administrative server.
  6. Create a log directory on the local disk for each node that the Application Server instance uses.

    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.


  7. Change the location of the Application Server instance PidLog to reflect the directory that you created in Step 6. To change the location, edit the init.conf file located in the server configuration directory.
  8. Change the location of PID_FILE in the stopserv file to match the value of PidLog that you set in Step 7.
  9. Change the location of the Log File, Log Root, and Transaction Log Location parameters to reflect the directory that you created in Step 6. To change these parameters, use the Application Server Administrative Interface. For instructions on configuration, see the Application Server documentation.
  10. Change the location of the accesslog parameter to reflect the directory that you created in Step 6. To change this parameter, use the asadmin utility. See the Application Server documentation for instructions.
  11. Ensure that any logical hostnames that the application server uses are configured and are online.
  12. If the application server is configured as a failover service, configure the HTTP listener IP address with the logical IP address and the server name with the logical hostname. If the application server is configured as a service mastered on multiple nodes, proceed to Step 14.

    This operation must be performed on the primary node of the logical host.

  13. If the application server is configured as a service mastered on multiple nodes, configure the HTTP listener IP address to 0.0.0.0 and Return Server Name to localhost.
  14. Verify that the HTTP listener is returning the correct server name.

    The correct server name is usually the hostname that clients will use to access the resources on the application server.

  15. If the application server is configured as a failover service, configure the IIOP listener with the logical IP address for the Oracle Solaris Cluster HA for Sun Java System Application Server instance. If the application server is configured as a service mastered on multiple nodes, proceed to Step 16.

    If the administrative server is to be made highly available, configure only the HTTP listener, the administrative server does not have an IIOP listener.

  16. Disable the Application Server startup of the Message Queue server by unchecking Start Enable for the services under JMS.
  17. Start the application server by issuing the startserv command.
    # /global/appserver/domains/scdomain/server1/bin/startserv

    If the server does not start, correct the problem. See the Application Server documentation for details.

  18. Stop the application server by issuing the stopserv command.
    # /global/appserver/domains/scdomain/server1/bin/stopserv

    You must stop the server before you proceed to the next part of the installation and configuration process.