WASD Install and Update

3.Update

Before Updating

• Review the original installation instructions to refresh the various considerations involved.
• Some insurance on the directory tree is recommended in case the update should fail or otherwise be unusable or problematic (of course, this is good advice whenever about to make major changes to anything!) This may be in the format of a regular site backup, special pre-update backup, or special pre-update ZIP archive of the directory tree. The latter two could be accomplished using commands similar to the following:
  $ BACKUP WASD_ROOT:[000000...] location:WASDROOT.BCK/SAVE/VERIFY $ ZIP "-V" location:WASDROOT.ZIP device:[WASD_ROOT...]*.* $ ZIP "-T" location:WASDROOT.ZIP

  If using ZIP then ensure that a previous version of the target ZIP file does not already exist. If it does then that version is updated, a new version is not created.

• For existing files a new version is created (the first time this is about to occur the UNZIPper requests permission – either "A" for all, or "y" or "n" or a per-file basis).
• It is possible to selectively extract portions of a tree if something has become damaged. This would be accomplished by specifying what needs to be extracted from the archive (instead of the default all), as illustrated by the following example where only the Alpha object modules are extracted.
  $ SET DEFAULT device:[000000] $ UNZIP device:[dir]archive-AXP.ZIP ht_root/src/httpd/obj_axp/*.*

3.1Package UNZIP

Updating a package follows a similar process to installation.

The ZIP archive will contain brief installation instructions. Use the following command to read this and any other information provided.

It is recommended to check the integrity of, then list the contents of, the archive before UNZIPing.

The archive contains the complete directory tree. Hence it is necessary to SET DEFAULT into the parent directory of the WASD_ROOT logical name, as with the following example.

Source Archive, Object Module Archives

If a complete build is planned then only the main archive is required. If a link-only build then an additional archive for each site architecture must be UNZIPed.

WASD OpenSSL

Building an SSL-capable version of the server is a common requirement.

As described in VSI OpenSSL SSL111-V0101-1S and SSL3-V0300-7 it is now possible to install VSI OpenSSL releases on pre-V8.4 VMS. This is the recommended approach to providing and maintaining OpenSSL for WASD.

WASD SSL is discussed in detail in Transport Layer Security of WASD Features and Facilities.

DCL Procedure UPDATE.COM

3.2UPDATE.COM Procedure

The UPDATE.COM procedure assists with subsequent updates of WASD. It assumes a vanilla setup, using the standard directories and account environment described in this document. All sections prompt before performing any action and generally default to "no". Read the questions carefully!

Of course it is best (read mandatory) for the server to be shut down during an update!

After UNZIPing the updated package do the following:

It provides the following functions:

1. Build Executables – Either compile sources and link, or just link package object code to produce images for the local version of VMS. If the system has a suitable SSL toolkit the installer is requested whether an SSL enabled version be built.
2. Server Quick-Check – Executes a procedure that runs up the HTTPd in demonstration mode. Allows evaluation/checking of the basic package (2.10 Quick-Check).
3. Server Support/Configuration Files – Copies changed example HTTP server configuration and support files from the [EXAMPLE] directory to the [HTTP$SERVER], [LOCAL] and [STARTUP] directories.
4. Update Scripts – Selectively copy groups of scripts from package build directories into the scripting directories.
5. Reapply Package Security – This section traverses the updated tree and sets all package directories and files to required levels of access. For directory settings see Recommended Package Security in WASD Configuration.
6. Post-Update Cleanup – Prompts for permission to execute the post-update procedure described below.
7. Purge Files – Prompts for permission to purge the entire WASD_ROOT:[000000...] tree.

If declined during the update procedure the post-update steps 6 and 7 can be performed at any subsequent time using

3.3Re-Linking

After a major update to the operating system the package may refuse to start, reporting the message

This implies the executables require re-linking for your particular version of VMS. This can be accomplished quite simply, perform the linking section only of the UPDATE.COM Procedure.

3.4Building using MMS

The Module Management System (MMS)

VSI DECset for OpenVMS Guide to the Module Management System   [PDF]

may be used to build WASD when installed on an ODS-5 volume (MMS is case-sensitive).

The basic MMS build without a VSI (HP/DEC) C compiler requires the respective WASD object file kit installed. Without object files the package will (attempt to) be compiled then linked. Below are some examples for building against the various SSL kits.

To cross-compile from IA64 to X86.

Relevant X86 shareable images (e.g. SSL111$LIBSSL_SHR32.EXE) must be copied to X86_XTOOLS$ROOT:[SYSLIB] to complete the build.

The MMS build comprises two elements, a small configuration module located in the [src] directory and the main build configurations in [src.mms].

/wasd_root/src/descrip.mms
/wasd_root/src/mms/

The MMS WASD build is courtesy of Mark Berryman.
Any non-trivial questions are best addressed to Mark.
He is contactable via the info-WASD mailing list.