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 Guide596210-006
4-89
Server Class Operations
After you enter the STOP SERVER command, the SCP1 Server Class’s processes
running under the $zweb PATHMON are stopped. To view the status of the SCP1
Server Class, enter the following commands:
PDMI 1>> OPEN $zweb,$yweb
PDMI 2>> STATUS SERVER SCP1
The following output is displayed:
PATHMON : \POS02.$ZWEB
SERVER #RUNNING ERROR INFO
SCP1 0
PATHMON : \POS02.$YWEB
SERVER #RUNNING ERROR INFO
SCP1 2
There are now only two SCP1 processes running under the $yweb PATHMON and
none under the $zweb PATHMON.
Forced Shutdown
To stop the NSJSP Server Class immediately, run the iTP Secure WebServer stop
script:
OSS: cd <iTP Installation Directory>/conf
OSS: ./stop
Running the stop script does not allow NSJSP processes to perform shutdown
operations before shutting down. One such shutdown operation is to persist all the in-
memory sessions to a persistent store, if configured.
Starting NSJSP
After configuring NSJSP and starting the iTP Secure WebServer, the NSJSP Server
Classes will also be started. If the NSJSP Server Class TS/MP configuration has not
been changed, but an NSJSP Server Class has been stopped, the NSJSP Server
Class can be started without restarting the iTP Secure WebServer.
To start an NSJSP Server Class, run the start script from the <iTP Installation
Directory>/conf directory in the iTP Secure WebServer environment:
OSS: cd <iTP Installation Directory>/conf
OSS: ./start
Note.
For information on the PDMCOM commands, see the TS/MP Release Supplement
Manual.
For information on the PATHCOM commands, see the TS/MP System Management
Manual.