Enabling Nessessionmanager - Netscape ENTERPRISE SERVER 6.1 - PROGRAMMER GUIDE TO SERVLETS Programmer's Manual

Each type of operation on the database that handles session information (looking
up, inserting, updating, and deleting) is performed by a corresponding dedicated
connection. Each of these connections has a precompiled SQL statement for higher
performance. The following parameters allow you to customize the number of
dedicated connections that perform each of the operations.
• - the number of connections that perform lookup operations (the
lookupPool
default is 4 connections).
• - the number of connections that perform insert operations (the
insertPool
default is 4 connections).
• - the number of connections that perform update operations (the
updatePool
default is 4 connections).
• - the number of connections that perform delete operations (the
deletePool
default is 2 connections).

Enabling NESSessionManager

You may want to enable
You can also enable
NESSessionManager
running in single process mode. To enable Enterprise Server to use
, do any of the following:
NESSessionManager
• Edit the file
web-apps.xml
Add a
session-manager
JSP as in the following example:
<session-manager
class='com.netscape.server.http.session.NES
<init-param>
<param-name>maxSessions</param-name>
<param-value>1000</param-value>
</init-param>
<init-param>
<param-name>timeOut</param-name>
<param-value>1800</param-value>
</init-param>
<init-param>
<param-name>reapInterval</param-name>
<param-value>600</param-value>
</init-param>
<init-param>
NESSessionManager
for a particular context if the server is
in the directory server_id
element within the
to change its default parameters.
.
/config
element for the servlet or
web-app
SessionManager
Chapter 6 Session Managers
NESSessionManager
'
61