iTP Secure WebServer System Administrator's Guide (iTPWebSvr 5.1+)

Installing the iTP Secure WebServer
iTP Secure WebServer System Administrator’s Guide—522659-001
2-3
Preparing Your System for the iTP Secure
WebServer
Preparing Your System for the iTP Secure
WebServer
This section describes the steps necessary 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, ensure that the host name
and host ID are specified. Refer to the TCP/IP Configuration and Management
Manual for more information.
3. If you are intending to use the Parallel Library support of TCP/IP for iTPWebServer
operations, read the following information.
Running the iTP WebServer relies on the properly configured Parallel Library
TCP/IP environment. Every CPU specified in the Server CPUS command (in the
httpd.config configuration file) needs to be enabled to run Parallel Library TCP/IP.
In other words, the TCPMAN needs to be properly configured and run. As a result,
there is a TCPMON (the monitor process) running on every CPU specified in the
Server’s CPUS command. In the configuration phase of the startup, the iTP
WebServer will validate the existence of these processes. Also, at least one
TCPSAM (TCP socket access point) process must be running. If not all of these
processes are running, the Auto-Accept feature will not be used. The iTP WebServer
will fall back to using the conventional support for TCP/IP.
For information about configuring for Parallel Library TCP/IP, refer to the TCP/IP
(Parallel Library) Configuration and Management Manual.
This manual is especially important for the configuration of the LAN adapter(s). The
access list of the SAC needs to include all CPUs designed to run httpd servers. This
is not new information, but just a reminder to double-check the configurations
because the list now should contain more CPUs than previously. In conventional
TCP/IP, a TCP/IP process is usually running on 2 CPUs - a primary and a backup.
For Parallel Library TCP/IP, if the application is running on all the other 14 CPUs,
then all of those need to be Parallel Library TCP/IP-enabled and must be in the
access list.
Parallel Library TCP/IP-enabled means that there should be a TCPMON process
running on that CPU. In order for the httpd servers to function properly, all these
processes must be in place. Socket errors will be reported if a TCPMON is not
running on a CPU that attempts to run a httpd process. The httpd server is designed
to retry the bind request if it fails. Repeated bind failures may indicate that a CPU is
not Parallel Library TCP/IP-enabled.