iTP Secure WebServer System Administrators Guide (Version 7.5+)

These software products are optional for using the iTP Secure WebServer:
• NonStop Server for Java (NSJ) 2.0, if you plan to use Java servlets in the iTP Secure WebServer
environment. For information about the NonStop Server for Java 2.0, see the NonStop Server
for Java Programmer's Reference.
• NonStop Servlets for JavaServer Pages (NSJSP) V1.0 or later, if you plan to use Java servlets
in the iTP Secure WebServer environment. For information about installing NSJSP, see NonStop
Servlets for JavaServer Pages (NSJSP) System Administrator's Guide.
• NonStop Tuxedo, if you will be using Active Transaction Pages (ATP) and are not using IEEE
floating-point support. For more information about ATP, see the iTP Active Transaction Pages
(iTP ATP) Programmer's Guide.
• If you plan to use C run-time library to install EMS templates, see the C/C++ Programmer's
Guide.
In addition to the NonStop software products, you must have access to a Web client such as
Netscape Navigator or Microsoft Internet Explorer. If you will be running your server in secure
mode, you must have access to a secure browser.
Required Hardware
The hardware required for NonStop servers is:
• For NonStop servers, you must have a Gigabit Ethernet ServerNet adapter (GESA), or a
Token-Ring ServerNet adapter (TRSA).
For information on installing the TRSA, see the Token-Ring Adapter Installation and Support
Guide. For information on installing the GESA, see the Gigabit Ethernet Adapter Installation
and Support Guide.
Preparing Your System for the iTP Secure WebServer
This section describes the steps to prepare your NonStop system for the iTP Secure WebServer.
The iTP Secure WebServer is set up to come up out-of-box and run on TCP/IP process $ZTC0,
using a port that is configured during the installation process. You can use multiple TCP/IP processes
in the same iTP Secure WebServer environment.
1. Verify that the OSS environment is active. Use the STATUS command to determine that the
OSS File Manager process $ZFMnn and the OSS Pipe Server process $ZPPnn (where nn is
a processor number) are running on each of your processors.
2. Verify that the TCP/IP subsystem is running. Using SCF, verify that the host name and host ID
are specified. For more information, see the TCP/IP Configuration and Management Manual.
3. If you intend to use the TCP/IPv6 or IP CIP for iTPWebServer operations, review the following
information:
Running the iTP Secure WebServer relies on the properly configured TCP/IPv6 or IP CIP
environment. Every processor specified in the Server CPUS command (in the httpd.config
configuration file) needs to be enabled to run TCP/IPv6 or IP CIP. In other words, the TCP6MAN
needs to be properly configured and run. As a result, there is a TCP6MON (the monitor
process) running on every processor specified in the Server's CPUS command. In the
configuration phase of the startup, the iTP Secure WebServer will validate the existence of
these processes. Also, at least one TCP6SAM (TCP socket access point) process must be
running. If not all these processes are running, the Auto-Accept feature will not be used. The
iTP Secure WebServer will fall back to using the conventional support for TCP/IP.
For information about configuring for TCP/IPv6 or IP CIP and LAN adapters, see Cluster I/O
Protocols (CIP) Configuration and Management Manual.
The access list of the SAC needs to include all processors designed to run httpd servers. You
must verify the configurations, because the list now should contain more processors. In
Preparing Your System for the iTP Secure WebServer 35