 |  |
I've spent the past week banging my head against the wall trying to
FM5 WSC IIS (how to make it work the first time)
From: Noel Del More
Date: Friday, December 1, 2000
Time: 4:09:02 pm
configure the OG ISP Web Interface in a shared server environment.
Sean's (limited) documentation on the subject only mentions setting up
WSC IIS using the 'default' web site on a server which I'm sure works
just fine, but isn't exactly what I had in mind, I didn't want to use
the 'default' web site but rather a 'virtual host' web site.
I also searched the dickens out of the archived mail but was unable to
find anything that dealt with setting this up as a 'virtual host'.
He also mentioned (somewhere) the need to maintain a copy of OG ISP's
web pages both on the server and in the 'Web' folder in FM5 directory.
A couple of points which may help others are:
1. You can avoid maintaining two copies of the OG web files by
choosing the FM5 'Web' folder as the root (home directory) of your
virtual IIS web site in the IIS MMC, e.g. C:\Program
File\Filemaker\Filemaker Pro 5\Web
Unless Sean has a reason for recommending otherwise this is probably
the most painless was of dealing with OG Upgrades. Sean did tell me
that you can place the files in a sub-directory of the FM5 'Web'
folder but that all of the OG ISP web files would need to be edited in
order to affect that change.
I'd like to suggest to Sean that since FM5 Unlimited can be used to
host other databases, that he consider doing this as a change to the
OG ISP web structure, e.g. C:\Program File\Filemaker\Filemaker Pro
5\Web\OG ISP\ I think it would make life a little saner for all of
us.
2. If your configuring this as a virtual host, use the IIS MMC and
create a Virtual directory called "Scripts" and point that Virtual
Directory to the '<drive>:\Inetpub\Scripts' directory where WSC the
'FMWCS_ISAPI.dll' file, e.g. C:\Inetpub\Scripts
This 'step' is the one that resulted in the little bald spot on top of
my noggin, once the 'light' went on the OG IPS web site came right up
and worked as advertised.
3. Since this is a 'virtual host' you'll need to configure the Web
Companion to a port other than 80, Filemaker Recommends port 591.
4. In the WSC Admin Interface, you want to 'Configure By Host' and
selection only Troubleshoouter_.fp5 and MainMenu.fp5
Now that I've got it working, the next step is to get SSL running.
Hopefully it will be less painful than this was and my hair will grow
back.
Regards
Noel
@INR.Net
------------------------------------------
To subscribe, unsubscribe and list archive
please visit http://www.optigold.com/lists
------------------------------------------
Messages In This Thread:
Return to Digital Point Solutions' Home Page