This document describes how to upgrade from Adobe ColdFusion MX 7 Enterprise (multi-server config) to Adobe ColdFusion 8 Enterprise (multi-server config).

The following were not enabled for the following documented procedures:

• RDS
• Verity Collections

System

• Microsoft Windows Server R2, Enterprise
  
• Edition SP1 with CFMX 7.02 / JRun4 Updater 7

Procedures (pre-installation and installation)

1. In ColdFusion MX 7 Administrator > Packaging & Deployment > ColdFusion Archives (.car) section, create a CAR archive of your current settings for each distinct server instance you wish to migrate over to ColdFusion 8 (see http://livedocs.adobe.com/coldfusion/7/htmldocs/00001760.htm for more info). Give the file a meaningful name such as cfmx7settings. In the Archive Wizard window that appears, click Select All and then go into the Server Settings section and ensure that the Java and JVM option is deselected. You do not want these settings as part of the CF 8 settings (CF 8 uses a more recent version of Javas VM, please see post installation notes for further information). You may wish to print off or copy the Archive Summary information to have your settings documented in case of any problems.
2. While still in ColdFusion MX 7 Administrator, navigate to the Server Settings > Settings Summary section and print off or copy ALL of your CF Server Java Class Path and CFX Class Path entries. You may need to consider updating to more recent versions of your CFX tags or possibly replace them entirely with a CFC version.
3. Open Windows Services and stop ALL CFMX and JRun4 services as well as IIS Admin. Right-click and select Properties for each of the CFMX and JRun services and set them to either Disabled or Manual on startup.
4. Create a full backup of your existing {JRun4_root }\ directory structure and call it JRun4_cf7. This will be your only path to a quick recovery if any issues arise during the migration.
5. Uninstall ColdFusion MX 7 completely through the Windows Add/Remove Programs console. Ensure that you reboot your server.
6. Delete your existing {JRun4_root} folder (You may need to reboot to complete this process).
7. Perform a complete installation of CF 8.0.1 from disk or from the download at http://www.adobe.com/products/coldfusion.
8. During installation, install to the same folder name you had previously with CFMX 7 (i.e. C:\JRun4 or /opt/jrun4).
9. Login to your CF Administrator, create/deploy all your ColdFusion instances and deploy your CAR file(s) appropriately.
10. Perform full load and regression testing.

Important Notes (post-installation)

1. If any of your ColdFusion applications are using frameworks that are loading a large number of classes and you are experiencing very slow load times, you may wish to configure ColdFusion to use an older or newer JVM version than 1.6. There is a known bug with Sun in regards to applications that load many classes at startup with this JVM release.
2. If you encounter any issues with your application, refer to your documentation, specifically your ClassPath entries from CFMX 7.
   
3. If you are running MySQL 5+, and previously were using an ODBC connector for your datasource, switch over to the new MySQL 4/5 drivers.
4. If you are running Ray Camden's Blog CFC, ensure you have the latest code as there were reported issues with CFMX 8.0.1.
   
5. If you encounter any issues relating to Verity Collections, check your Port numbers as CFMX 8.0.1 uses different ports in the event you install CFMX 8.0.1 and CFMX 7 in parallel.
6. Any Custom IIS folders you set up previously will not be upgraded by the installer. Ensure you go into any of these folders and ensure the .DLL files are pointing to CFMX 8.0.1 and not CFMX 7.
   
7. Check your instances to ensure everything is in place.
8. Ensure that you have gone through all settings from your CF 8 Administrator to ensure that any new settings added with this version of CF are implemented appropriately.
   

Additional Information

Migration Resources

Creating and Deploying Archive (CAR) Files: http://livedocs.adobe.com/coldfusion/8/htmldocs/help.html?content=deploying_3.html

Products affected