To Set Up High Availability Session Persistence

Before You Begin

High availability session persistence is incompatible with dynamic deployment, dynamic reloading, and autodeployment. These features are for development, not production environments, so you must disable them before enabling HA session persistence. For information about how to disable these features, see Sun GlassFish Enterprise Server 2.1 Application Deployment Guide.

1. Create an Enterprise Server cluster.

   For more information, see To Create a Cluster .

2. If you are using HADB to store session state data, create an HADB database for the cluster.

   ---

   Note –

   The HADB software is supplied with the Enterprise Server standalone distribution of Sun GlassFish Enterprise Server. For information about available distributions of Sun GlassFish Enterprise Server, see Distribution Types and Their Components in Sun GlassFish Enterprise Server 2.1 Installation Guide. HADB features are available only in the enterprise profile. For information about profiles, see Usage Profiles in Sun GlassFish Enterprise Server 2.1 Administration Guide.

   ---

   If you are using in-memory replication on other servers in the cluster for session state data, omit this step.

   For more information about creating an HADB database, see configure-ha-cluster(1).

3. Set up load balancing for the cluster.

   For more information , see Setting Up HTTP Load Balancing.

4. Enable availability for the desired application server instances and web or EJB containers.

   Then configure the session persistence settings. Choose one of these approaches:

   • Use Admin Console. See Enabling Availability for a Server Instance.

   • Use the asadmin command-line utility. See set(1) and configure-ha-persistence(1).

5. Restart each server instance in the cluster.

   If the instance is currently serving requests, quiesce the instance before restarting it so that the instance gets enough time to serve the requests it is handling. For more information, see Disabling (Quiescing) a Server Instance or Cluster

6. Enable availability for any specific SFSB that requires it.

   Select methods for which checkpointing the session state is necessary. See Configuring Availability for an Individual Bean

7. Make each web module distributable if you want it to be highly available.

8. Enable availability for individual applications, web modules, or EJB modules during deployment.

   See Configuring Availability for an Individual Application or EJB Module

   In the Administration Console, check the Availability Enabled box, or use the asadmin deploy command with the --availabilityenabled option set to true.