Web Connection includes a host of tools for configuring your Web Site they consist of:

• The Web Connection Management Console
  This console lets you create project and configure your server. The Configure Server is especially useful as it can do all of the things required to configure a Web Connection application including creating a virtual, scriptmap, setting up an Application Pool and configuring DCOM operation. This is the recommended way to do this!

• Command line utilities
  These are also based on the Management Console.exe file but can be run directly from the DOS prompt or from a VFP IDE. See the Management Console Command Line Interface. These options allow you to create virtuals, configure scriptmaps, set autologon and many other options. The functions are also directly accessible to your own applications via the CONSOLE project.
  

The setup program and the various Project and Process Wizards should create all the Web site configuration settings for you automatically. But under certain circumstances it's possible that the new settings don't take. In particular you may find that virtual directory and script map settings didn't take.

For those of you that want to know or don't trust utilities here's how to do the dirty work by hand.

For manual installation on IIS 7 or later please see:
IIS 7 Configuration

For manual installation on IIS 6 and Windows 2003
Windows 2003 Configuration

Manually configuring IIS under Windows NT/2000/XP/Windows Server

Making the appropriate entries in IIS is fairly straightforward. You can use the IIS Management Console to perform these task via an easy to use GUI interface.

Creating a virtual directory

• Bring up the IIS Adminstration Tool which can be found under the Adminstrative Tools

• Select the Web site you want to configure. Typically this will be the default Web site or the first in the list.

• Select New | Virtual Directory

• A Wizard will pop up and ask for a physical disk path for the virtual. Select a path like d:\inetput\wwwroot\MyVirtual. If wc.dll will reside in this directory make sure you check the Executable Files option in the Wizard - otherwise Script support is all that's required.

  If the directory exists below the Web root, you may not be able to create the virtual through the Wizard as the MMC sees a naming conflict with the existing directory. In this case simply select the directory from the Web site's directory listing and right click, then click Properties. Go down to the Application Settings setting and click on the Create button to create the virtual directory. As above check the Execute Permission to Scripts and Executables if you have wc.dll in this directory, otherwise set it to Scripts.
  

Creating Script Maps

• To set up script maps go back to the Web root . Right click and select Properties and select the Home Directory tab. Click the Configuration button which brings up a page with App Mappings, which are script maps. Each script map is a file extension that's mapped to an executable file such as the Web Connection ISAPI extension DLL. Click Add and point at the wc.dll file and select an extension (such as wc, wcs) to be mapped.

  

  Make sure that the 'Check that file exists' checkbox is unchecked!
  Make sure that you have the 'Check that File exists' checkbox unchecked! If this flag is checked dynamic pages that don't have a file on disk will not run. For example most of the sample page links don't include an underlying disk file.
  
  On XP OK button stays disabled
  On Windows XP there's a UI bug that causes the OK button not to enable after you've entered your settings. To get this to work put a period in front of the script map (ie. .wp). Also make sure that the file you've picked exists - use the Browse button to make sure. This is an XP specific bug.
  

• Web Connection installs the following extensions in its install and new projects: WC, WCS, , WCSX, WWSOAP. Additionally WWD (for the Demo app), WWT (for the Message board), BLOG (for the Blog sample) are installed for the full product installation.
  

Script maps by default are installed on the new virtual directory only, but you can optionally install them at the root of the server in which case they are visible throughout the entire Web site. Typically you'll want local script maps only, global scriptmaps can be useful if your application is site-wide or wants to run in various different virtual directories.

Make sure your temp directory has full rights for IUSR_
It's vital that you configure the directory that you choose for Web Connection temp file creation (set in wc.ini with PATH= and your app's INI file as TEMPFILEPATH=) has FULL rights configured for the IUSR_ account. If you're running NTFS use the NT Directory permissions to configure this. With FAT set up the TEMP path for sharing and make sure that IUSR_ or Everyone is included in the list.

Note: The temp path does not have to be your system TEMP path, although that's the logical place to put this file. I personally prefer to use a path such as d:\temp\wc so the directory is isolated and this is the installation default.

Using the wwWebServer Class to create configurations programmatically

Web Connection ships with a class library called WebServer.vcx which lets you programmatically configure the Web server. To do so you can use like the following from the VFP Command Window:

DO CONSOLE WITH "SPLASH"
o=CREATE("wwWebServer","IIS4")
o.CreateVirtual("wconnect","c:\inetput\wwwroot\wconnect\")
o.CreateScriptMap(".wc","c:\inetput\wwwroot\wconnect\wc.dll")

The following server types are supported:

IIS6 - IIS6 is used under Windows Server and sets up a Web Connection Application Pool
IIS4 - IIS4 and IIS5 and PWS 4 and 5 under Windows NT
IIS3 - IIS 3 and PWS 3 under Windows NT
PWS4 - Personal Web Server 4.0 Windows 98
PWS3 - Personal Web Server 1.0 and 3.0 Windows 95

Using the Server Configuration Wizard

You can also use the Management Console's Server Configuration Wizard to create Virtual directories and script maps.

These are the tools the Web Connection Setup uses internally to configure the server, so if Setup fails to install settings it's possible that the wwWebserver class and the Console will not do the trick and you have to follow the manual steps outlined above.

See also

Server Configuration Wizard | Management Console Command Line Interface