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

Programming and Management Features
NonStop Servlets for JavaServer Pages (NSJSP) 6.0 System Administrator’s Guide—544548-004
4-26
server.xml Configuration File
server.xml Configuration File
The Commit Change operation causes the NSJSPADMIN server to serialize the
current configuration back to the NSJSP server.xml configuration file. At the same
time, the current version of the server.xml file is preserved using this naming
convention:
server.xml.yyyy-mm-dd.hh-mm-ss
where:
yyyy-mm-dd
is the year-month-date
hh-mm-ss
is the hour-minutes-seconds (in 24-hour format)
yyyy-mm-dd.hh-mm-ss is the timestamp when the Commit Change operation is
performed. For example, server.xml.2004-06-21.14-43-39 is created to
preserve the configuration file before the Commit Change operation is performed at
2:43:39 PM on June 21st, 2004.
These preserved server.xml files are located in the NSJSP_HOME/conf/directory.
The preserved context configuration files (with names of the form <context-
name>.xml.yyyy-mm-dd.hh-mm-ss) are located in two places depending on the
way the application is deployed:

NSJSP_HOME/conf/[enginename]/[hostname]/[webappname].xml

NSJSP_HOME/webapps/[webappname]/META-INF/context.xml
For example, the files are located in this directory:
NSJSP_HOME/conf/NSJSP/localhost
This subsection includes the information about:

Content of the server.xml File

Roll Back a Commit Change Operation

Cleaning the Preserved server.xml Files
Content of the server.xml File
When the NSJSPADMIN server 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 including those that were dynamically deployed.

All attributes are listed, including those that were omitted (using default values).