iTP Secure WebServer System Administrator's Guide (Version 7.0)

Installing the iTP Secure WebServer
iTP Secure WebServer System Administrator’s Guide—523346-012
2-4
Preparing Your System for the iTP Secure
WebServer
3. Read this information if you intend to use the Parallel Library support of TCP/IP for
iTPWebServer operations.
Running the iTP Secure WebServer relies on the properly configured Parallel
Library TCP/IP environment. Every processor 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
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 TCPSAM (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 Parallel Library TCP/IP and LAN adapters,
see TCP/IP (Parallel Library) Configuration and Management Manual.
The access list of the SAC needs to include all processors designed to run httpd
servers. You must carefully check the configurations because the list now should
contain more processors than previously. In conventional TCP/IP, a TCP/IP
process is usually running on 2 processors — a primary and a backup.
For Parallel Library TCP/IP, if the application is running on all the other 14
processors, and 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 processor. 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 processor that attempts to run a httpd process. The httpd server is
designed to retry the bind request if it fails. Repeated bind failures might indicate
that a processor is not Parallel Library TCP/IP-enabled.
•
Use One TCPSAM Process
Check that there is one TCPSAM process pair running on any two processors in
the system. It is recommended that you use only one TCPSAM process pair - even
where you are using more than one IP address. Unlike the conventional TCP/IP
processes, one TCPSAM process can provide socket interfaces for all IP
addresses configured in the Parallel Library TCP/IP environment. If you use more
than one, two httpd servers might attempt access to the same port and therefore
generate EADDRINUSE socket errors.
•
Use Static Servers
It is strongly recommended that you run as many static servers as you might need.
Creating dynamic servers is known to be expensive and will severely affect
response time - especially for the request waiting for the dynamic server to be
Note. The following conditions are applicable for TCP/IPv6 and IP CIP.