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

Configuring NSJSP

NonStop Servlets for JavaServer Pages (NSJSP) 6.0 System Administrator’s Guide—544548-004

3-16

Deploying web applications on NSJSP startup

If you do not want to use the NSJSP Manager, deploy your web applications statically

to NSJSP followed by an NSJSP startup. The location where you deploy web

applications for this type of deployment is called the appBase, and is specified for

each Host. For more information on deploying web applications on the NSJSP startup,

refer http://tomcat.apache.org/tomcat-6.0-doc/deployer-

howto.html#Deployment%20on%20Tomcat%20startup.

Deploying web applications on a running NSJSP server

Web applications can be deployed on a running NSJSP server. If the Host

autoDeploy attribute is set to true, the Host will attempt to deploy and update the

web applications dynamically. For more information on deploying web applications on a

running NSJSP server, refer http://tomcat.apache.org/tomcat-6.0-doc/deployer-

howto.html#Deploying%20on%20a%20running%20Tomcat%20server.

Deploying web applications using NSJSP Manager

For information on deploying web applications using the NSJSP Manager, see

Manager Web Application on page 5-1.

Deploying web applications using NSJSP Client Deployer

The Client Deployer is used to validate, compile, compress to .WAR, and deploy web

applications to the production or development NSJSP servers. However, the target

NSJSP server must be running because this feature uses the NSJSP Manager. For

more information on deploying web applications using the NSJSP Client Deployer,

refer http://tomcat.apache.org/tomcat-6.0-doc/deployer-

howto.html#Deploying%20using%20the%20Client%20Deployer%20Package.

Configuring the Security Manager

NSJSP can also be started using a Security Manager. The SecurityManager

function enables a web application to run its own sandbox. The Security Manager

allows you to restrict trusted functionality to code that requires it.

NSJSP uses its own version of the standard file catalina.policy, documented in

Tomcat 6.0.13. The security policies implemented by the Java Security Manager are

configured in the file iTP_catalina.policy located in the directory

NSJSP_HOME/conf.

The iTP_catalina.policy file replaces any system java.policy file. The file

iTP_catalina.policy contains a default set of security policies to be enforced (by

the JVM) when NSJSP is run with the option java.security.manager (see

servlet.config

on page 3-2). You can assign additional permissions to particular web

applications by adding additional grant entries.