VWcms is distributed as a ZIP archive and can be UNZIPed onto either an ODS-2 or ODS5 volume.
$ SET DEFAULT HT_ROOT:[SRC]
and the optional object module archive
$ UNZIP <device>:[<directory>]VWCMS<nnn>-<arch>.ZIP
After this the VWcms executable must be compiled and linked
$ SET DEFAULT [.VWCMS]
or if the optional object module archive deployed merely linked
$ @BUILD_VWCMS LINK
and the executable placed into the scripting directory. For an Alpha this would be
$ COPY [.OBJ_AXP]VWCMS.EXE CGI_EXE:
Then the VWcms environment itself needs to be started. This defines required logicals and INSTALLs the image with required privileges.
Of course to make this a permanent part of the server environment it will be necessary to include this and other required logical names in system startup procedures. This and the associated server configuration is described in Site Configuration.
In WASD_CONFIG_GLOBAL (WASD v10 or later) or HTTPD$CONFIG (v9.3 or earlier) the CSS file suffix must be configured:
The server must be restarted following this change.