iTP Secure WebServer System Administrators Guide (Version 7.5+)

TCP/IPv6
TCP/IPv6 has multiple listener sockets on the same port. TCP/IPv6 allows the server direct access
to the communication environment from their own processors instead of having to communicate
via the processor that contains the HP TCP/IP process. This is done by linking to a system library
containing the TCP/IP procedures and allowing the server to call the functions that are performing
TCP/IP-related processing in its own context.
Running with the Auto-Accept feature, an iTP Secure WebServer no longer requires its Distributor
component. The httpd servers assumes the listening in addition to the distributing functions of the
Distributor. The Distributor server class is completely removed from the PATHWAY environment.
Running the iTP Secure WebServer relies on the properly configured TCP/IPv6 environment. Every
processor specified in the Server CPUS command (in the httpd.config configuration file) must be
enabled to run TCP/IPv6. The TCP6MAN must be properly configured and running. As a result,
a TCP6MON (the monitor process) runs on every processor specified in the Server's processor
command.
Unlike the conventional TCP/IP subsystem, the TCP/IPv6 enables iTP Secure WebServer to create
a listening socket on each of these processors. By creating a listening socket on each of these
processors, the httpd servers provide the listening capability for themselves. Therefore, mixing
TCP/IPv6 with conventional TCP/IP subsystems is not permissible. If both, TCP6SAM process and
conventional TCP/IP process are specified as the transport service providers, the Auto-Accept
feature will not be enabled. The iTP Secure WebServer will be running as a conventional TCP/IP
configuration.
IP CIP
The iTP Secure WebServer works the same way with IP CIP as it does with TCP/IPv6. However,
IP CIP enables all the httpd servers to assume the listening role (as opposed to one per processor
in TCP/IPv6).
iTP Secure WebServer httpd
The iTP Secure WebServer httpd has two main functions:
• A file server. The httpd process transfers and stores files, such as HTML documents.
• A message-switching facility. The httpd process forwards messages from Web clients to
application programs.
The httpd process is implemented as a server class in NonStop TS/MP. Therefore multiple httpd
processes can execute in parallel; the number of processes fluctuates automatically in response to
changes in workload. NonStop TS/MP can also restart a server process that fails. (The iTP Secure
WebServer uses the default value of the PATHCOM AUTORESTART parameter.)
PATHMON Process
The PATHMON process provides centralized monitoring and control of a PATHMON environment
consisting of server classes and other types of objects. You establish the operational parameters
for the PATHMON environment, including the characteristics of individual server classes, by creating
a PATHMON configuration file. Thereafter, you can use the PATHCOM utility to make configuration
changes and obtain information from the PATHMON process.
Multiple PATHMON environments can run on the same NonStop system. For example, the iTP Secure
WebServer Administration Server has its own PATHMON environment, separate from the iTP Secure
WebServers environments it manages. (If you have multiple iTP Secure WebServer environments
on the same system, you still need only one PATHMON environment for the Administration Server.)
Each PATHMON environment has a separate, uniquely named PATHMON process.
iTP Secure WebServer Architecture 31