Sun Cluster Data Service for Sun Java System Application Server Guide for Solaris OS

Sun Cluster HA for Sun Java System Application Server Overview

This section explains how the Sun Cluster HA for Sun Java System Application Server enables Sun Java System Application Server for high availability. Consult the Sun Cluster Data Service Release Notes for Solaris OS for new Sun Cluster HA for Sun Java System Application Server installation and configuration information.

The Sun Java System Application Server provides a high-performance Java 2 Enterprise Edition (J2EE™) 1.3 compliant platform suitable for broad deployment of application services and web services. It is designed to meet the needs of enterprise customers and can run under the control of Sun Cluster software.

The Sun Java System Message Queue is packaged with the Sun Java System Application Server installation. See Sun Cluster Data Service for Sun Java System Message Queue Guide for Solaris OS for information about configuring the Sun Java System Message Queue for high availability.

Rich clients can directly connect to the Sun Java System Application Server. Web client connections to the Sun Java System Application Server can be directed through a front-end web server. The Sun Java System Application Server provides a pass-through plugin installation for use with the Sun Java System Web Server.

Implementation of the Sun Cluster HA for Sun Java System Application Server does not assume the existence of programs on which your architecture depends. Programs on which your architecture depends such as databases and web servers should be configured to be highly available, but can run on a different cluster.

See “Planning for Sun Cluster Data Services” in Sun Cluster Data Services Planning and Administration Guide for Solaris OS and the Sun Cluster Overview for Solaris OS for general information about data services, resource groups, resources, and other related topics.

You can configure the Sun Cluster HA for Sun Java System Application Server in either of the following ways:

See How to Register and Configure the Sun Cluster HA for Sun Java System Application Server as a Failover Data Service and How to Register and Configure Sun Cluster HA for Sun Java System Application Server as a Service Mastered on Multiple Nodes for procedural information.

Failover Configuration Overview

The Sun Cluster HA for Sun Java System Application Server is a data service with appropriate extension properties to configure a failover application server mastered by one node at a time. A domain's administrative server can also be made highly available as a failover resource. Web clients can connect directly to the Sun Java System Application Server.

Use of the Sun Java System Application Server command-line or GUI administration tool is restricted in a clustered environment. Before you configure application instances and the administrative server into resource groups, see Configuration Restrictions for information about using asadmin or the Sun Java System Application Server Administrative Interface in your cluster. See “Configuration Guidelines for Sun Cluster Data Services” in Sun Cluster Data Services Planning and Administration Guide for Solaris OS for more information about configuring resources and resource groups.

Use the standard configuration in this section to plan the installation and configuration of the Sun Cluster HA for Sun Java System Application Server. The Sun Cluster HA for Sun Java System Application Server might support additional configurations. However, you must contact your Enterprise Services representative for information on additional configurations.

The following figure illustrates a standard failover configuration for a Sun Java System Application Server that runs on a two-node cluster. See Configuration Restrictions for additional information about configuring Sun Cluster HA for Sun Java System Application Server as a failover data service.

Figure 1–1 Two-Node Cluster With Failover Data Service Configuration

Illustration: The preceding context describes the graphic.

Multiple Masters Configuration Overview

You can also configure the Sun Cluster HA for Sun Java System Application Server to be mastered on multiple nodes at the same time. The multiple masters configuration provides scalability by using a front-end web tier to direct requests to the application servers. The pass-through plugin that the application server provides must be used with a front-end web tier to direct requests to one of the running Sun Java System Application Server instances.

A highly available Sun Java System Web Server is configured to run on the cluster listening on a logical hostname. If the web tier is running on the same cluster as the application server, the plugin should be configured to pass requests to the cluster private IP addresses. The Sun Java System Web Server instance can also be configured to run on a different cluster. If the web tier is running on a separate cluster, the plugin is configured to pass requests to the physical hostnames of the cluster members that can run the Sun Java System Application Server resource. An example of a physical hostname is phys-schost-1.

The Sun Cluster HA for Sun Java System Application Server configurations that are mastered on multiple nodes can use the private interconnect to direct traffic between the Sun Java System Web Server to the Sun Java System Application Server.


Note –

If you configure the Sun Cluster HA for Sun Java System Application Server as a service that is mastered on multiple nodes at the same time, you must install and configure the Sun Java System Web Server. The Sun Java System Web Server configuration must be the same on all cluster nodes.


Multiple instances of the Sun Java System Application Server can be load balanced. To enable load-balancing, install the Sun Java System Application Server plugin into the Sun Java System Web Server configuration. The Sun Java System Web Server can be configured as a failover or scalable resource when it is used as a front-end to the Sun Java System Application Server.

The Sun Java System Application Server instance is configured so that its HTTP Listeners listen on all interfaces (0.0.0.0), which is the default for Sun Java System Application Servers.


Note –

For a data service mastered on multiple nodes, the IIOP listeners are not highly available.


The following figure illustrates a configuration for a Sun Java System Application Server that masters the resource on two nodes at the same time.

Figure 1–2 Two-Node Cluster With Data Service Mastered on Multiple Nodes

Illustration: The preceding context describes the graphic.