iTP Secure WebServer System Administrators Guide (Version 7.5+)

CN=Secure Transport Bootstrap Certificate
OU=Testing Only - Do not trust for Secure Transactions
OU=No Assurance - Self-Signed
OU=Generated date time PDT year
O=comm.company.com
NOTE: Commercial use of the ninety-day test certificates is prohitbited.
NOTE: Certain versions of Microsoft Internet Explorer do not accept self-signed test certificates.
Test-starting the Administration Server and the iTP Secure WebServer
Use this 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 Click 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.
For more information about starting, stopping, and managing the server in other ways, see section
5, “Managing the iTP Secure WebServer Using Scripts” (page 82). To complete the preparation,
choose one the following sections.
If You Plan to Use TLS or SSL Encryption
If you plan to use encryption provided by the Transport Layer Security (TLS) or the Secure Sockets
Layer (SSL), to obtain a certificate from a CA and generate a public/private key pair to use during
run time, follow the procedures in “Configuring for Secure Transport” (page 53).
If You Are Using the Nonsecure Version
If you are using the nonsecure version of the iTP Secure WebServer, to learn how to use
configuration directives to customize the server environment, see “Configuring the iTP Secure
WebServer” (page 94).
46 Installing the iTP Secure WebServer