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-90
Manual Deployment and Undeployment of Web
Applications
To start an NSJSP Server Class, complete the following steps:
1. Obtain the PATHMON name from the httpd.config file located in the <iTP
Installation Directory>/conf directory.
2. At the TACL prompt, run the following commands:
TACL> PATHCOM $<PATHMON name>
= START SERVER <server class name>
After running the START SERVER command, the system displays the following
message indicating that the server is started:
$YY66S: SERVER server_name, STARTED
Manual Deployment and Undeployment of Web
Applications
You can control the deployment of applications by using attributes in the server.xml
file. This section discusses the following topics:

Deploying Applications at Startup

Deploying Applications on a Running NSJSP Server
Deploying Applications at Startup
In the server.xml file, the location of web applications is specified by the appBase
attribute of the Host.
Note. The THAW SERVER command only needs to be entered when a status show that
the server class was frozen. If the THAW SERVER command is entered and the server
class was not frozen, an error message is displayed with the following text:
ERROR - *1060* SERVER <server class name>,NOT FROZEN
Note.

By default, an NSJSP Server Class includes four processes. The Admin Server Class
includes only two processes.

You can use either PATHCOM or PDMCOM to execute server class operations such as
stop, start, thaw and freeze.

Check the <NSJSP 6.1 Installation name>.<date>.log file to ensure that the
NSJSP server has restarted.

You can use either PATHCOM or PDMCOM to execute server class operations such as
stop, start, thaw and freeze.
Note.
The default host is localhost and the default appBase is
<NSJSP_HOME>/webapps.