NonStop Servlets for JavaServer Pages (NSJSP) 6.0 System Administrator's Guide

Configuring NSJSP
NonStop Servlets for JavaServer Pages (NSJSP) 6.0 System Administrator’s Guide—544548-004
3-44
Configuring NSJSPPersistentManager and
Persistent Store

The default implementation, NSJSPStandardManager, provides no persistence
and stores sessions in memory only.

The optional, NSJSPPersistentManager, stores active sessions that have been
swapped out and also saves sessions across restarts of the NSJSP container. You
can specify the storage location for the session data by configuring the appropriate
<Store> element nested under the <Manager> element.
Configuring NSJSPPersistentManager and Persistent Store
NSJSPPersistentManager (Session Persistence Support)
NSJSPPersistentManager is the persistent implementation of a session manager. It
can swap active, but idle, sessions out to a persistent store, in addition to save
sessions across restarts of the NSJSP container. The actual persistent store
mechanism is configured through a <Store> element nested under the <Manager>
element.
For a detailed description of the attributes supported by NSJSPPersistentManager,
refer http://tomcat.apache.org/tomcat-6.0-doc/config/manager.html.
Configuring the Persistent Store
If you are using NSJSPStandardManager, no elements can be nested inside your
<Manager> element.
For the persistence manager implementation (NSJSPPersistentManager), you
must nest a <Store> element that defines the characteristics of the persistent data
store. Example 3-22 shows the implementation of NSJSPPersistentManager.
To enable the session data to be persisted, bring down the NSJSP SERVLET and
NSJSPADMIN ServerClass by using the PATHCOM utilities instead of the stop script
provided with the iTP WebServer distribution. For more information, see Stopping
NSJSP on page 2-10.
NonStopSQLJDBCStore
The NonStopSQLJDBCStore implementation is a NonStop SQL database-based
store that saves swapped-out sessions into a pre-configured NonStop SQL database
table that is accessed by a JDBC driver.
For more information on configuring a store and its attributes, refer the JDBC Based
Store section on http://tomcat.apache.org/tomcat-6.0-doc/config/manager.html.
Apart from the attributes mentioned on the website there are two additional attributes
that need to be configured for the store to be persistent. These attributes are explained
below:
Note. To provide persistent sessions support, configure a <Store> element.