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

Using NonStop Servlets for JavaServer Pages

(NSJSP)

iTP Secure WebServer System Administrator’s Guide—523346-002

9-21

iTP_server.xml

This is a version of the standard server.xml file modified to use with the

iTPWebServer.

This is an XML file with a DTD (set of tags and structures) specified in server.dtd.

The file is located (by default) in /usr/tandem/webserver/servlet_jsp/conf.

iTPWebServer Modifications

The following statements in the iTP_server.xml file are modified to work with the

iTPWebServer. They must not be changed:

<RequestInterceptorclassName="org.apache.tomcat.request.iTPWSSessionIntercept

or" />

<Parameter name="handler"

value="org.apache.tomcat.service.http.iTPWSHttpConnectionHandler"/>

<Parameter name="socketFactory"

value="com.tandem.servlet.ReceiveServerSocketFactory"/>

</Connector>

Context Paths

To add an application, you must add the context path into the context manager section

of iTP_server.xml and the associated filemap into the servlet.config file.

Assume that you want to add the application orders with associated servlets, JSP and

other resources. The context path should be entered as follows:

</context>

The context path shows the context, essentially the start of the path for any URL

attempting to locate and run a servlet. The docbase could be used to create a separate

location for the application, other than the default webapps directory.

The corresponding filemap from servlet.config should look like this:

Filemap /orders $server_objectcode

Reloading Servlets

If the “reloadable” attribute is set to true in the iTP_server.xml file, the container will

automatically reload servlet classes (loaded from either the WEB-INF classes directory

or a JAR file in the WEB-INF/lib directory) that have changed. The reload function is

only applicable for the top level of Servlet classes. It means that any changes in the

class that is used inside user servlets will not be brought in.