VWcms kits may be downloaded from

http://wasd.vsm.com.au/wasd/

or a mirror site.

VWcms installation comprises three main steps.  These are covered in detail in the following sections.

1. VWcms kit build
   
   • Locations will vary between Apache (SWS), OSU and WASD.
   • Compiled locally or an image built from package object modules.
   • The image is then placed in the server scripting directory (or otherwise mapped into Web server space).
   • The startup procedure executed (image INSTALLed and logical names defined).
2. HTML editor
   
   • TinyMCE and/or FCKeditor are unarchived to a location in the file-system accessable to the Web server.
   • This file-system location must then be mapped into Web server space.
3. Site creation and configuration
   
   • A site comprises a directory in the file-system accessable to the Web server.
   • A logical name must be defined to locate this directory.
   • The directory must be mapped into Web-server space.
   • The basic files required for a site may be copied one of the VWcms example directories.
   • The site must be configured and content added.

VWcms Root

Although not mandatory (VWcms sites may be located anywhere in file-system the server account has access) for convenience of resource mapping it is suggested that all VWcms site directories be located under a single root directory using a concealed logical name.  For example

$ DEFINE /SYSTEM /TRANSLATION=CONCEALED VWCMS_ROOT DKA0:[VWCMS.]

MIME Types

The following file types must be mapped to MIME types by the server:

File Type	MIME Type
.CSS	text/css
.HTML	text/html
.JS	text/JavaScript
.XML	text/xml

Updating VWcms

An update of VWcms is very similar to an initial installation.  Just ensure that a backup of the site(s) is performed prior to update.   Then install the new kit.   Check the release notes for configuration changes, etc., that might need to be propagated to any existing sites.  Execute the startup procedure (primarily to INSTALL the new executable).

Updating HTML editor

When updating the release of the HTML editor remember that browsers cache Web content and the files comprising this are no different.  Of course a browser should be set to, and should, periodically revalidate its cache content.  However it's highly likely that unless a browser's cache is explicitly purged after an upgrade a mix of old and new components may produce unexpected and undesirable results!  Caution!