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-25
The Installation-Specific servlet.config File
Servlet is enabled by default. The JMXProxy is defined in the old manager
application’s deployment descriptor (web.xml). Example 3-33 shows the
configuration for JMX Proxy Servlet in the web.xml file.
The NSJSP Manager GUI provides features to query, compare, and modify MBean
attributes across the NSJSP server class processes. Although the JMX Proxy Servlet is
available in NSJSP 6.1, HP recommends that you use the NSJSP Manager GUI for
MBean operations.
While the JMX Proxy Servlet provides features to modify MBean attributes across NSJSP
server class processes in a single PATHMON, the NSJSP Manager GUI provides similar
functionality across NSJSP server class processes running across multiple PATHMONS.
The JMX Proxy Servlet can be used in scripts to manage NSJSP Mbeans. However, the
NSJSP Manager GUI cannot be used in scripts. Therefore, if you are using scripts to
manage NSJSP MBeans, you can continue to use the JMX Proxy servlet in NSJSP6.1 to
execute those scripts.
SaveSessionOnCreation
Enables or disables saving sessions into a persistent store during creation time.
The default value is false. This is to prevent saving a session before it is modified
by the user application. This also reduces the number of database operations for
each client request.
If both the SaveSessionOnCreation and the SessionBasedLoadBalancing
options are set to false, and if a persistent manager is configured with a
persistent store, then all sessions are written to the store at the end of each
request processing cycle. As a result, all changes made to the session by the user
application are persisted to the store.
Example 3-33. Configuration for JMXProxyServlet in the web.xml file
….
….
<servlet>
<servlet-name>JMXProxy</servlet-name>
<servlet-
class>org.apache.catalina.manager.JMXProxyServlet</servlet-class>
</servlet>
….
….
<servlet-mapping>
<servlet-name>JMXProxy</servlet-name>
<url-pattern>/jmxproxy/*</url-pattern>
</servlet-mapping>
….
….