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-84
Persisting Changes to the server.xml File and
Context Files
Contents of the server.xml File
When the Admin Server Class serializes its configuration back to the server.xml file,
the following changes occur in addition to the configuration changes:

All comments are removed.

All contexts are serialized except those that were deployed using the
context.xml file or those providing the context.xml file inside the .war or the
docBase directory.

All attributes are listed including those that were omitted (using default values).
Roll Back a Commit Change Operation
You can manually roll back the Commit Change operation, because the server.xml
files are preserved.
Complete the following steps to roll back the Commit Change operation:
1. Stop the NSJSP Server Class.
2. Rename the current server.xml file to the server.xml.temp file.
3. Rename the preserved server.xml.yyyy-mm-dd.hh-mm-ss file to the
server.xml file.
4. If you have modified any setting for a particular context, which includes <context
name>.xml file, complete the following steps to revert those context changes:
a. Rename the <context name>.xml file of that context (under the <NSJSP
6.1 Installation Directory>/conf/NSJSP/localhost folder) to the
<context name>.xml.tmp file.

Rename the <context-name>.xml.yyyy-mm-dd.hh-mm-ss file to the
<context-name>.xml file.
Note. The attributes that are not applicable to NSJSP may not be serialized.
Note. HP recommends that you make changes to the server.xml file using a text editor.
Note.

To roll back the Commit Changes operation, you must restart the NSJSP Server Class.

The server.xml and the context.xml files can be backed up but the
nsjsp-user.xml file cannot be backed up.
Note. You can stop the NSJSP Server Class using the NSJSP Manager application or
using the CLI.