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

Configuring NSJSP
NonStop Servlets for JavaServer Pages (NSJSP) 7.0 System Administrator’s Guide—674372-005
3-30
The Installation-Specific servlet.config File
The NSJSP Manager GUI provides features to query, compare, and modify MBean
properties across the NSJSP server class processes. Although the JMX Proxy
Servlet is available in NSJSP 7.0, HP recommends that you use the NSJSP
Manager GUI for MBean operations.
While the JMX Proxy Servlet provides features to modify MBean properties 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 NSJSP 7.0 to execute those scripts.
Starting from NSJSP 7.0, the JMX Proxy Servlet is integrated with NSJSP
Manager. The functionality of JMX Proxy Servlet remains the same as the earlier
version of NSJSP. However, there will be the following two exceptions:

The Servlet will accept the following two new requests parameters:
Serverclass: Since NSJSP Manager (unlike NSJSP Web Manager
application) has capability to manage more than one serverclass, the jmxproxy
request should specify which serverclass the request is intended for. The
Serverclass request parameter will determine the intended serverclass.
Process: In addition to performing a JMX operation on a specific serverclass,
NSJSP Manager 7.0 will also provide an option to run the operation on a
specific NSJSP process. The process on which to run to the JMX operation will
be determined by the Process parameter passed in the request. However, the
provided process name should be a valid NSJSP process belonging to a
serverclass that is managed by NSJSP Manager.
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>
….
….