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

Installing NSJSP

NonStop Servlets for JavaServer Pages (NSJSP) System Administrator’s Guide—525644-003

2-5

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. This script is:

OSS: cd iTPWS_INSTALL_DIR/conf

OSS: ./start

2. When you see the EMS message

(#1) Servlet ServerClass started. Version

Procedure = T1222H50_30APR06_BASE_V500_1

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 more information, see

Starting NSJSP Through a Security Manager on page 3-23.

For information on JAAS support, see JAASRealm on page 3-39.

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:

OSS: cd iTPWS_INSTALL_DIR/conf

OSS: ./restart

Possible Error Conditions

The NSJSP class file (ServletJSPConnector.jar) and Servlets JNI

(libT1222.so) 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.

Stopping NSJSP

You can stop NSJSP in two ways by using the stop script, as described in the iTP

Secure WebServer System Administrator’s Guide, or by using the nsjsp_stop script,

described as follows.

The NSJSP script called nsjsp_stop is located in the iTPWS_INSTALL_DIR/conf

directory. This script, shown in Example 2-1 on page 2-6, enables the NSJSP container

to be stopped gracefully by invoking the servlet/jsp destroy() methods for

cleanups and flushing the persistent session data into a pre-configured persistent data

store.