Installing ColdFusion on IIS 7 (Vista)
So since I got my new Dell at home I've been using my old Dell as a 'pseudo-server' and connecting to it over my home network for local development. This has been working out fine - but there has always been something that bugged me about using the built in web server that ships with ColdFusion as a development server. Every time you wanted to create a new 'site' you pretty much have to code around the fact that you're really under one wwwroot. For example lets say you have the following directory structure:
- wwwroot
- site1
- components
- myComponent.cfc
- components
- site2
- components
- myComponent.cfc
- components
- site1
In the example above I might have the following code under site1:
Pretty standard stuff really - just creating an instance of the myComponent.cfc under site1. Well the pain of the matter happens when you decide to move site1 up to a production environment. In most cases you'll want the contents under site1 to be the actual root of your site. Otherwise your URL might look something like http://mysite.com/site1 - which may be what you intended - but usually isn't. So now you've also got the pain of coding around a poorly planned site that could potentially have many references to the single root development environment.
So the standard fix to creating a workable development environment is to run ColdFusion in the multi-server configuration (which is available as an option when installing CF).
I've chosen to focus a few posts on setting up ColdFusion on IIS for a few reasons. First of all I like GUI's. I'm not afraid to admit it. I've tried to mess with Apache and it seemed like a pain in the rear for a GUI geek like me. No, I know it's really not that hard - but hell - it's my Vista and I'll GUI if I want to (sorry Brian you couldn't talk me out of it ;) Actually to be fair I did attempt to install Apache but ran into issues getting the latest release to install on Vista (insert Vista sucks comments below). I also liked the fact that IIS 7 appears to be able to handle multiple sites in a development environment. To top it all off it's free - at least it is on Vista Premium which is what I'm running.
So I'm going to post at least a few more posts on how to get ColdFusion running on IIS7 (on Vista). There not going to be anything groundbreaking for some folks who know this stuff like the back of their hands but for beginners I think it should be an enlightening journey.
Step One is simple. So simple in fact I'm not even going to post the instructions since it's already been done for me. So if you're playing along at home your first step will be to hit that tutorial and get IIS running. The next step is to do a simple ColdFusion install and follow the prompts for a multi-server config. CF should recognize IIS running on your machine and you'll want to tell the install wizard to make CF available for all sites under IIS. Everything else is a pretty standard CF install.
Update: Please read this comment...



http://www.jasonholden.com/downloads
It will set the webroot to the directory from which it is run.
To install Apache on Vista what you have to do is turn off something called "User Account Control" in the User Account control panel and then do the install.
Once you're done installing switch it back on otherwise vista will bug the hell out of you until you do switch it back on.
Oh and you have to take the apachemonitor out of startup because it blows up on vista.
Of course when I did this I didn't actually know about right clicking on an exe and choosing "Run as Admin", so it may be that you can just do that with the Apache Installer.
http://www.communitymx.com/content/article.cfm?cid...
I created a Virtual Directory in my webroot, but that doesn't seem to do anything. It always says that movie couldn't be loaded.
I'd really appreciate some input on this...
Thanks guys!
Now getting them to load data is another question. Adding a JRunScripts virtual directory (and enabling CGI) keeps the data call from 404ing, but its still an empty response...
I really wonder why this problem is so hard to find some info on if you google around...
I don't suspect anybody else has figured it out and could share? :)
First, you need to create a virtual directory called JRunScripts and point it at CF_ROOT\runtime\lib\wsconfig\1
Next, go to the handler mappings at the IIS root, right click "ISAPI-dll", click handler permissions, and check "execute."
Finally, open Notepad *as an administrator*. Open c:\windows\system32\inetsrv\config\applicationhost.config. Search for "*.dll" and you should find the ISAPI handler mapping node under the <handlers> section. Add allowPathInfo="true" as an attribute on that node and save it (IIS will automatically reload it, you dont need to restart it). Voila, flash forms should load data.
I've followed your instructions and now the flash form loads, but is stuck in an endless loop it seems and I get the little loading icon, but nothing comes up.
If I pull up a flash form with lots of data in it, it just crashes the IE.
Any other ideas? Or perhaps a little more detailed descriptions? I may be stupid ;)
Thanks for al lyour help so far though!
It has to be some kind of config error in IIS, but I can't figure out what's wrong.
Anybody have a quick rundown of what settings I have to have set, what handlers need to be there?
Any help is very much appreciated
If its getting a 404 on that then your JRunScripts virtual directory isn't set up correctly; if its getting a blank response then the pathInfo setting I mentioned above isn't set correctly.
Also, are you using the jrun_IIS6_*.dll or the jrun.dll to connect? Mine is using the (older) jrun.dll connector.
I have CF7.02 working on Vista - well its partly working on Vista with IIS 7.
The problem I found when I try to browse the server - I get an error IO server communication error. I cant browse to find an access database, and I cant browse to set up a mapping.
This is really bugging me as I havent been able to find away to get around this error.
If I then open Dreamweaver, in the application panel I cant view database via the RDS server.
{Thanks Heidi Bautista} // the MS SQL 2005 MS SQL / ODBC Driver workaround { Thanks to Charlie Arehart } // and the now the Host header workaround {Thank You Todd} Any clues to get the aforementioned errors resolved?
I'd give that a shot.