WASD Configuration – Introduction

WASD Configuration

1.Introduction

WASD is outlined in the Introduction and Package Overview sections of the WASD Features document.

Installation and update of the package is covered by WASD Installation.

This document provides detailed configuration instructions of the WASD Web Services package.

Following installation the package should require only minor further configuration for basic serving.

WASD configuration is performed using the contents of five files located using logical names

WASD_CONFIG_AUTH	request authorization control
WASD_CONFIG_GLOBAL	global server configuration
WASD_CONFIG_MAP	request processing control
WASD_CONFIG_MSG	provides server messages
WASD_CONFIG_SERVICE	specifies services (virtual servers)

along with server CLI parameters commonly provide by startup DCL procedures.

Initially two files may require alteration.

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 (Account Support Files in WASD Installation).
The only configuration that should require immediate attention will be the mapping rules (10. Request Processing Configuration).

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

Configuring the HTTP server run-time characteristics (2. Configuration Considerations).
Mapping request paths to the VMS file system, and to other things such as scripts (10. Request Processing Configuration).
Customizing some or all messages (8. Message Configuration).
Establishing an authentication and authorization environment (11. Authorization Configuration (Basics)).