iTP Secure WebServer System Administrator's Guide (iTPWebSvr 5.1+)
Installing the iTP Secure WebServer
iTP Secure WebServer System Administrator’s Guide—522659-001
2-12
Test-Starting the Administration Server and the iTP
Secure WebServer
Test-Starting the Administration Server and the iTP
Secure WebServer
Use the following procedure to verify your configuration:
1. Start the Administration Server by executing the start script:
: cd /usr/tandem/webserver/admin/conf
: ./start
2. Use a web client to connect to the Administration Server through its IP address or
DNS name (as specified during installation).
The web client displays the iTP Secure WebServer Administration Server home
page.
3. Click the View button to view your configuration files or the Edit button to edit
those files.
4. Click the Start or Restart button to start the iTP Secure WebServer.
5. Check the EMS log file for startup messages.
Section 6, Managing the iTP Secure WebServer Using Scripts, contains more
information about starting, stopping, and managing the server in other ways. But to
complete preparation, read whichever of the following sections apply to you.
If You Are Planning to Use SSL or PCT Encryption
If you plan to use encryption provided by the Secure Sockets Layer (SSL) or the
Microsoft Private Communications Technology (PCT), follow the procedures in
Section 4, Configuring for Secure Transport
, to obtain a certificate from a CA and
generate a public/private key pair to use during runtime.
If You Are Planning to Use WebSafe2 Encryption
If you plan to use the iTP Secure WebServer with the WebSafe2 unit, follow the
procedures in Section 5, Integrating the WebSafe2 Internet Security Processor (WISP),
to add the WebSafe2 unit to the iTP Secure WebServer environment, to obtain a
certificate from a CA, and to generate a public/private key pair to use during runtime.
If You Are Using the Nonsecure Version
If you are using the nonsecure version of the iTP Secure WebServer, refer to Section 7,
Configuring the iTP Secure WebServer, to learn how to use configuration directives to
customize the server environment.
Note. Certain versions of Microsoft Internet Explorer do not accept self-signed test certificates.