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 Communications Server 2.0 Application Deployment Guide.

1. Create an Communications Server cluster.

   For more information, see To Create a Cluster .

2. Set up load balancing for the cluster.

   For more information , see or Chapter 2, Configuring Converged Load Balancing for SIP or converged web/SIP applications.

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

4. Restart each server instance in the cluster.

5. 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

6. Make each web/SIP module distributable if you want it to be highly available.

7. Enable availability for individual applications, web/SIP 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.