[0001] [0002] [0003] [0004] [0005] [0006] [0007] [0008] [0009] [0010] [0011] [0012] [0013] [0014] [0015] [0016] [0017] [0018] [0019] [0020] [0021] [0022] [0023] [0024] [0025] [0026] [0027] [0028] [0029] [0030] [0031] [0032] [0033] [0034] [0035] [0036] [0037] [0038] [0039] [0040] [0041] [0042] [0043] [0044] [0045] [0046] [0047] [0048] [0049] [0050] [0051] [0052] [0053] [0054] [0055] [0056] [0057] [0058] [0059] [0060] [0061] [0062] [0063] [0064] [0065] [0066] [0067] [0068] [0069] [0070] [0071] [0072] [0073] [0074] [0075] [0076] [0077] [0078] [0079] [0080] [0081] [0082] [0083] [0084] [0085] [0086] [0087] [0088] [0089] [0090] [0091] [0092] [0093] [0094] [0095] [0096] [0097] [0098] [0099] [0100] [0101] [0102] [0103] [0104] [0105] [0106] [0107] [0108]
|1Introduction| |0Welcome!| |^ WASD is outlined in the |link%|../features/##Introduction| and |link%|../features/##Package Overview| sections of the |link%|../features/##|WASD Features| document. |^ Installation and update of the package is covered by |link%|../install/##|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 |table| |~ |. 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) |!table| |^ along with server CLI parameters commonly provide by startup DCL procedures. |^ |*Initially| two files may require alteration. |number| |item| 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 (|link%|../install/##Account Support Files++in++WASD Installation||). |item| The only configuration that should require immediate attention will be the mapping rules (|link|Request Processing Configuration||). |!number| |^ |*More generally| server runtime configuration involves the considerations discussed in |link|Site Organisation| along with the following aspects: |bullet| |item| Configuring the HTTP server run-time characteristics (|link|Configuration Considerations||). |item| Mapping request paths to the VMS file system, and to other things such as scripts (|link|Request Processing Configuration||). |item| Customizing some or all messages (|link|Message Configuration||). |item| Establishing an authentication and authorization environment (|link|Authorization Configuration (Basics)||). |!bullet| |0Keep site-specific resources and server installation separate and distinct.| |2Troubleshooting?| |^ When initially installing or configuring WASD, and sometimes later where something breaks spectacularly, it is most useful to be able to gain insight into what the server is up to. |^ The |/go-to| tool is\ |"<span style=\"font-size:110%\">WATCH</span>||\ (yes, all capitals, and for no other reason than it makes it stand out). |^ WATCH is described in detail in |link%|../features/##WATCH Facility++of the++WASD Features and Facilities|| document. |^ For most circumstances WATCH can be made available for troubleshooting even if the configuration is significantly broken. This is done by using a skeleton-key to authorise special access into the server. |^ The skeleton-key is described in detail in |link%|../features/##Skeleton-Key Authentication++of the++WASD Features and Facilities|| document. |^ |*TL;DR| |^ Enable at the command-line with the username anything beginning with an underscore and at least 8 characters, same for the password length. |code| $ HTTPD /DO=AUTH=SKELKEY=_|/username||:|/password|| |!code| |^ Then using a browser access any available service, entering the above username (including underscore) and password when prompted. |block| |link%|/httpd/-/admin/report/WATCH|https://\<i\>the.host.name:port\</i\>\ /httpd/-/admin/report/WATCH| |!block| |^ The service administration facilities (of which WATCH is one) are also available and useful. |block| |link%|/httpd/-/admin/|https://\<i\>the.host.name:port\</i\>\ /httpd/-/admin/| |!block|