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

Migrating to NSJSP 7.0

NonStop Servlets for JavaServer Pages (NSJSP) 7.0 System Administrator’s Guide—674372-005

7-17

Application Deployed Using a .war File

Deploying a .war file can be achieved without using the NSJSP Manager. Copy the

.war file to the folder defined by the appBase of the Host element in which the

application must be deployed. In the default configuration, appBase of the only Host

element is the webapps folder in the <NSJSP_HOME> directory.

A .war file can also be deployed using the NSJSP Manager. You can also provide the

context path.

NSJSP 7.0 handles the context definition (META-INF/context.xml) same as

NSJSP 6.1 except copyXML. For more information on copyXML, see The context.xml

File on page 3-69.

Application Deployed Using a Directory

Copy the entire application directory to the folder specified in appBase of the Host

element. In the default configuration, appBase of the only Host element is the

webapps folder in the <NSJSP_HOME> directory.

An application directory can also be deployed using the NSJSP Manager. The NSJSP

Manager offers the additional flexibility of providing the context path.

NSJSP 7.0 handles the context definition (META-INF/context.xml) differently than

NSJSP 6.1. For more information on how context is handled and copyXML, The

context.xml File on page 3-69 .

Distribution

Starting from NSJSP 7.0, the example and docs applications are packaged as .war

files. This is done for the ease of distribution. However, in the beginning these .war

files are exploded, and hence slows down the first time start up process for NSJSP.

Considerations for Migrating Web Applications

from NSJSP 6.0 to NSJSP 6.1

Table 7-9 lists the prerequisites of NSJSP 6.0 and NSJSP 6.1.