Currently at work, my main project consist of the migration of all our ColdFusion (intranet) applications from CF9 to CF11. And that includes a migration from Windows 2003 to Windows 2012.
I’ll spare you the details of how I struggled to get Adobe CF11 up and running: let’s just say that the server I was assigned to was not a pristine, default Windows 2012 – and that turned out to be a major hurdle. But I managed to get CF up and running, with a little help from our server administrators. So now it’s a matter of testing all the apps in a new environment, all the while debugging the effects of the small and large differences between the old and new server configurations.
What I want to note here is, above all things, a few small actions on the server that make my life a lot easier. By the way, I’m assuming that you only have a single Apache Connector for all your CF applications. All paths given are relative to your ColdFusion root folder.
First of all, when installing ColdFusion hotfixes from Adobe, it is always a good idea to check whether or not the Apache Connector requires upgrading or reconfiguration. For a maximum of information on this subject, check out Charlie Arehart’s “CF911: Why/when you MUST update the web server connector for ColdFusion 10/11 and may have missed it”. Since I’m working on Windows, I have to remember to use “
config/wsconfig.exe” (but that means two CF service restarts) or “
cfusion/connectors/bin/Upgrade_all_connectors.bat” after stopping IIS and CF. It is above all essential to run either command as Administrator, or it won’t work!
Another good thing to know is that CF11 Hotfix 7 includes a modification of the connector to control whether or not IIS should replace error messages with its own (sometimes irrelevant) error pages. The IIS pages are the default, but they are easily replaced by changing the value of key “
iis_skip_custom_errors_enable” to “
true” in the file “
config\wsconfig\1\isapi_redirect.properties”. Easy and useful, especially when you’re testing in different browsers on multiple client platforms.
Now all that’s missing in this context, is a tool to pick up the hotfix files from Adobe and store them in a simple HTTP update site where our intranet servers (without Internet connection, of course) can pick them up. I know – or at least, I assume – that I’m not the first one to deal with this situation, but I haven’t (yet) found such a script or application…