NonStop Servlets for JavaServer Pages (NSJSP) 6.1 System Administrator's Guide
Configuring NSJSP
NonStop Servlets for JavaServer Pages (NSJSP) 6.1 System Administrator’s Guide—596210-006
3-53
The server.xml File
The Context container backgroundProcess is invoked to perform session
expiration and class monitoring.
The backgroundProcess method for a container is invoked in a separate thread
called the background processing thread. It is possible to have a separate thread
for each of the containers. A backgroundProcessor thread is spawned if the
container's backgroundProcessorDelay attribute has a positive value. Each
container invokes the backgroundProcess method of its child container if the
child container is not configured to spawn its own backgroundProcessor thread.
NSJSP inherits this feature from Apache Tomcat.
Child Elements Nested in the Engine Element
Following are the child elements that are nested in the Engine element:
Realm
Host
Realm
The Realm element is used for authenticating all the applications hosted on all the
hosts under the Engine element. For more information about Realms, see Realms
on page 7-7.
Example 3-49 shows the default values for the Realm element.
Example 3-49. The Default Values for Realm Element
<Engine name="NSJSP" defaultHost="localhost" >
<Realm
className="org.apache.catalina.realm.UserDatabaseRealm"
resourceName="UserDatabase" digest="MD5" />
<!--
<Valve className=
"com.hp.tandem.nsjsp.valves.NSJSPRequestDumperValve"
dumperOn="true" recordLength="1000"/>
-->
<Host name="localhost" appBase="webapps" unpackWARs="true"
autoDeploy="true" xmlValidation="false"
xmlNamespaceAware="false" configClass=
"com.tandem.servlet.catalina.startup.NSJSPContextConfig">
<Valve className=
"com.hp.tandem.nsjsp.valves.RequestTrackerValve"/>
</Host>
</Engine>










