Product Review
Setting Up Your Development Server with ColdFusion 5, MX, and BlueDragon
The world of ColdFusion application servers is quite interesting at the moment. Macromedia's recent update to CFMX 6.1 promises to add a lot of stability and speed to the product. BlueDragon, New Atlanta's alternate CFML runtime engine continues to gain momentum. Yet despite these two great products, much of the development out there is still based on ColdFusion 5 (or earlier).
Reader Feedback: Page 1 of 1
#3 |
Charlie Arehart commented on 9 Jan 2004
This is Charlie here, Jon. When you refer to 6.1, do you mean CFMX 6.1? Or BlueDragon 6.1? I'll assume from your subject line that you mean CFMX.
I'm afraid I can't think of what your install of CFMX 6.1 did to clobber port 80 on IIS. Just to clarify further, you're not referring to changes you did as a result of this article, right?
First I'd confirm that IIS is running at all. Then, does it serve HTML files from port 80 and out of the default inetpubwwwroot? Is your problem with attempts to browse files there or via a virtual directory pointing to another physical location for the code?
There are just lots of things that could be impacting you, and they may be due to IIS config, or something CFMX 6.1 did. Maybe someone else will have other thoughts.
|
#2 |
Jon commented on 1 Jan 2004
I have XP professional with CF5 and CFMX installed. After I updated to 6.1, my port 80 IIS stopped working, the port 8500 works fine. XP professional only has one web server and no matter what I have done to date, port 80 does not work. Any ideas what 6.1 did to port 80?
|
#1 |
free beachler commented on 1 Dec 2003
As soon as I read the first few paragraphs I realized this was exactly what I wanted to do on our dev server. Immediately implementing the steps illustrated in the article I soon found problems.
We were running CFMX 6.0.1 - but I'm not sure the full version number or patch level (I'm not too sure on determining CFMX 6.0 patch level). When using the "Web Server Configuration" JAR file I found it didn't work as expected - and when I added a "web server configuration" the .cfm and .cfml App Mappings in IIS were unchanged - and the .jsp, .jws, .cfc mappings were not created at all.
As a workaround I ended up just upgrading our CFMX installation to 6.1. Then performing the steps in the article was cake - now it's all setup! Thanks again for the great article.
|