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

Installing NSJSP
NonStop Servlets for JavaServer Pages (NSJSP) System Administrator’s Guide—525644-002
2-6
Starting or Restarting NSJSP
6. Verify the VPROC of the $NSJSP_HOME/bin/servlet.ssc binary. There should
be a T1222 VPROC that matches the <version> portion of the installation
directory. If no match exists, an installation error has occurred and must be
corrected before proceeding.
7. To compile servlets in the NSJSP environment, update your OSS profile. After
installing NSJSP 5.0, include the servlet-api.jar file in the Java classpath.
For example:
$NSJSP_HOME/<version>/common/lib/servlet-api.jar
Starting or Restarting NSJSP
When the NSJSP software is started, a running TCP/IP process is required. This
process is set by the setup script.
1. To start NSJSP, run the start script from the iTPWS_INSTALL_DIR/conf
directory in the iTP Secure WebServer environment. The script starts the HTTPD
process using the httpd.config configuration file. The script is shown below:
OSS: cd iTPWS_INSTALL_DIR/conf
OSS: ./start
2. When you see the EMS message
(#1) Servlet ServerClass started. Version
Procedure = T1222V50_10NOV05_BASE_V500_2
you can access the NSJSP sample page from a web browser at URL:
http://hostname:portnumber/servlet_jsp/
NSJSP can also be started by using a security manager. For information on this, refer
to Starting NSJSP Through a Security Manager on page 3-24.
For information on JAAS support, see JAASRealm on page 3-40.
To restart NSJSP, use the restart script, stop or nsjsp_stop and start scripts in
sequence, as described in the iTP Secure WebServer System Administrator’s Guide,
or use the PATHCOM utility to freeze, stop, thaw, and start NSJSP. The restart
script is shown below:
OSS: cd iTPWS_INSTALL_DIR/conf
OSS: ./restart
Possible Error Conditions
The NSJSP class file (ServletJSPConnector.jar) and Servlets JNI
(libT1222.a) must be the same version; otherwise, startup of the NSJSP
environment fails and a message reporting the error appears in the
servlet_error.log file.