Choosing a Persistence Store

The following types of persistent storage are supported for
passivation and checkpointing of the SFSB state:

The local file system - Allows a single server instance
to recover the SFSB state after a failure and restart. This store
also provides passivation and activation of the state to help control
the amount of memory used. This option is not supported in a production
environment that requires SFSB state persistence. This is the default
storage mechanism.

Other servers - Uses other server instances in the
cluster for session persistence. Clustered server instances replicate
session state in a ring topology. Each backup instance stores the
replicated data in memory.

The high-availability database
(HADB) - Allows a cluster of server instances to recover the SFSB
state if any server instance fails. The HADB is also used as the passivation
and activation store. Use this option in a production environment
that requires SFSB state persistence. For information about how to
set up and configure this database, see the description of the configure-ha-cluster command in the Sun GlassFish Enterprise Server v2.1.1 Reference Manual.

Choose the persistence store in one of the following ways:

To use the local file system, first disable availability.
Select the Availability Service component under the relevant configuration
in the Admin Console. Uncheck the Availability Service box. Then
select the EJB Container component and edit the Session Store Location
value. The default is domain-dir/session-store.

To use other servers, select the Availability Service
component under the relevant configuration in the Admin Console.
Check the Availability Service box. To enable availability for the
EJB container, select the EJB Container Availability tab, then check
the Availability Service box. All instances in an Enterprise Server cluster
should have the same availability settings to ensure consistent behavior.