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

Configuring NSJSP
NonStop Servlets for JavaServer Pages (NSJSP) 6.1 System Administrator’s Guide—596210-006
3-96
Configuring the Manager Element
Configuring the Manager Element
The Manager element represents the session manager that will be used to create and
maintain HTTP session objects as requested by a web application.
A Manager element is always configured as a child of the Context element. Each
application can configure its own Manager in the context definition in the META-
INF/context.xml file of the application. Example 3-78 shows a sample context
configured with a persistent manager.
For all applications that do not define a Manager explicitly, the Manager configured in
the <NSJSP_HOME>/conf/context.xml file will be used as the default manager. By
default, the NSJSPStandardManager is used. This is an in-memory session
manager. Example 3-79
shows the default Manager configuration in the
<NSJSP_HOME>/conf/context.xml file.
Example 3-78 shows a sample context configured with a persistent manager.
Example 3-77. Creating A Session Data Table with Four Partitions Across Four
Different Disks
create table sessdata (
session_id CHAR(48) NO DEFAULT NOT NULL,
process_name CHAR(8) NO DEFAULT NOT NULL,
rec_number INTEGER UNSIGNED NO DEFAULT NOT NULL,
valid SMALLINT UNSIGNED NO DEFAULT,
maxinactiveinterval INTEGER NO DEFAULT,
lastaccessed LARGEINT NO DEFAULT,
app_name VARCHAR(150) NO DEFAULT NOT NULL,
session_data VARCHAR(3600) CHARACTER SET ISO88591,
primary key (session_id, process_name, rec_number))
location $DATA03
hash partition by (session_id)(
add location $DATA00,
add location $DATA01,
add location $DATA02
);
Note. Before using a persistent manager, the session table must be created. For
information on how to create the session table, see Create the Persistent Store
on
page 3-84.