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-3
Configuring the Security Manager
configuration file, you can store Context elements in individual files (with a .xml
extension) in the $NSJSP_HOME/conf/<engine-name>/<host-name>/ directory.
This method allows dynamic reconfiguration of the web application because the main
iTP_server.xml file cannot be reloaded without restarting NSJSP. It is
recommended that you not place <Context> elements directly in the
iTP_server.xml file. Instead, you should put them in the META-INF/context.xml
directory of your WAR file or in the $NSJSP_HOME/conf/<engine-name>/host-
name>/ directory.
In addition, NSJSP 5.0 evaluates variables (${<variable-name}) while parsing XML
documents. Therefore, an extra "$" (dollar sign) is required while specifying NonStop
SQL session tables. For example:
<Context path="/servlet_jsp/examples" docbase="examples" >
<Manager
className="com.tandem.servlet.catalina.session.NSJSPPersistentManager"
saveOnRestart="true" checkInterval="300">
<Store className=
"com.tandem.servlet.catalina.session.NonStopSQLJDBCStore"
driverName="com.tandem.sqlmp.SQLMPDriver"
connectionURL="jdbc:sqlmp:"
sessionTable= "$$SYSTEM.T1222CAT.SessData" />
</Manager>
</Context>
In the same way, the table name for a NonStop SQL JDBCRealm requires extra "$"
(dollar sign). For example:
<Context path="/Servlet_jsp/jsp_examples" docBase="jsp-examples">
<Realm className="org.apache.catalina.realm.JDBCRealm"
connectionURL="jdbc:sqlmp:" driverName="com.tandem.sqlmp.SQLMPDriver"
userRoleTable="$$DATA00.REALMDB.USERROLE"
userTable="$$DATA00.REALMDB.USERS"/>
</Context>
If a context is altered using the admin web application, changes are saved to its
corresponding configuration file. In the meantime, a backup copy of the context is
saved in the $NSJSP_HOME/conf/<engine-name>/<host-name>/backup/
directory.
Configuring the Security Manager
NSJSP 5.0 supports enhanced security by allowing you to configure which NSJSP
internal packages are protected against package definition and access. This
arrangement prevents a non-trusted application from accessing sensitive NSJSP
internal packages.