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

Migrating to NSJSP 6.1
NonStop Servlets for JavaServer Pages (NSJSP) 6.1 System Administrator’s Guide—596210-006
7-24
Considerations for Migrating Web Applications from
NSJSP 5.0 to NSJSP 6.1
Compiling the Application
NSJSP 5.0 implements the Java Servlets 2.4 specifications whereas NSJSP 6.1
implements the Java Servlet 2.5 specifications. You must compile the application with
the NSJSP 6.1 library jar files to ensure that the Java Servlet API used in the
application is supported in NSJSP 6.1. The library files are located in the lib folder of
the installation.
Session Store
If the application uses HTTP sessions and the application or the NSJSP servlet
container is configured for persistent sessions, you must migrate the session store
along with the application.
For information on migrating the session store, see Migrating the Session Store on
page 7-27.
For more information on persistent sessions, see Chapter 3, Configuring NSJSP.
Deploying Web Applications in NSJSP 6.1
After making the changes to the application, you must deploy the application in NSJSP
6.1. Although you can manually deploy an application in NSJSP 6.1 by copying the
application resources, such as the .war file, to an appropriate location, such as the
webapps folder in NSJSP 6.1, HP recommends that you deploy the application in
NSJSP 6.1 using the NSJSP Manager.
For information on deploying web applications using the NSJSP Manager, see Chapter
4, Managing NSJSP.
You can use the following methods to migrate applications from NSJSP 5.0 to NSJSP
6.1:
Application Deployed Using a context.xml File
If an application is deployed using its context definition file, HP recommends that you
deploy the application using the NSJSP Manager. An application is deployed using the
context.xml, as follows:
Unlike in NSJSP 5.0, the path attribute of the context element in the context definition
is ignored in NSJSP 6.1. The path is derived from the name of the context definition
file. For example, if the name of the context definition file is foo.xml, the path of the
context is /foo.
The NSJSP Manager provides an option to deploy an application using its context
definition file. In this case, you can mention the context path and the manager derives
the name of the context definition file from the path specified. For example, if the value
of path is /foo and the full path to context definition file is
Note. In NSJSP 5.0, the persistent manager in the application’s context.xml file enables
you to configure the application for persistent sessions.