iTP Secure WebServer System Administrator's Guide (iTPWebSvr 5.1+)

Using NonStop Servlets for JavaServer Pages With
The iTP Secure WebServer
iTP Secure WebServer System Administrator’s Guide—522659-001
9-3
Migration
Migration
•
Migration From T0094 to T1222 (See page 9-40). This describes how to modify an
existing configuration of servlets to conform to Java servlet 2.2 API specifications
and the J2EE environment.
Overview
Example 9-1 contains a roadmap of the main directories and configuration necessary to
get NonStop Servlets for JavaServer Pages up and running. This is only intended as an
overview of the way things work together - specifically to answer the question, "How do
you get from a URL to the application and to a servlet?"
The first configuration file is servlet.config which is located in the /conf directory of
/usr/tandem/webserver.
•
servlet.config - For each application (a collection of related servlets and resources)
you must create a Filemap, mapping those servlets to the server object code. For
example, to add the application myapp1 and its related servlets
filemap /myapp1 $server_objectcode
You must specify the home for NonStop Servlets for JavaServer Pages by setting the
environment variable
set env(SERVLET_JSP_HOME) /usr/tandem/webserver/servlet_jsp
The other two main configuration files are located in the /servlet_jsp directory. This
default root directory for NonStop Servlets for JavaServer Pages is
/usr/tandem/webserver/servlet_jsp. The /conf subdirectory contains two main
configuration files;
•
iTP_server.xml - You must create a context path for every application. Use context
path to specify the directory (application) name, and use docbase to specify the path
from the root (servlet_jsp) to the application. This ensures any URL that contains
the application name and a resource name, such as a servlet name, can locate that
resource.
•
web.xml - This file is known as a deployment descriptor because it contains xml
commands you use to deploy and control servlets and JSP. You may set alias names
for them (the default is the class name), initialize with values, provide MIME
mapping, welcome and error pages, and so on.