iTP Secure WebServer System Administrators Guide (Version 7.5+)

restart of the iTPWebServer. Again, this behavior is not new to the PATHWAY system, it just
might 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, if you are
using TCP/IPv6 or IP CIP, the -restarth option is no longer supported.
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. You should the host ID using the IP address defined
for host name.
5. When you configure DNS, you must modify the file, $SYSTEM.ZTCPIP.RESCONF for IPv4
addresses, $SYSTEM.ZTCPIP.IPNODES for IPv6 addresses, to point to the DNS name server
you are using. For information about starting DNS, see 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
Event Management Service (EMS) Template Installation
Before you install the iTP Secure WebServer, you should install the EMS templates. When the
templates are installed, each event reported by the iTP Secure WebServer appears in EMS displays
and logs using the subsystem identifier TANDEM.WEBSERV.version and an event number that
identifies the error or other event. For more information and examples, see “Error Messages”
(page 260).
If you do not install the EMS templates, all event messages from the iTP Secure WebServer appear
as if generated by OSS. Each message has the subsystem identifier TANDEM.OSS.version and
an event number that represents not the event itself but a severity ranking.
Follow this procedure after you unpax the iTP Secure WebServer pax file (as described in “Installing
and Configuring the iTP Secure WebServer” (page 38)):
To install a new set of EMS templates:
1. Log on as super ID:
TACL> logon super.super
2. Rename the files $system.zweb.newres and $system.zweb.newnres. (For example,
you could call them newres1 and newnres1.)
3. If you are using a NonStop K-series server, run the Configuration Utility Program (COUP),
including these commands:
ASSUME ALLPROCESSORS
ALTER EMS^TEMPLATES (RESIDENT newres1, NONRESIDENT newnres1)
If you are using a NonStop S-series or NonStop NS-series servers (Integrity servers and
BladeSystem servers), run the Subsystem Control Facility (SCF), including these commands:
ALTER SUBSYS $zzkrn, NONRESIDENT_TEMPLATES newnres1
ALTER SUBSYS $zzkrn, RESIDENT_TEMPLATES newres1
4. Run the template script to create the new versions of newres and newnres.
5. Run the install.EMS script, located in the
/usr/tandem/webserver/TnnnnHnn_DDMMMYY_SPR_Hnnn_nn/admin/conf directory,
as:
Event Management Service (EMS) Template Installation 37