WASD VMS Web Services - Install and Config

1 - New to WASD? Start Here!

next previous contents full-page


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.

    $ UNZIP device:[dir]archive.ZIP

  2. INSTALL Package

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

  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:

  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.

next previous contents full-page