To enable or disable availability at the server instance or container level using the Administration Console:
You can change the Store Pool Name if you changed the JDBC resource used for connections to the HADB for session persistence. For details, see the description of the configure-ha-cluster
command in the Utility Reference.
memory
(no persistence) file
(the file system) and ha
(the HADB). For production environments that require session persistence, use ha
.
If the Persistence Type is set to memory
, you can use the sessionFilename
property to specify a file system location where the HTTP session state is stored if the server instance is gracefully shut down. This is useful for internal testing but is not supported for production environments.
If the Persistence Type is set to file
, you can use the directory property to specify the file system location where the HTTP session state is stored. Persisting to the file system is useful for internal testing but is not supported for production environments.
ha
. Allowed values are as follows:web-method
- The session state is stored at the end of each web request prior to sending a response back to the client. This mode provides the best guarantee that the session state is fully updated in case of failure.time-based
- The session state is stored in the background at the frequency set by reapIntervalSeconds
. This mode provides less of a guarantee that the session state is fully updated. However, it can provide a significant performance improvement because the state is not stored after each request.on-demand
- The session state is stored at the user’s request.ha
. Allowed values are as follows:session
- The entire session state is stored every time. This mode provides the best guarantee that your session data is correctly stored for any distributable web application.modified-session
- The entire session state is stored if it has been modified. A session is considered to have been modified if HttpSession.setAttribute()
or HttpSession.removeAttribute()
was called. You must guarantee that setAttribute()
is called every time an attribute is changed. This is not a J2EE specification requirement, but it is required for this mode to work properly.modified-attribute
- Only modified session attributes are stored. For this mode to work properly, you must follow these guidelines:
configure-ha-cluster
command in the Utility Reference.file
(the file system) and ha
(the HADB). For production environments that require session persistence, use ha
.file
and ha
.
If either Persistence Type is set to file
, the EJB container specifies the file system location where the passivated session bean state is stored. See "Configuring the SFSB Session Store When Availability Is Disabled". Checkpointing to the file system is useful for internal testing but is not supported for production environments.
configure-ha-cluster
command in the Utility Reference.