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

Configuring NSJSP

NonStop Servlets for JavaServer Pages (NSJSP) System Administrator’s Guide—525644-003

3-13

filemaps.config

For each new application (a collection of related servlets, JSP and other resources)

you may need to add a corresponding filemap in the filemaps.config file.

For example, a new application called orders could be accessed while the default path

is /servlet_jsp/orders or by adding this filemap.

Filemap /orders $server_objectcode

Any application deployed using the admin or manager application has the option of

requesting the nsjspadmin ServerClass to add the context path as a Filemap for

HTTPD routing purpose. The nsjspadmin ServerClass manages filemaps.config

file so it is recommended that you place all user-defined filemaps in the

filemaps.config file.

Configuring Web Applications

A web application is a collection of servlets, HTML pages, images, JSP files, a

deployment descriptor, and other configuration files all in one location. The web

application is organized as a structured hierarchy of directories that can be packaged

or unpackaged from a WAR file.

The directory structure has two parts:

•

A public area for resources such as HTML pages and images that are downloaded

to clients for direct rendering on the browser.

•

A private area that has the root WEB-INF, which contains configuration files such

as the web.xml deployment descriptor, servlet classes, and library files -

resources that require a managed lifecycle.

Example 3-10. Sample Application Directory Structure on OSS

/webapps/myapp1/

index.html

images/

companylogo.gif

ourfounder.gif

literature/

whitepaper.pdf

WEB-INF/

web.xml

classes/

shoppingcart.class

checkout.class

lib/

xmltools.jar

src/

shoppingcart.java

checkout.java