As I mentioned in my previous message, you should NOT associate the PRG extension with FoxWeb. Your FoxWeb URLs should use the fwx extension, even though you are calling PRG files. FoxWeb strips the extension and looks for the right file as described in the diagram below.
Please study the Locating and Addressing Scripts topic of the FoxWeb documentation carefully. It provides detailed answers to your questions. Here's a summary:
The FoxWeb documentation describes how you can mix your scripts with static files and enable the Use Web Server's Directory Mappings option, but you need to be very careful, should you decide to go this route. Please make sure to read the "Storing Scripts in the Web Tree" section of the Locating and Addressing Scripts topic, as well as the "Preventing your data and programs from being downloaded over the Web" section of the Securing your Server topic before attempting this.
Sent by Tim Bowen on 05/26/2004 07:18:21 AM:
Ok, my foxweb has been running and NOT as a service either. I have the .prg associated with c:\inetpub\scripts\foxweb.exe. I do not use fwx's. But I want to test this to see if it really works so my quest is should "c:\inetpub\programs" contain my prgs and htm's?. I am confused about the 'DEFAULT PROGRAM ROOT'
Sent by FoxWeb Support on 05/25/2004 07:33:41 PM:
Have you started FoxWeb? You need to do so, using one of the methods listed in the Operating the FoxWeb Server topic in the FoxWeb documentation (and in the readme file). While you are setting up the server you should disable the Run as a Service option. This will allow you to click on the FoxWeb tray icon and see the status of your channels, as well as view the actual channel windows (to look for potential problems). You can view the channel windows by enabling the corresponding option in the FoxWeb Control Center and in the right-click context menu of the tray icon.
You should not associate prg files with foxweb.dll. You can still call them using the fwx extension. When a request gets received by FoxWeb (regardless of whether it contains the fwx script mapping, or explicitly points to foxweb.dll/exe), the software looks for fwx, prg and fxp files. The following diagram describes this process:
Sent by Tim Bowen on 05/25/2004 01:34:21 PM:
shoud l I associate the prgs with foxweb.dll as well?
I now get "could not connect to Foxweb broker" when trying to go here:
I ask this, should my foxweb default program root which is "c:\inetpub\programs" contain my prgs and htm's?
and should I use web servers directory mappings?
Sent by FoxWeb Support on 05/25/2004 12:08:20 PM:
The readme.txt file in the FoxWeb directory contains instructions on testing a new FoxWeb installation.
By the way, I recommend associating the fwx extension with foxweb.dll instead of foxweb.exe. The two programs offer identical functionality, but the dll uses the ISAPI protocol to communicate with the server, making it much more efficient, because the server does not need to start a new process with every request.
Sent by Tim Bowen on 05/25/2004 10:14:16 AM:
I've gotten by that error and IIS 5.0 is running. I'v got both .prg & .fwx executable paths set to c:\inetpub\scripts\foxweb.exe. I have my htm files in c:\inetpub\wwwroot. How can I test this to see if it's actually works?
Sent by FoxWeb Support on 05/24/2004 10:51:09 AM:
This sounds like a configuration error. I recommend that you initially disable the Run as Service option until you get FoxWe running properly. Once you have fixed the problem, you can re-enable this option.
You should also check the file fwstart.log for any error messages that would help you identify the problem.
Sent by Tim Bowen on 05/24/2004 08:19:48 AM:
Thanks, Is it normal not to be able to start my default web server until other foxweb components are configured correctly? I get the message "service did not respond to start or control request in a timely fashion".
Sent by FoxWeb Support on 05/21/2004 03:37:51 PM:
The Configuring your Web Server page in the FoxWeb documentation contains detailed instructions on how to configure IIS for use with FoxWeb.
Sent by Tim Bowen on 05/21/2004 01:15:18 PM:
I've decided with other existing issues not to "migrate" but start again fresh. I have a clean IIS 5.0 on the new server and need to go to work setting it up. Can you point me to a good resource that explains all the IIS steps.?
Sent by FoxWeb Support on 05/16/2004 07:47:05 PM:
After installing FoxWeb you will have to copy all files from the FoxWeb Program Root and its subfolders from the old server to the same location on the new server. The actual FoxWeb configuration would not take more than a couple of minutes if done manually, but I guess you could also export the old server and import it in the new server. You can use regedit.exe, highlight hkey_local_machine\software\Aegis Group and select the File\Export menu option. Copy the resulting reg file to the new server and double-click on it.
Regarding IIS, there is a utility that can copy Metabase information from one server to another, but I can't remember where I found it in the past. It may be included in all IIS installations, but more likely I got it from the IIS Resource Kit.
Sent by Tim Bowen on 05/13/2004 10:49:55 AM:
Can anyone advise on easiest way to move all I've got on my IIS 5.0/foxweb web server to new & different hardware? I've put so much configuration work into the current server that I'd hate to duplicate it manually. Thanks.