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

Migrating to NSJSP 5.0
NonStop Servlets for JavaServer Pages (NSJSP) System Administrator’s Guide—525644-002
7-4
Pre-Compiled JSPs
During installation the existing iTP_catalina.policy file is backed up. Incorporate
your specific configuration into the new iTP_catalina policy file.
For more information about the NSJSP enhanced security manager, see Enhanced
Security Manager on page 3-26.
For more information about the security manager, see the documentation at
http://jakarta.apache.org/tomcat/tomcat-5.0-doc/security-manager-howto.html.
Pre-Compiled JSPs
The NSJSP 5.0 release has an upgraded JSP compiler and runtime environment
(Jasper2). As part of the upgrade when the setup script is run, the work directory
$NSJSP_HOME/work is deleted. This causes the first access to a JSP resource to
trigger off a JSP compilation and ensures that all JSPs use the upgraded Jasper2
compiler and runtime environment.
Note the JSP compilation always causes the first access to a JSP resource to be slow.
It is recommended that you pre-compile your JSPs because this allows for better
performance and response time for the first request. Typically in most production
environments, JSPs are very rarely modified so it makes sense to have your web
application perform and scale better.
The Standalone Application Deployer allows you to pre-compile your JSP programs
and compile your web application. The "jasper2" task in the sample
$NSJSP_HOME/deployer/build.xml configuration file, will pre-compile and
generate <servlet-mapping> tags for all JSPs that are part of your web application.
For more information on the Standalone Application Deployer, see the documentation
at http://jakarta.apache.org/tomcat/tomcat-5.0-doc/deployer-howto.html.
The $NSJSP_HOME/bin/jspc.sh script is no longer shipped in the NSJSP 5.0
release. You can use the Standalone Application Deployer to achieve the same
functionality by using the "jasper2" task as described above.
manager Web Application
The manager web application provides the management functions for all web
applications in the NSJSP container. In prior versions, the management functions were
provided using the nsjsp_manager (an interactive shell script). The nsjsp_manager
is no longer supported.
Application Migration Considerations
In NSJSP 5.0, for security, the Invoker Servlet is no longer enabled at the product
installation. However, you can enable the Invoker Servlet manually after carefully
examination of your security considerations.