wftk: Installation

As of version v0.5 (October 2000) there are very few tools for wftk installation. OK, there are no tools for wftk installation. You're on your own, in other words. Also, all we have is an AOLserver version of the task manager, so you'll need AOLserver. At this point I'm not even compatible with the current version of AOLserver; I'm still on v2.1 because I've been working so hard on wftk that I haven't had time to upgrade. So it's your fault. Anyway, assuming you have AOLserver v2.1 installation media, here's how to set up the wftk:

1. Unzip or untar the wftk archive. On Windows, with v0.5, this must be in the c:\wftk directory if you're going to use the precompiled code.
2. If you're compiling (i.e. Unix or you're a Windows renegade), update the localdefs.h file in the include directory to point to your installation path.
   If you're compiling with MSVC under Windows, update MSVC.BAT in the top directory to point to your MSVC directories. If you want to build a workspace and project files, feel free to contribute them back to the project, but I'm not going to mess with them.
3. If you're compiling, compile by running make in the three C-language directories. Sorry for the redundancy; I'll fix this kind of thing up in v1.0 or so. Under Windows, run build.bat in each directory instead of running make. You'll need Perl in this case, or modify build.bat to eliminate the call to LPML.
4. Install AOLserver from the media. If you've already got AOLserver installed, skip this step and the next one.
5. Using the AOLserver admin tool on port 9876 of your box (by default) add a virtual server. This will be your wftk server.
6. If you're running Windows, set up an ODBC datasource named wftk. If you want, use the wftk.mdb in the top-level directory. This probably won't scale terribly well, but it's a nice way to get your feet wet.
7. Point the pageroot of the virtual server to the top-level directory of your installation.
   Point the tclroot of the virtual server to the taskmgr directory.
   Configure your database information. Get ready to debug queries if you're not running PostgreSQL or Access/ODBC.
   Add the proper CGI extension for the CGI components; I'm using .cgi under Unix and of course it must be .exe under Windows.
   Here's an excerpt from my (Windows) nsd.ini for this server:

   [ns/server/server1]
   DirectoryFile=index.html, index.htm, index.shtml
   PageRoot=c:\wftk
   
   [ns/server/server1/cgi]
   Map=GET /*.exe
   Map=POST /*.exe
   
   [ns/server/server1/db]
   Pools=*
   DefaultPool=wftk
   
   [ns/server/server1/module/nssock]
   Port=80
   Hostname=phobos
   
   [ns/server/server1/tcl]
   Library=c:\wftk\taskmgr
   

   Do the same for your virtual server and you can't go wrong.
8. If you haven't already, restart AOLserver to get it to load those definitions.
9. You'll want to configure AOLserver's permissions to keep hands off of POST requests; by default, all POSTs are marked as password-only by AOLserver. Since our POST CGIs already handle permissions, we don't need AOLserver to meddle. So do this:
   • Go to the AOLserver admin page at [server]/NS/Admin.
   • Select the Access Control link.
   • Select the "Show All Records" link (that's in the fourth group of links down there)
   • Find the record for POST / and select that.
   • Select No restriction on users and No restriction on groups. Update.
10. Under Windows, find the DLLs in the expat/bin directory and copy them to windows\system.

Let me know where the holes are in these instructions. (Thanks to the guys at Consotec for finding the first one; I had neglected to document my fix to the permissions.)