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-25
Considerations for Migrating Web Applications from
NSJSP 5.0 to NSJSP 6.1
/usr/webmstr/webapps/myapp.xml, the NSJSP Manager copies the myapp.xml
file to the appropriate location in NSJSP 6.1 with the name foo.xml and then deploys
the application based on the contents of foo.xml. The directory where the context
definition file is copied will always be <NSJSP_HOME>/conf/<engine
name>/<host name>. In this example, foo.xml is copied to the above location.
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 6.1 handles the context definition (META-INF/context.xml) differently than
NSJSP 5.0. NSJSP 6.1, extracts the context.xml file from the .war file and copies
the context.xml to the <NSJSP_HOME>/conf/<engine_name>/<host_name>
directory with the name <context_name>.xml. For example, if foo.war is deployed
and contains a META-INF/context.xml file, NSJSP 6.1 copies the context.xml
file to foo.xml to the above directory. With subsequent restarts of NSJSP, this
application will be deployed from the context definition file rather from the .war file.
You can also modify the context during run time using the Admin application.
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 6.1 handles the context definition (META-INF/context.xml) differently than
NSJSP 5.0. NSJSP 6.1 copies the META-INF/context.xml file of the application
and copies the context.xml in the
<NSJSP_HOME>/conf/<engine_name>/<host_name> directory with the name
<context_name>.xml. For example, if foo.war is deployed and contains a META-
INF/context.xml file, NSJSP 6.1 copies the context.xml file to foo.xml in the
specified directory. With subsequent restarts of NSJSP, this application will be
deployed from the context definition file rather from the application directory. You can
also modify the context during run time using the Admin application.
Note. In NSJSP 5.0, the path defined in the context definition file is not used. Also, the path is
not derived from the name of the file.