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-3
Required Hardware
other PATHMON environment on the same NonStop system. For more information,
see Install a WISP on page 2-17 and The WebSafe2 Interface Driver (WID) on
page 5-3.
•
If you plan to use C run-time library to install EMS templates, see the C/C++
Programmer’s Guide.
In addition to the NonStop software products, you must have access to a Web client
such as Netscape Navigator or Microsoft Internet Explorer. If you will be running your
server in secure mode, you will need access to a secure browser.
Required Hardware
The hardware required for NonStop servers is:
•
For a NonStop K-series server, you must have a 3615 Ethernet controller or a 3616
Token Ring controller.
For information about installing the 3615 Ethernet controller or the 3616 Token
Ring controller, see Configuring Controllers for NonStop Systems.
•
For NonStop servers, you must have an Ethernet 4 ServerNet adapters (E4SA), a
Gigabit Ethernet ServerNet adapter (GESA), or a Token-Ring ServerNet adapter
(TRSA).
For information about installing the E4SA, see the Ethernet Adapter Installation
and Support Guide. For information on installing the TRSA, see the Token-Ring
Adapter Installation and Support Guide. For information on installing the GESA,
see the Gigabit Ethernet Adapter Installation and Support Guide.
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, check that the host name
and host ID are specified. For more information, see the TCP/IP Configuration and
Management Manual.
Note. WID and WISP are compatible only with systems running on G-series RVUs.