To Set Up High Availability Session Persistence

Before You Begin

High availability session persistence is incompatible with dynamic deployment, dynamic reloading, and auto-deployment. 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 Chapter 2, Deploying Applications, in Sun Java System Application Server Enterprise Edition 8.2 Administration Guide.

1. Create an Application Server cluster.

   For more information, see To Create a Cluster .

2. Create an HADB database for the cluster.

   For more information , see configure-ha-cluster(1).

3. Set up HTTP 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.