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

Managing NSJSP
NonStop Servlets for JavaServer Pages (NSJSP) 7.0 System Administrator’s Guide—674372-005
4-128
Deploying Applications on a Running NSJSP Server
<NSJSP_HOME>/conf/<engine_name>/<host_name> directory contains a
context element (and its associated subelements) for a single web application. The
value of the docBase attribute of the context element will be the absolute path to a
web application directory, or the absolute path of a .war file.
2. All .war files are then deployed. A .war file in the appBase directory that does
not have a corresponding directory of the same name (without the .war extension)
will be automatically expanded, unless the unpackWARs property is set to false.
If you redeploy an updated .war file, you must delete the expanded directory
before restarting NSJSP to ensure that the updated war file expands again.
3. It is assumed that any subdirectory within the application base directory contains a
web application and is deployed last.
Deploying Applications on a Running NSJSP Server
In addition to the deployment at startup, you can deploy web applications while NSJSP
is running. If the value of the Host’s autoDeploy attribute is set to true, the Host will
attempt to deploy and update web applications dynamically, as required. The auto
deployer first performs the procedure as described in Deploying Applications at Startup
on page 4-127 and subsequently monitors web applications for the following changes:

Updates to the WEB-INF/web.xml file – An update to the WEB-INF/web.xml file
causes a reload of the web application.

Deletion of .war files – Deleting a .war file causes the application to undeploy,
and any associated expanded directory, context file, and work directory are
removed. Subsequently, current user sessions will not be persisted.

Deletion of a directory – Deleting a directory causes the application to undeploy,
and any associated context file and work directory are removed. Current user
sessions will not be persisted. Any associated .war file will not be deleted, and the
application will be redeployed from the .war file when the auto deployer checks for
changes.

Deletion of a context file – Deleting a context file causes the application to
undeploy, and any associated work directory is removed. Current user sessions
will not be persisted. Any associated .war file and directory will not be deleted,
and the application will be redeployed from the .war file (or from the directory if no
.war file is present) when the auto deployer checks for changes.

.war file update – Updating a .war file causes the application to undeploy, and
any associated expanded directory, context file, and work directory are removed.
Current user sessions will not be persisted.
Note. The location of the docBase attribute defined in the XML context file must be out-
side the appBase directory to ensure that automatic deployment operates properly.
Note. If the auto deployer is enabled, the updated war file will automatically expand after
the last expanded directory is removed.