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

Managing NSJSP
NonStop Servlets for JavaServer Pages (NSJSP) 7.0 System Administrator’s Guide674372-005
4-122
Operations Using the Command-line Interface
5. Start the server class that is in the STOPPED state.
Operations Using the Command-line Interface
This section discusses the following topics:
iTP Secure WebServer Operations
Server Class Operations
iTP Secure WebServer Operations
NSJSP is installed as part of an iTP Secure WebServer installation. Each NSJSP
Server Class is defined to TS/MP during startup. The following configuration files are
located in the <NSJSP_HOME>/conf directory during the NSJSP installation:
servlet.config (installation-specific and generic)
jdbc.config
filemaps.config
When an NSJSP configuration file is modified, the HTTPD command-line utility must
redefine the iTP Secure WebServer's TS/MP configuration. To redefine the TS/MP
configuration, you must cold start the iTP Secure WebServer. The iTP Secure
WebServer must be cold started to create and add the NSJSP Server Class definitions
to the iTP Secure WebServer TS/MP configuration.
To perform a cold start, you must stop and then start the iTP Secure WebServer using
the scripts provided in the <iTP Installation Directory>/conf directory.
Restarting the iTP Secure WebServer is equivalent to stopping the iTP Secure
WebServer and then doing a cold start.
To cold start the iTP Secure WebServer, see Verifying the NSJSP Installation
on
page 2-18.
If you modify NSJSP container files, such as server.xml and
logging.properties, for the changes to take effect, restarting the NSJSP Server
Class is sufficient. You need not cold start the iTP Secure WebServer.
The NSJSP Server Classes that are defined by the iTP Secure WebServer include
configuration parameters, such as MAXSERVERS and NUMSTATIC, that are copied
directly from the servlet.config file. If you modify the parameter values, you must
update the servlet.config file, and must stop and then start the iTP Secure
WebServer.
Note. After each save operation, the web applications that define an explicit context will be
restarted because the context file is updated. This happens irrespective of whether the
application’s context was modified or not.
Note. The HTTPD object in the <iTP Installation Directory>/bin directory can be
used both as a command-line utility and as the object file for the HTTPD Server Class.