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

Overview and Architecture
NonStop Servlets for JavaServer Pages (NSJSP) System Administrator’s Guide—525644-003
1-6
The Deployment Descriptor
subdirectory (containing the zip or jar files), and your customized version of the
web.xml file – the deployment descriptor.
webapps/myapp1/WEB-INF/web.xml
webapps/myapp1/WEB-INF/classes/helloworld.class
webapps/myapp1/WEB-INF/lib
A detailed description of the directory structure can be found in Configuring Web
Applications on page 3-13.
The Deployment Descriptor
A default version of web.xml sets the basic configuration for a context and MIME
types for all servlets, and can also preload and start up servlets when the web
container is first started. If you have a custom web.xml file for your particular servlet
or JSP, that custom file overrides the default.
In NSJSP, the default version of web.xml is located in this directory:
/usr/tandem/webserver/servlet_jsp/conf
Web Archive (WAR) Files
The web application can be packaged into a web archive (WAR) file to provide a
simplified means of distributing Java class files and related resources as a single
deployment unit.
For example, to create a WAR file for the application /myapp1 go to the root of the
application.
cd /usr/tandem/webserver/servlet_jsp/webapps/myapp1
This command packs all the files and subdirectories into a single file called
myapp1.war. The -c option creates a new archive, the -f option specifies the target file
name, and the -v (verbose) option echoes the files to your display.
jar -cf myapp1.war *
To view the contents of an existing WAR file, type:
jar -tvf myapp1.war
To deploy a WAR file, see Add a New Web Application on page 3-14.