In this post I will walk you through the steps to upgrade your ColdFusion 9 servers to Update 1 when you're running Distributed IIS Web Servers. If you missed my last post, you can read it here (http://bit.ly/hbwmvv) to learn about the high availability environment we have, and the redundancy you can obtain when using distributed IIS web servers. As with any upgrade or update, it is important to assemble all of the files you may need and read through the documentation available. Make sure you confidently understand the steps you'll be going through. Also, if needed, schedule your downtime window and notify your support departments and/or customers. Okay, let's get started!
Step 1: Backup! This is critical and I recommend doing this whenever applying a hotfix or update. I make 2 different backups. The first is of all ColdFusion settings from the Administrator using a CAR file. This should be old hat to most CF admins out there, but at a high level you do this: Login to your CF Admin, choose Packaging & Deployment from the left menus, select ColdFusion Archives and follow the on-screen instructions.
The second is to backup the entire set of files in the JRUN directory, if your disk space allows. Both of these backups will allow you to recover from most any install crash or corruption of files.
Step 2: Download the update installer from Adobe.com (http://www.adobe.com/support/coldfusion/) and copy to your server. Also be sure to download the install doc as well, as the first set of instructions from Adobe are complete and accurate.
Step 3: Following the instructions in the install doc from Adobe, start by shutting down all of the services listed. A note about ColdFusion version 9: the Windows Services were re-named to start with Adobe instead of Macromedia for multi-server installations. Funny that the default admin instances are still named starting with Macromedia.
Step 4: Double-click the installer to start the install wizard and follow the on-screen instructions, providing the correct responses for your environment.
Step 5: Once the installer has completed, check the log file that was created in the JRUN directory for any errors or warnings.
Step 6: Restart all services that were stopped before starting the install wizard and confirm that you can access your CF Administrator and that it now reflects 9.01 for the version. Since you are probably working within a scheduled downtime window, now would be a good time to apply any CF hotfixes, Windows Updates, and perhaps reboot the entire machine for good measure.
Step 7: Upgrade the JRUN IIS Connectors. Now this is where the Adobe docs are lacking and the main point of this post.
First, locate and copy the wsconfig.jar file from your recently upgraded ColdFusion server to your distributed IIS web server(s). This file will need to be copied to all web servers.
After copying over the file you will need to locate your current wsconfig.jar file and replace it with the new one. It's a good idea to make a complete backup copy of your connectors, just in case.
Now, you can upgrade all connectors by running the following command. Be sure the paths to your java.exe and wsconfig.jar files are accurate.
c:\jre6\bin\java -jar c:\tempcf9\wsconfig.jar -u
Here's a tip: Run this command to dump all of the available wsconfig commands to a text file for future reference:
c:\jre6\bin\java -jar c:\tempcf9\wsconfig.jar -h >c:\wsconfig-commands.txt
Step 8: Test! With any update, testing your sites and code is smart. Overall, this whole process took only about 15 minutes to complete, but we used the remaining 45 mins of our maintenance window to run as many tests as we could. You never know what code you have that might not run on the new server version.
I would like to thank the folks working the @Adobe_Care Twitter account for getting me in touch with Swathi C. who works on Adobe's third tier engineering team. She answered all of my questions about this process and gave me some excellent tips that I use often. Feel free to follow-up with me on Twitter if you have further questions. No guarantees that I'll have answers, but I'm happy to try. On Twitter: @philspitze
- Phil Spitze, Network Manager