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-23
web.xml
For example:
<servlet>
<servlet-name>
Snoop
</servlet-name>
<servlet-class>
SessionSnoop
</servlet-class>
<load-on-startup>
3
</load-on-startup>
</servlet>
The example shows a servlet class file, SessionSnoop, which has a priority of 3.
Files with a higher priority will be loaded before this one. Note that the servlet class
name is SessionSnoop, but a URL would reference it by the servlet name Snoop.
Defining a Session Timeout Value
This parameter could be in either of the two versions of the web.xml file. The default
session timeout interval value for all sessions created in the web application can be
defined in the web.xml file using session-config and session-timeout elements. The
specified timeout value must be expressed in a whole number of minutes. For
example:
<session-config>
<session-timeout>
30
</session-timeout>
</session-config>
Your Application Version of web.xml
Each application could have a copy of web.xml, the deployment descriptor, at the root
level of the application, for example:
/webapps/myapp1/WEB-INF/web.xml
This file overrides any settings made in the web.xml file at the servlet_jsp/conf
level.
Initialization of Servlets
You could initialize servlets in either of the two versions of the web.xml file.
If portability is a requirement, you may prefer to put the initialization within the
application version of web.xml. This is the deployment descriptor location used when
packing or unpacking web application archive (WAR) files.