WASD VMS Web Services - Install and Config

Welcome!

This chapter provides a quick guide to getting your WASD package installed, configured and serving. This covers initial installation.

1. Unzip Package

   Install the files following the guidelines in 2 - Installation and Update Note that more than one archive may be needed (Source Archive, Object Module Archives).

   If Transport Layer Security (TLS - a.k.a. Secure Sockets Layer - SSL) is to be used and a TLS/SSL server image to be built the WASD [Open]SSL product must be installed at this stage (see "WASD VMS Web Services - Features and Facilities"; 4.2 - SSL Functionality Sources WASD Web Services - Features and Facilities ). An existing HP SSL1 (HP SSL is obsolete) for OpenVMS product requires no additional step. If the WASD [Open]SSL package it must UNZIPed into the [.WASD_ROOT] tree at this stage.

   $ SET DEFAULT [.WASD_ROOT]
   $ UNZIP device:[dir]archive.ZIP
   

2. INSTALL Package

   Server installation is performed using the INSTALL.COM procedure (2.7 - Installation DCL Procedure).

   • Build Package - Compile and link, or just link supplied object files to produce VMS executables for the system's version of VMS.
   • Check Package - Check basic operation of the package (2.10 - Quick-Check).
   • Create Server and Scripting Accounts - Create two independent accounts, one for executing the server, the other for executing scripts (3.1 - VMS Server Account). If quotas are enabled on the target disk provides an ambit allocation for these accounts. Review this at some stage.
   • Set Package Security - This sections traverses the newly installed tree and sets all package directories and files to required levels of access (5.3 - Maintaining Package Security).
   • Copy Support and Configuration Files - Copy the example server support and configuration files (3.3 - Account Support Files).
   • Install Scripts - Selectively copy groups of scripts from package build directories into the scripting directories.

3. Configure Package

   Following the execution of the INSTALL.COM procedure the package should require only minor, further configuration.

   Initially two files may require alteration.

   1. The startup file, possibly to set the local WASD_CONFIG_GMT logical (for systems not supporting DTSS (e.g. DECnet-Plus)). Consider using the STARTUP_LOCAL.COM file for other site-specific requirements (3.3 - Account Support Files).
   2. The only configuration that should require immediate attention will be to the mapping rules (12 - Request Processing Configuration).

   More generally server runtime configuration involves the considerations discussed in 4.2 - Site Organisation along with the following aspects:

   • Configuring the HTTP server run-time characteristics (4 - Configuration Considerations).
   • Mapping request paths to the VMS file system, and to other things such as scripts (12 - Request Processing Configuration).
   • Customizing some messages (or all if non-English language environment) (10 - Message Configuration).
   • Establishing an authentication and authorization environment.

4. Start Server

   Execute the startup procedure. Get your browser and connect!

5. Find Out What's Wrong :^(

   Of course something will not be right! This can happen with the initial configuration and sometimes when changing configuration. The server provides information messages in the run-time log, look in the WASD_ROOT:[LOG_SERVER] directory.

   Remember, the basic installation's integrity can always be checked as described in 2.10 - Quick-Check. This uses the configuration files from the [EXAMPLE] directory, so provided these have not been altered the server should execute in demonstration mode correctly.

   Can't resolve it? See 2.17 - Reporting Problems.