WASD Hypertext Services - Technical Overview

[next] [previous] [contents] [full-page]

3 - New to WASD? Start Here!

This chapter provides a quick guide to getting your WASD package installed, configured and serving. This is for initial installation. Updates are another matter.

  1. Unzip Package

    Install the files following the guidelines in 4 - Installation and Update.

  2. Check Package

    Check the operation of the basic package as recommended in Quick Check.

  3. Consider Local Setup

    Stop and consider local file system organisation.

    Refer to comments in 4.1 - Local Setup Suggestions and 4.2 - Organizing Documents.

  4. Create Server Account

    Using the VMS AUTHORIZE utility and the recommendations in 5 - Server Account and Environment provide an account for the HTTPd server process. Pay particular attention to process quotas.

  5. Copy Server Support Files

    Copy the following files from HT_ROOT:[EXAMPLE] into the server account's home directory (ensuring the server account has read and execute permission for files and directory).

    Copy the startup file, STARTUP.COM from the same location into the local directory decided upon in step 3.

  6. Edit Server Support Files

    The only file requiring modification should be the startup file, and then only if non-recommended locations have been chosen for configuration files, etc. Check anyway! Relevant information is provided in 5.2 - Account Support Files.

  7. Copy Configuration Files

    Copy the following files from HT_ROOT:[EXAMPLE] into the local configuration directory decided upon in step 3 (ensuring the server account has read permission).

  8. Edit Configuration Files

    Server configuration involves the following aspects.

    Initially the only configuration that should be required will be to the mapping rules, see 8 - Mapping Rules.

    Aspects to be considered later.

  9. Start Server

    Execute the startup procedure. Get your browser and connect!

  10. 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 it's run-time log, look in HT_ROOT:[LOG.SERVER]

    Remember, the basic installation's integrity can always be checked as described in 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 4.3 - Reporting Problems.


[next] [previous] [contents] [full-page]