Chapter 1
Installation Requirements and Prerequisites
Before you can
install
the Secure Web Server for OpenVMS (based on
Apache), you should
verify that
your system meets the minimum hardware and software requirements
described
below.
1.1
Hardware Requirements
You can install
the
Secure Web Server for OpenVMS on any system running OpenVMS Alpha or
OpenVMS
I64.
1.2 Software Requirements
The Secure Web
Server
requires the following software:
·
HP OpenVMS Alpha Version 7.3-1 or higher, or OpenVMS I64
Version
8.2 or higher
(OpenVMS 7.3-1
requires
the C run-time library patch: VMS731_ACRTL (VMS731_ACRTL-V0300 or
later) available
from the
HP Services Patch
Database.)
·
HP TCP/IP Services for OpenVMS Version 5.3 or higher
1.2.1 MultiNet and TCPware Network
Products
If you are using
MultiNet
or TCPware from Process Software Corporation, instead of HP TCP/IP
Services for
OpenVMS, you should be aware of the following information.
The Secure Web
Server has
been tested and verified using HP TCP/IP Services for OpenVMS. There
are no
known problems running the Secure Web Server with other TCP/IP network
products
such as MultiNet and TCPware, but HP has not formally tested and
verified these
other products.
MultiNet and
TCPware
require ECO kits for the Secure Web Server. These ECO kits are subject
to
change. For the latest ECO kit information, contact Process Software
and ask
for the ECO kits required to run the Secure Web Server for OpenVMS.
Send
network connectivity questions regarding the Secure Web Server on
TCPware and
MultiNet via email to support@process.com.
1.2.2
CSWS_JAVA
CSWS_JAVA
includes the
following Apache
Jakarta
technologies: Tomcat
(JavaServer Pages 1.2, Java Servlet 2.3, MOD_JK, and MOD_JK2) and Ant.
(Note: Ant is
a partial implementation of the Jakarta Ant subproject and its use is
limited
to building the included sample web applications and simple
user-written web
applications for Tomcat.)
CSWS_JAVA has
retired
support for CSWS_JSERV. If you want to continue JSERV support,
download
CSWS_JAVA Version 1.1 from the CSWS_JAVA for HP Secure Web Server for
OpenVMS
web site at http://h71000.www7.hp.com/openvms/products/ips/apache/csws_java.html.
See the
CSWS_JAVA for HP
Secure Web Server for OpenVMS Installation
Guide and Release Notes for CSWS_JAVA requirements.
1.2.3
CSWS_PHP
PHP is a
server-side,
cross-platform, HTML embedded scripting language that lets you create
dynamic
web pages. PHP-enabled web pages are treated the same as regular HTML
pages,
and you can create and edit them the way you normally create regular
HTML
pages.
See the CSWS_PHP
for HP
Secure Web Server for OpenVMS Installation
Guide and Release Notes for CSWS_PHP
requirements.
1.2.4
CSWS_PERL
Perl has
become the premier scripting language of the Web, as most CGI programs
are
written in Perl. The Secure Web Server for OpenVMS supports an
optional kit,
CSWS_PERL. This kit includes MOD_PERL, an interface between Perl and
the Secure
Web Server which lets you write modules entirely in
Perl.
See the
CSWS_PERL for HP
Secure Web Server for OpenVMS Installation
Guide and Release Notes for
CSWS_PERL requirements.
1.2.5
Building the Apache HTTP Server from Source
Code
The Secure Web
Server V1.3-1
kit is based on Apache 1.3.26. Source code and instructions for
building an
Apache HTTP server for OpenVMS can be found at the Secure Web Server
for
OpenVMS web site at http://h71000.www7.hp.com/openvms/products/ips/apache/csws_source.html.
Chapter 2
Installation and Configuration
Read this
chapter to
install and configure the Secure Web Server for OpenVMS. Installation
and
configuration consists of the following steps:
1.
Read the release notes
2.
Install the server and optional modules
3.
Configure the server
4.
Review the post configuration checklist
5.
Test the installation
Detailed
instructions for
completing each of these steps are provided below.
2.1 Read
the Release Notes
Before you begin
the
installation, you should read the HP Secure Web Server for OpenVMS
Release
Notes.
2.2
Install the Secure Web Server and Optional Modules
If you are upgrading to
OpenVMS Alpha
Version 8.2, the currently available CSWS_JAVA V2.1, CSWS_PERL V1.1,
and Perl
for OpenVMS V5.6-1 kits will work properly.
New kits are
required for the Secure Web Server and CSWS_PHP on OpenVMS Alpha, and
for the
Secure Web Server and all of the optional kits on OpenVMS I64.
You
can install the Secure Web Server by itself or with one or more of the
optional
modules. You can install
the optional modules later, if you choose.
Before you
begin, do the
following:
1.
Decide what you want to install.
2.
Review the software requirements for the server and each
optional module
you are installing.
3.
Decide where you want to install the kit.
Note
The
Secure Web Server, CSWS_PERL, and CSWS_PHP must be installed in the
same
directory (required).
By
default, the Secure Web Server, CSWS_PERL, and CSWS_PHP are installed
in
SYS$COMMON. However, HP recommends that you specify another location.
CSWS_JAVA
can be installed into a different disk or directory from the Secure
Web Server.
(HP requires that you install CSWS_JAVA on an ODS-5 enabled disk. Your
installation of the Secure Web Server can remain on an ODS-2 disk.)
HP recommends that you
shut down
the Secure Web Server (and Tomcat, which runs as a separate
process) before
installing a new version of any component: CSWS, CSWS_PHP, CSWS_Perl,
or
CSWS_JAVA (Tomcat).
Follow these
instructions
to install the Secure Web Server by itself or with the optional
modules.
1.
Make sure you are logged in as a privileged OpenVMS user
(for
example, SYSTEM).
2.
Select UIC group and member numbers for the APACHE$WWW
account
that will be created by the installation procedure. HP recommends that
you use
an empty or new UIC group (without current members). Servers typically
use the
highest unused UIC group (for example, [370,1]).
To ensure that the UIC you
chose for APACHE$WWW has READ and WRITE access to the intended login
device, use the SHOW DEVICE/FULL command.
3.
Decompress the server kit with one of the following commands, depending on the
platform
on which you are installing the server kit:
$ RUN
CPQ-AXPVMS-CSWS-V0103-1-1.PCSI_SFX_AXPEXE ! on Alpha
$ RUN
HP-I64VMS-CSWS-V0103-1-1.PCSI_SFX_I64EXE ! on I64
The files
are expanded and are named CPQ-AXPVMS-CSWS-V0103-1-1.PCSI (on Alpha) and HP-I64VMS-CSWS-V0103-1-1.PCSI (on I64). Do not rename these
files.
4.
Start the installation with the PRODUCT INSTALL command.
Use the
/DESTINATION qualifier to specify a target device and directory for
the
installation. If you do not specify a destination, the software will
be
installed in SYS$COMMON. HP recommends that you specify another
location.
Note
Once you enter a
PCSI INSTALL
CSWS/DESTINATION=[destination] command, you cannot change the
installation location unless you remove CSWS and then reinstall it. To
change
the installation location when you upgrade to a new version of CSWS,
you must
first enter the PCSI REMOVE CSWS command, then enter PCSI INSTALL
CSWS/DESTINATION=[new-destination].
Review the
software
requirements for the server and each optional module you are about to
install.
To prevent installation problems, make sure the required software is
installed before you enter the
PRODUCT
INSTALL command.
To install the
server,
enter the following command:
$ PRODUCT INSTALL
CSWS
/DESTINATION=device:[directory-name]
To install the server and one or more
of the
optional modules, specify CSWS and the CSWS_nnnn kit name on
the PRODUCT
INSTALL command line, separated by commas.
(You must have previously expanded the optional kit in order to
install
it with the server.)
For
example, to install the server and CSWS_PHP, use the following
command:
$ PRODUCT
INSTALL
CSWS, CSWS_PHP /DESTINATION=device:[directory-name]
The installation
proceeds
and displays product information as well as post-installation
instructions. The
installation is finished when you see the DCL prompt ($).
After the
installation,
you must configure the Secure Web Server.
Note
Do not attempt
to start
the server or configure any optional modules before you have
configured the
server.
2.2.2 Sample Installation
Following is an
example
of the Secure Web Server product installation.
$
PRODUCT INSTALL
CSWS /DESTINATION=DKB300:[000000]
The
following
product has been selected:
CPQ AXPVMS CSWS V1.3-1 Layered
Product
Do you
want to
continue? [YES]
Configuration
phase starting ...
You will
be asked
to choose options, if any, for each selected product and
for
any
products that
may be installed to satisfy software dependency
requirements.
CPQ
AXPVMS CSWS V1.3-1
Hewlett-Packard Company & The
Apache
Software Foundation.
* This
product
does not have any configuration options.
Execution phase
starting ...
The
following
product will be installed to destination:
CPQ AXPVMS CSWS V1.3-1
USER$DISK3:[000000.]
Portion
done:
0%...10%...20%...30%...40%...50%...60%...70%...90%...100%
The
following
product has been installed:
CPQ AXPVMS CSWS V1.3-1 Layered
Product
CPQ
AXPVMS CSWS V1.3-1
Release notes are available in
SYS$HELP:CSWSxxx.RELEASE_NOTES.
HP highly recommends that you
read these
release notes.
For the most up-to-date
documentation,
including release notes,
Frequently Asked Questions
(FAQs), and
information about configuring
and running the HP Secure Web
Server,
please see the web pages at:
http://h71000.www7.hp.com/openvms/products/ips/apache/csws.html
Post-installation tasks are
required for
the HP Secure Web Server.
The OpenVMS Installation and
Configuration
Guide gives detailed directions.
This information is a brief
checklist.
Configure OpenVMS aspects of the
HP Secure
Web Server by:
$
@SYS$MANAGER:APACHE$CONFIG
If the OpenVMS username
APACHE$WWW does not
exist, you will be
prompted to create that
username. File ownerships are set to
UIC
[APACHE$WWW],
etc.
After configuration, start the HP
Secure
Web Server manually by
entering:
$
@SYS$STARTUP:APACHE$STARTUP
Check that neither SYLOGIN.COM
nor the
LOGIN.COM write any output to
SYS$OUTPUT:. Look especially for
a
$ SET
TERMINAL/INQUIRE.
Start the HP Secure Web Server at
system
boot time by adding the
following lines to
SYS$MANAGER:SYSTARTUP_VMS.COM:
$ file :=
SYS$STARTUP:APACHE$STARTUP.COM
$ if
f$search("''file'")
.nes. "" then @'file'
Shutdown the Apache server at
system
shutdown time by adding the
following lines to
SYS$MANAGER:SYSHUTDWN.COM:
$ file :=
SYS$STARTUP:APACHE$SHUTDOWN.COM
$ if
f$search("''file'")
.nes. "" then @'file'
Test the installation using your
favorite
Web browser.
Replace host.domain in the
following URL
(Uniform Resource Locator)
with the information for the HP
Secure Web
Server just installed,
configured, and
started.
URL http://host.domain/ should
display the
standard introductory page
from the Apache Software
Foundation. This
has the bold text "It
Worked! The Apache Web Server is
Installed
on this Web Site!" at the
top
and the Apache server logo prominently displayed at the
bottom.
If you do not see this page,
check the HP
Secure Web Server
release notes, particularly the
Frequently
Asked Questions section.
If you'd like to use secure
connections
with the HP Secure Web Server
then you'll need to create a
server
certificate. We recommend
that
you start by creating a 30 day
self signed
certificate using the
following certificate
tool:
$
@APACHE$COMMON:[OPENSSL.COM]OPENSSL_AUTO_CERT.COM
Once the certificate has been
created
you'll need to uncomment the
following directive in the
APACHE$COMMON:[CONF]HTTPD.CONF file to
enable SSL.
Include
/apache$root/conf/ssl.conf
Thank you for using the HP Secure
Web
Server.
2.3 Configure the Secure Web Server
After you have
installed
the Secure Web Server, you are ready to configure it.
The installation
wrote
values, such as the name of the directory where the Secure Web Server
is
installed, to the file:
SYS$COMMON:[SYSMGR]APACHE$CONFIG_DEFAULT.DAT
The information
stored in
this file provides the default values you see during configuration. Do
not try
to modify the contents of this file.
