iTP Secure WebServer System Administrator's Guide (iTPWebSvr 6.0+)
Using NonStop Servlets for JavaServer Pages 
(NSJSP)
iTP Secure WebServer System Administrator’s Guide—523346-002
9-16
Begin the Installation
In addition, when using a JVM binary in a location other than the default 
/usr/tandem/java, set the JAVA_HOME OSS environment variable to the 
alternate Java location prior to starting the environment. If not set, the default 
servlet.config file uses the Java binary at /usr/tandem/java.
Once the ./setupjava and ./setup scripts have run, do not delete or modify 
the version specific directory (/usr/tandem/webserver/servlet_jsp/
<version>) or its subdirectories as there are OSS symbolic links pointing back to 
that directory tree. If you do delete any of these directories or subdirectories, you 
will have to reinstall the entire product starting with unpaxing the product PAX file.
2. Verify the VPROC of the WebServer's /bin/servlet.ssc binary. There should be a 
T1222 vproc that matches with the <version> portion of the installation directory. If 
there is not a match, then an installation error has occurred and must be corrected 
before proceeding.
A running TCP/IP process is required when the NSJSP software is started. The 
default NSJSP installation assumes that the running TCP/IP process will be named 
$ZTC0. If $ZTC0 is not running, then the servlet.config file located in the 
iTPWebServer's /conf directory must be modified. The servlet.config file's 
"Server" directive must be modified to add a MapDefine that indicates the OSS 
process name of the correct TCP/IP process. For example, if the TCP/IP process 
name is $ZTCxx, then the servlet.config would be modified as follows:
Server $server_objectcode {
 ...
 MapDefine =TCPIP^PROCESS^NAME /G/ZTCxx
 ...
}
Failure to use the default $ZTC0 or a valid MapDefined TCP/IP process will result 
in an error indicating a SocketException with "Guardian or User Defined Error 14" 
(FENOTFOUND).
3. Start the iTP Secure WebServer using the start script (see the iTP Secure 
WebServer softdoc). You should then see the EMS message:
#7001: Servlet Server Class started
You can now access the NSJSP sample page from a web browser at URL:
http://hostname:<portnumber>/samples/Servlets/ 
Possible Error Condition.  The NSJSP servlet class files (iTP_Servlet_JSP.jar) and 
servlets JNI (libtandemservlet.a) must be the same version. If they do not match, startup of 
the NSJSP environment fails and a message reporting the error appears in the OSS 
syslog file.










