Go to Step 1

---

The setup program guides you through the first time configuration of Web Connection for your Web server. The setup process performs the following tasks automatically. For reference I also mention how you can configure these things manually.

• Creates the wconnect script directory
  This directory contains the wc.dll ISAPI extension and also the default Admin page that allows you to administer the server remotely. This task can also be performed manually in the IIS Management Console by selecting the directory and creating a virtual.

• Configures the directory with Execute rights
  Execute rights are required in the script directory in order for wc.dll to be able to be executed directly or through script mapping. This can also be configured manually by selecting the directory in the IIS management console and clicking on the Execute rights (or selecting Script and Execute combo in IIS 5).

• Configures a temporary directory
  A temp directory for Web Connection message files are required when running file based messaging. In this mode message files are exchanged between the Web Server and the Visual FoxPro server. The directory holds these files. Directory must allow FULL access to the annonymous Web user account( IUSR_ <machinename> on IIS) or Everyone account.

• Creates scriptmap entries to allow direct execution of WC, WCS, FXP files
  Web Connection supports scripting as part of the framework so you can create HTML pages that contain embedded script or template code. These script maps point at wc.dll and let the framework parse the requests. You can also configure scriptmaps manually by selecting the Web root in the IIS Management Console, Home Directory, Configuration. The dialog allows you to add and remove script map extensions. Add WCS, WC, FXP and point them all at the full path of wc.dll installed in the Web directory (ie. after installation was complete).

• Copies Sample Files
  The setup program also copies the sample pages and images to the Web directory you created. The main files are default.htm which is the main demo page and admin.asp which is the administration page. admin.asp is important and should be copied for every copy of wc.dll.

• Sets up the configuration files
  Set up also configures wc.ini and your wcDemo.ini where wcDemo.ini will be you main application's configuration file which will vary by name depending on the project name. The most important settings in these files are the Path (wc.ini) and TempFilePath (wcDemo.ini) and Template (wc.ini and wcDemo.ini) which must match in both files so that file based messaging can find the message files.

These settings are the basic settings that must be performed for a Web Connection installation. The Setup program as well as the Web Connection Management Console New Project Wizard perform these task for you automatically, but it's important to understand what happens behind the scenes in case these settings do not work or are accidentally changed. If you or your administrator needs to know what happens with Microsoft Web servers or you want to manually configure settings check out the topic manually configuring Microsoft Web Server.