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

Managing NSJSP
NonStop Servlets for JavaServer Pages (NSJSP) 6.1 System Administrator’s Guide—596210-006
4-57
Overview and Architecture
4 Managing NSJSP
This section describes the following topics:

Overview and Architecture

Admin Web Application Features

Login and Security Considerations

Managing Admin Web Application Operations
Overview and Architecture
An NSJSP 6.1 configuration can be changed by editing configuration files and then
stopping and restarting the iTP Secure WebServer environment. However, it is also
desirable to make changes dynamically without stopping the NSJSP processes. Such
changes would also need to be made to the configuration files, if they need to be
persisted. The Admin Web application provides this capability for a single PATHMON.
It can update a configuration file with changes and distribute those changes to every
running process in the NSJSP Server Class under a PATHMON. The Admin Web
application runs in a separate NSJSP Admin Server Class from the NSJSP Servlet
Server Class. The name of the Admin Server Class is derived from the NSJSP Server
Class name. The Admin Server Class name is <NSJSP server class name>-adm.
Admin Web application requests are routed to the Admin Server Class (through a
filemap created for the iTP Secure WebServer). The administrator browses objects
and performs updates through the Admin Web application pages. When you select
Save to complete an update, the save operation does not implement the changes in
the NSJSP Server Class immediately. You must next click the Commit Changes
button for the changes to actually be processed. The Admin Web application then
updates the relevant configuration file and broadcasts all the saved changes to all
running processes of the NSJSP Server Class under the same PATHMON.
Figure 4-33
shows operator Admin operations received by the iTP Secure WebServer
directed to the Admin Server Class. When you click Commit Changes, the Admin
Server Class first updates the configuration file (for example, server.xml) and then
broadcasts all the saved changes in a chunk to every running process of the NSJSP
Note.

HP recommends that you perform the Commit Changes operation only after making all
changes to the configuration.

The Admin Web application can manage an NSJSP Server Class in only one PATHMON
when NSJSP 6.1 is installed in an iTP Secure WebServer environment that is configured
for online-upgrade.
Note. If the Admin Server Class fails to start or is stopped for some reason, the NSJSP Server
Class continues to run. All web applications, except the Admin Web application and the
Manager Web application, are still accessible.