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

Oracle Solaris Cluster HA for Sun Java System Application Server Overview

Highly Available Components

Highly Available DAS and NA

Highly Available Message Queue and HADB

Supported Configurations

Before Node Failure

After Node Failure

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 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)

How to Verify the Installation and Configuration of the Node Agents Configured as a Failover Data Service

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

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

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

How to Register and Configure Oracle Solaris Cluster HA for Sun Java System Application Server as a Failover DAS Component and a Failover NA Component

Examples of Registering and Configuring the Failover DAS Component in the Oracle Solaris Cluster HA for Sun Java System Application Server

Example of Creating the Failover Node Agent Component in the Oracle Solaris Cluster HA for Sun Java System Application Server

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

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

How to Verify the Failover DAS Component

How to Verify the Failover Node Agent Component

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

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

Verifying the Application Server Supported Versions as of 9.1 Installation and Configuration

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.

How to Verify the Installation and Configuration of the Domain Administration Server (DAS)

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.

  1. On Node1, start DAS manually, using the asadmin command.

    Note - The DAS must have been configured to listen on the failover IP address IP-address.


  2. Connect to the administrative console from a browser.
    https://IP-address:port
  3. Verify that you are connected to the administrative console.
  4. On Node1, stop DAS manually, using the asadmin command.
  5. Switch the DAS resource group from Node1 to Node2.
    # 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.

  6. On Node2, start DAS manually, using the asadmin command.
  7. Connect to the administrative console from a browser.
    https://IP-address:port

    If you are not able to connect to the administrative console from the browser, perform the following actions.

  8. On Node2, stop DAS manually, using the asadmin command.

How to Verify the Installation and Configuration of the Node Agents Configured as a Failover Data Service

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.

  1. On Node1, start the Node Agent manually using the asadmin command.

    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.


  2. Connect to the server instances from a browser.
    http://logical-hostname:instance1-port
    http://logical-hostname:instance2-port
  3. Ensure that you can connect to any application deployed on the server instance.
  4. If you are not able to connect to an application deployed on the server instance, perform the following steps.
  5. On Node1, stop the Node Agent by using the asadmin command.

    This step stops all the server instances that are configured for this Node Agent.

  6. Switch the Node Agent resource group from Node1 to Node2.
    # 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.

  7. On Node2, start the Node Agent manually by using the asadmin command.

    This step starts the Node Agent and all the server instances that are configured for this Node Agent.

  8. Connect to the server instances from a browser.
    http://logical-hostname:instance1-port
    http://logical-hostname:instance2-port
  9. If you are not able to connect to the server instance from the browser, perform the following steps.
  10. After successfully verifying the configuration, stop the Node Agent and all the server instances on Node2 by using the asadmin command.