Skip Navigation Links | |
Exit Print View | |
Oracle GlassFish Server 3.1-3.1.1 High Availability Administration Guide |
1. High Availability in GlassFish Server
2. Setting Up SSH for Centralized Administration
3. Administering GlassFish Server Nodes
4. Administering GlassFish Server Clusters
To Preconfigure Nondefault GMS Configuration Settings
To Change GMS Settings After Cluster Creation
To Check the Health of Instances in a Cluster
To Validate That Multicast Transport Is Available for a Cluster
Using the Multi-Homing Feature With GMS
Traffic Separation Using Multi-Homing
Creating, Listing, and Deleting Clusters
To List All Clusters in a Domain
5. Administering GlassFish Server Instances
6. Administering Named Configurations
7. Configuring Web Servers for HTTP Load Balancing
8. Configuring HTTP Load Balancing
9. Upgrading Applications Without Loss of Availability
10. Configuring High Availability Session Persistence and Failover
11. Configuring Java Message Service High Availability
A cluster is a named collection of GlassFish Server instances that share the same applications, resources, and configuration information. For information about GlassFish Server instances, see Chapter 5, Administering GlassFish Server Instances.
GlassFish Server enables you to administer all the instances in a cluster as a single unit from a single host, regardless of whether the instances reside on the same host or different hosts. You can perform the same operations on a cluster that you can perform on an unclustered instance, for example, deploying applications and creating resources.
A cluster provides high availability through failure protection, scalability, and load balancing.
Failure protection. If an instance or a host in a cluster fails, GlassFish Server detects the failure and recovers the user session state. If a load balancer is configured for the cluster, the load balancer redirects requests from the failed instance to other instances in the cluster. Because the same applications and resources are on all instances in the cluster, an instance can fail over to any other instance in the cluster.
To enable the user session state to be recovered, each instance in a cluster sends in-memory state data to another instance. As state data is updated in any instance, the data is replicated.
Scalability. If increased capacity is required, you can add instances to a cluster with no disruption in service. When an instance is added or removed, the changes are handled automatically.
Load balancing. If instances in a cluster are distributed among different hosts, the workload can be distributed among the hosts to increase overall system throughput.