In-Memory Session Replication Documentation Plan for GlassFish Server Open Source Edition 3.1

People and Roles

Name Role Location Time Zone Email
Paul Davies Documentation Feature Owner Santa Clara, CA, USA US/Pacific pauldavies@dev.java.net
  Peer Reviewer Santa Clara, CA, USA US/Pacific @dev.java.net
Mahesh Kannan Software Engineer Santa Clara, CA, USA US/Pacific mk111283@dev.java.net
Joe Fialli
Software Engineer Burlington, MA, USA
US/Eastern jfialli@dev.java.net
Gopal Jorapur QA Engineer Santa Clara, CA, USA US/Pacific gopaljorapur@dev.java.net

Audience

This feature is aimed at system administrators.

Summary of the Feature From a User's Perspective

The In-Memory Session Replication feature provides high availability of HTTP session states and EJB session states by enabling containers to store session state data persistently. Data that is stored persistently can survive GlassFish instance failures and can be used to re-create the session on the surviving instance to which GlassFish Server fails over.

Availability

The In-Memory Session Replication feature is provided in the Web Profile distribution and the Full Platform distribution.

Statement of Work

This section describes in detail for each document the work that is required by the introduction of the feature, such as changes, addition of new material, relocation of existing material, and removal of existing material.

Documentation Impact:

  • None
  • Minor
  • Moderate
  • Major
  • New

Note - If a document is task based (as opposed to reference), the changes should be determined from the user task analysis for the feature.


Changes to Books

High Availability Administration Guide Changes

Section Documentation Impact Writer Reviewers Description of Change
Storage for Session State Data in Chapter 1. High Availability in GlassFish Server
Moderate
Paul
Mahesh Kannan
Joe Fialli
Reinstate from v2.1.1 documentation.

Remove references to HADB.

In the description of how replicated data is stored, replace the references to "ring topology" with a statement that GlassFish Server uses a consistent hash algorithm to determine where an instance's session state data is stored.
Chapter 9. Configuring High Availability Session Persistence and Failover
Moderate
Paul
Mahesh Kannan
Joe Fialli
Reinstate from v2.1.1 documentation.

Remove references to HADB and to usage profiles.

Move tasks that use the GUI to the online help.

Explain how to perform the following tasks by using the asadmin utility or by modifying deployment descriptor files:
  • Set up high availability persistence
  • Enable session availability for a server instance
  • Enable availability for the web container
  • Configure availability settings for the web container
  • Configure availability settings for an individual web application
  • Store single sign-on information persistently
  • Enable availability for the EJB container
  • Configure availability settings for the EJB Container
  • Configure the SFSB session store when availability is disabled
  • Configure availability for an individual application or EJB module
  • Configure availability for an individual EJB component
  • Specify methods that are to be checkpointed

Changes to Online Help

All changes to online help, including those arising from the In-Memory Session Replication feature, are detailed in Administration Console Documentation Plan.

Changes to Man Pages

Man Page Name and Section Documentation Impact Writer Reviewers Description of Change
list-persistence-types NEW Rebecca Parks Joe Fialli
Mahesh Kannan
New command to list persistence types. The --type option has two possible values, web or ejb. The built-in types listed are memory, file, and replicated.

Review Schedule

The review schedule for the documentation items that are affected by this feature is provided in the following table.

Item Review Start Date Review End Date
High Availability Administration Guide changes    
Online Help changes    

Reviewers are listed in the Statement of Work.

Related Information

Email aliases: