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

Installing the iTP Secure WebServer
iTP Secure WebServer System Administrator’s Guide—523346-002
2-5
Preparing Your System for the iTP Secure
WebServer
CPU that already has a number of httpd servers running is neither going to help
distribute the load nor improve performance. Note that load distribution has now
been moved down to the adapter level by use of the round-robin filter. Additional
processes may create more dispatching costs for the CPU.
°
Specify the -address Command in All Accept Directives
It is also recommended to use the -address command in all Accept directives.
Unlike the conventional TCP/IP processes TCPSAM allows the httpd servers to
interface with all subnets configured in the Parallel Library TCP/IP environment.
The “accept ALL IP addresses” is literally ALL IP addresses defined in the entire
system. This may be more than you expected.
°
Rebalancing Servers Across CPUs
When a CPU is brought down, PATHMON is likely to restart a number of static
servers on other CPUs in order to keep the number of static servers as specified in
the NUMSTATIC server attribute. When the CPU is reloaded, PATHMON will not
automatically rebalance its servers among the CPUs. If there are extensive reloads
you may want to rebalance manually - using actions ranging from a simple
stopping of one or two servers, to a complete restart of the iTPWebServer. Again,
this behavior is not new to the PATHWAY system, it just may be more obvious
when everything from application to transport is vertically aligned.
°
You Can No Longer Use Restarth
Because the new product architecture no longer has a distributor working as a
buffer zone between the incoming connection requests and the httpd servers, new
servers cannot successfully bind to a local port unless the older httpd servers
cease their operations. Therefore the -restarth option is no longer supported if you
are using Parallel Library TCP/IP.
4. If you do not have Domain Name Server (DNS) running on your network, configure
and run DNS. You start DNS when you start TCP/IP. The out-of-box start-up
requires that the host name be fully qualified to match the DNS entry. The host ID
must be configured using the IP address defined for host name.
5. When you configure DNS, you must modify the file $SYSTEM.ZTCPIP.RESCONF
to point to the DNS name server you are using. For information about starting
DNS, refer to the TCP/IP Configuration and Management Manual.
6. For security, you should add a super ID (for example, super.webmastr) configured
for the OSS environment, and you should use this super ID instead of super.super
when installing the software.
7. Log on to the newly created super ID before installing the iTP Secure WebServer
software:
TACL> LOGON super.webmastr