This chapter provides a quick guide to getting your WASD package
installed, configured and serving. This covers initial installation.
- Unzip Package
Install the files following the guidelines in 4 - Installation and Update.
Note that more than one archive may be needed
(Source Archive, Object Module Archives).
- INSTALL Package
Server installation is performed using the INSTALL.COM procedure
(4.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 (4.9 - Quick-Check).
- Create Server and Scripting Accounts -
Create two independent accounts, one for executing the server, the other for
executing scripts (5.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
(7.2 - Maintaining Package Security).
- Copy Support and Configuration Files -
Copy the example server support and configuration files
(5.3 - Account Support Files).
- Install Scripts -
Selectively copy groups of scripts from package build directories into the
scripting directories.
- Configure Package
Following the execution of the INSTALL.COM procedure the package should
require only minor, further configuration.
Initially two files may require alteration.
- The startup file, possibly to set the local HTTPD$GMT logical (for systems
not supporting DTSS (e.g. DECnet-Plus)). Consider using the STARTUP_LOCAL.COM
file for other site-specific requirements
(5.3 - Account Support Files).
- The only configuration that should require immediate attention will be to
the mapping rules (14 - Request Processing Configuration).
More generally server runtime configuration involves
the considerations discussed in 6.1 - Site Organisation along with the
following aspects:
- Start Server
Execute the startup procedure. Get your browser and connect!
- 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
HT_ROOT:[LOG_SERVER] directory.
Remember, the basic installation's integrity can always be checked
as described in
4.9 - 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.15 - Reporting Problems.