Accessibility

ColdFusion Release Notes

ColdFusion MX 6.1 Updater

Release Notes Part 1 - Known Issues, Changes, and Installation Instructions

April 21, 2005

This document contains information about the ColdFusion MX 6.1 Updater. The Updater works with all editions and installation configurations of ColdFusion MX 6.1, including the server configuration and the J2EE configuration. You cannot use this Updater with any ColdFusion releases prior to ColdFusion MX 6.1.

This release of the ColdFusion MX Updater does not support versions of ColdFusion MX for IBM WebSphere purchased from the IBM Passport licensing program. If you have purchased ColdFusion MX through Passport, you must obtain a copy of the Updater directly from IBM.

Note: To determine whether the Updater is installed, check the Version number listed on the ColdFusion MX Administrator Login page or on the Version line of the Administrator System Information page. The Version number of ColdFusion MX 6.1 with the Updater is 6,1,0,83762.

Because of their length, these Release Notes are divided into three parts.

Contents of Part 1

Other Parts of the Release Notes

Part 2 -- ColdFusion MX 6.1 Issues Fixed in this Release

Part 3 -- Installing ColdFusion MX with the Update and Uninstalling the Update

Note: In these Release Notes, cf_root refers to the directory where ColdFusion is installed or deployed. By default, you install ColdFusion MX server configuration in C:\CFusionMX in Windows and /opt/coldfusionmx on UNIX. You deploy ColdFusion MX J2EE configuration in a directory that depends on the application server.

What's New in this Release

The ColdFusion MX 6.1 Updater includes over 65 ColdFusion MX bug fixes including many database-related bug fixes and enhanced support for images in mail. It also includes several fixes to COM support, and numerous other fixes. The Updater rolls together all ColdFusion MX 6.1 hot fixes and security patches that have been released to date, eliminating the need to install multiple hot fixes and patches. It includes many fixes that are not available elsewhere. The updater also includes JRun Updater 3 (for ColdFusion server configurations only), and new releases of DataDirect JDBC drivers (version 3.3 build 31) and JIntegra COM support (version 1.6.1).

Known Issues with this Release

The following issues that were known to exist with this Updater at the time of the release. These issues are additional to any listed elsewhere. For confirmed issues that are discovered after the release date, and for known issues in ColdFusion MX, see ColdFusion MX TechNote ColdFusion MX 6.1 Confirmed Issues.

Issue ID

On Windows 2003 systems with Service Pack 1 (SP1), the installer immediately exits in the "preparing to install" dialog before extracting files.  This worked previously on Windows 2003 without SP1.

A feature of Windows 2003 Service Pack 1 is "Data Execution Prevention".   This security feature blocks the InstallAnywhere self-extractor for CF 6.1 and all JRun4 Updaters.  (CF 7.0 is not affected).  To fix this problem, do the following:

  1. Click Start, right click My Computer, and select Properties.
  2. On the Advanced tab, click the [Settings] button under the Performance section.
  3. Select the Data Execution Prevention Tab in the Performance Options dialog.
  4. Select the radio button for "Turn on DEP ... except those I select:"
  5. Select "Add" and select the Coldfusion or JRun installer.  (the entry shows up as "InstallAnywhere Self-Extractor" in the dialog)
  6. Select "Apply" on the "performance options" and "OK" on the "System Properties" page
  7. Now run the installer
Here is Microsoft's description of this feature.
60086
You must use the following command to install the pure Java version of the update:
java -classpath cfmx-61-updater-other.jar install -i console
56647
If you are using IBM WebSphere 5.1 as your J2EE server, you must configure the XML parser as described in the TechNote ColdFusion MX 6.1: IBM WebSphere 5.1 support. 56498
This update includes the security patch for the problem identified in Macromedia Security bulletin MPSB03-07. However, the update does not include the version of the patch that is required for the J2EE configuration running on IBM WebSphere 4 and Fujitsu Interstage 5.1. If you run ColdFusion MX on these J2EE servers, use the link and instructions in the security bulletin to download and install the patch. You should install the patch after you update ColdFusion, but before you restart it. 56531

If you have two instances of the CFIDE directory, one in the web server's web root, and the other in the cf_root directory, the Administrator might generate cfimport errors. If you have such a configuration, rename the CFIDE directory that is located in the cf_root directory, or ensure that both CFIDE directories contain the same files by copying the files from web server's CFIDE directory to the cf_root/CFIDE directory after you complete the update.

Users who initially installed ColdFusionMX 6.1 using the ColdFusion internal web server and started using an external web server at a later time are most likely to encounter this issue.

56971
If you are connecting to a DB2 database with a very small application heap size setting, you can get a "Virtual storage or database resource is not available" error message when you try to run a query. If this error occurs, you can resolve problem by increasing the applheapsz database configuration parameter to allow a larger application heap. 53547

If a ColdFusion request is sent to ColdFusion MX 6.1 with the update before the ColdFusion application is fully loaded and running, ColdFusion does not respond to requests. This problem applies to ColdFusion MX server configuration and J2EE edition on JRun 4. Macromedia has created a Hot fix for this problem. See TechNote 19536 for details.

56681
ColdFusion MX 6.1 and ColdFusion MX 6.1 with the update continue to run client purge operations even if you clear the option to purge client data in the ColdFusion MX administrator. See TechNote 19279 for details, including a Hot fix.
Note: The technote specifies ColdFusion MX 6.1, but also applies to ColdFusion MX 6.1 update
54464
53910
54372
49691

Back to Contents

Functional Changes in this Release

The following functional changes have been made in this release of the Updater. These issues are additional to any listed elsewhere. For more information on known issues in ColdFusion MX, see ColdFusion MX TechNote ColdFusion MX 6.1 confirmed issues.

Changes
The behavior of the Oracle driver when fetching numeric columns, such as 7.4, has changed. The retrieved value is now formatted with zeros to include all the specified decimal places, such as 12.1200 instead of 12.12. This change is not a bug, but it is a behavior change from the previous release.
As a result of changes made to fix a bug in the cfexecute tag, CFML pages that specify command line arguments in the name attributes might have to specify them in the arguments attribute, as documented.
Two attributes have been added to the cfmailparam tag to support mail file attachments:
disposition="disposition-type"
content ID="content ID"
The disposition attribute specifies how the file content is to be handled. Its value can be inline or attachment.The contentID attribute specifies the mail content-ID header value and is used as an identifier for the attached file in an IMG or other tag in the mail body that references the file content. This ID should be globally unique.

Back to Contents

Updating a ColdFusion MX 6.1 Server Configuration in Windows

This section explains how to install the ColdFusion MX 6.1 update on a server configuration in a Windows platform. Read the Installation Notes before you install the update.

Note: If you are updating ColdFusion MX 6.1 on Windows XP with SP2 installed, read Technote 19518 for information on using ColdFusion MX with Windows Firewall enabled.

To install the ColdFusion MX update in Windows:

  1. Close any applications that are currently running on your computer.
  2. If you are running the server configuration, stop the following services:
    • ColdFusion MX Application Server
    • ColdFusion MX ODBC Agent
    • ColdFusion MX ODBC Server
    • On Windows Server 2003 systems only: Windows Management Instrumentation
    • If you use IIS as your web server for ColdFusion MX: World Wide Web Publishing Service.
    • If you use a web server other than IIS or the ColdFusion MX built-in web server:
      the web server.
  3. Run cfmx-61-updater-win.exe. The Install Wizard starts.
  4. Follow the instructions in the wizard. Select the Server Configuration option on the Configure Installer page. Respond as appropriate to all other options; for example, specify the location of the ColdFusion MX 6.1 installation that you are updating. Let the installer run to completion.

    Note: If you use IIS as your web server and do not shut it down in step 3, ColdFusion attempts to shut down each site individually and restart it after installing the update. If you have large numbers of sites, this might take a long time.

  5. After the Pre-Installation Summary page of the wizard, the Updater copies updated files to your computer and upgrades any configured web server connectors.
  6. After the installation is complete, ensure that any services you stopped in step 2 are running, and restart them if they are not running.

Back to Contents

Updating a ColdFusion MX 6.1 Server Configuration on UNIX

This section explains how to install a ColdFusion MX update on a Server Configuration on UNIX. Read the Installation Notes before you install the update.

Note: These instructions use the general term cfmx_updater_file to refer to the Updater file. The specific Updater 3 filename depends on the operating system, as follows:

Linux cfmx-61-updater-lin.bin
Solaris cfmx-61-updater-sol.bin
HPUX cfmx-61-updater-hpux.bin

To install the ColdFusion MX update on UNIX:

  1. Log in as root.
  2. Stop ColdFusion MX with the following command:

    /cf_root/bin/coldfusion stop

  3. Stop your web server.
  4. Using the cd command, go to the directory with the Cold Fusion MX Updater file.
  5. Ensure that the Updater file owner has full permissions and all others have read and execute permissions.
  6. Start the installation with the following command:

    ./cfmx_updater_file

    The installation program starts.

  7. Follow the instructions in the Install Wizard . Select the Server Configuration option on the Configure Installer page. Respond as appropriate to all other options; for example, specify the location of the ColdFusion MX 6.1 installation you are updating.
  8. After the Updater program finishes, ensure that your web server has restarted; if not, restart it manually.
  9. Start ColdFusion MX with the following command:

    /cf_root/bin/coldfusion start

Back to Contents

ColdFusion MX Server Configuration Installation Notes

In the following notes, cf_webroot refers to the directory that contains the ColdFusion MX CFIDE directory. This directory is typically the active web server's root document directory. For example, for the ColdFusion MX internal web server, this directory is cf_root\wwwroot. If ColdFusion MX uses another web server, such as Microsoft IIS or Apache, the directory might have a different path. You specify the location of this directory in one of the Updater installation program steps.

  • The Updater writes the following information files to the cf_root directory:
Macromedia_ColdFusion_MX _6.1_Updater_InstallLog.log Log file that provides installation details, including the files installed.
cfmx_updater_installer_debug.txt Detailed debugging information that can be useful for Macromedia Technical Support.
  • The Updater checks for the existence of the following files before installing the update. If any of these files is missing, the Updater reports an error and does not install the update.
In Windows cf_root\bin\cfstart.bat
cf_root\lib\cfusion.jar
cf_root\lib\bcel.jar
cf_webroot\CFIDE\administrator\Application.cfm
On UNIX cf_root/bin/coldfusion
cf_root/lib/cfusion.jar
cf_root/lib/bcel.jar
cf_webroot
/CFIDE/administrator/Application.cfm
  • The Updater puts copies of the original versions of all files that it updates in the cf_root/cumulative_hotfix_bkup directory tree. Each file's location in this directory tree reflects the original file's location relative to the cf_root directory.

    Caution: If you reinstall an update that has already created backup files, the installation overwrites the original backup files and you will lose the 6.1 release versions of the files. If you must reinstall the update, copy the backup files to a place outside the cumulative_hotfix_bkup directory before you reinstall.

  • Due to compiler changes in this Updater, ColdFusion application code must be recompiled to work properly. To ensure that this occurs, the Updater installer renames the existing cfclasses folder, located at cf_root\wwwroot\WEB-INF, to cfclasses_backup.

    You can use the cfcompile script installed in the cf_root\bin directory to recompile your ColdFusion applications. Recompiling your application helps to improve initial page request time, but is not necessary for the proper functioning of ColdFusion applications. Use the following commands to run this script:

    In Windows:

    cfcompile.bat cf_webroot [cf_app_file_dir]

    On UNIX:

    ./cfcompile.sh -cfuser username -webroot cf_webroot
                        [-dir cf_app_file_dir]

    The variable cf_webroot specifies your web root directory, such as C:\inetpub\wwwroot.

    The variable cf_app_file_dir is the directory that contains the CFML files to be compiled. It must be underneath the web root directory. If you omit the -dir attribute, the script recompiles all ColdFusion pages in the web root directory and all its subdirectories.

    In the UNIX command, username specifies the ColdFusion runtime user, and must correspond to the user under which ColdFusion MX runs (typically, nobody). You specify the user in the Install Wizard.

    After successfully recompiling and testing your applications, you can remove the cfclasses_backup folder created by this installation.

  • The Updater automatically upgrades all configured web connectors. In some cases, you might have to upgrade all configured connectors independently of the Updater; for example, following installation of a security patch. To upgrade the connectors in Windows, run cf_root\bin\connectors\Upgrade_all_connectors.bat. On UNIX or Linux run cf_root/bin/connectors/upgrade_all_connectors.sh. The script takes no arguments

Back to Contents

Updating a ColdFusion MX 6.1 J2EE configuration on JRun 4 in Windows

This section explains how to install the ColdFusion MX 6.1 update on a J2EE configuration that uses JRun 4 as the J2EE server in a Windows platform. Read the Installation Notes before you install the update.

Use this procedure in Windows if you selected either of the following options in the ColdFusion MX 6.1 installer:

  • J2EE Configuration (ColdFusion MX with JRun 4)

    (This option installs ColdFusion MX 6.1 and a full copy of JRun 4. )

  • J2EE configuration (EAR/WAR file)

    (This option lets you install ColdFusion MX 6.1 on an existing JRun 4 server.)

Notes:

  • Updating ColdFusion MX 6.1 on JRun 4 does not update the JRun 4 server. If you have not done so, Macromedia recommends that you run the latest JRun 4 Updater before updating ColdFusion MX 6.1. For more information on updating JRun 4, see the Macromedia JRun Hot Fix Main Page.
  • If you are updating ColdFusion MX 6.1 on Windows XP with SP2 installed, read Technote 19518 for information on using ColdFusion MX with Windows Firewall enabled.

Use the following steps for each instance of the ColdFusion MX J2EE application that you have deployed on JRun. If you installed Coldfusion MX using the J2EE Configuration (ColdFusion MX with JRun 4) option and have not installed any additional ColdFusion instances using the EAR/WAR file, do this procedure once.

To install the ColdFusion MX update in Windows:

  1. Close any applications that are currently running on your computer.
  2. If you run any of the following as a Windows service, stop them:
    • The the instance of JRun that runs the ColdFusion MX 6.1 application that you are updating.If you selected the J2EE Configuration (ColdFusion MX with JRun 4) option when you installed ColdFusion MX 6.1, and have not deployed ColdFusion MX on additional instances of the JRun server, this is the Macromedia JRun cfusion server.
    • ColdFusion MX ODBC Agent.
    • ColdFusion MX ODBC Server.
    • On Windows Server 2003 systems only: Windows Management Instrumentation
    If the JRun server on which ColdFusion MX 6.1 is deployed does not run as a Windows service, use the JRun Launcher or JRun Management Console to stop the JRun server on which ColdFusion MX runs.
  3. Run cfmx-61-updater-win.exe. The Install Wizard starts.
  4. Follow the instructions in the wizard.
    1. On the Configure Installer page, select the J2EE Configuration (ColdFusion MX with JRun 4) option.
    2. On the Configure ColdFusion MX page, specify the location of the WEB-INF directory of the ColdFusion MX 6.1 instance you are updating. The wizard default value is the default location if you selected the J2EE Configuration (ColdFusion MX with JRun 4) option when you installed Coldfusion MX 6.1.
    3. Let the installer run to completion.
  5. After the Pre-Installation Summary page of the wizard, the Updater copies updated files to your computer.
  6. When you have updated all JRun 4 servers on which you deployed ColdFusion MX 6.1, you can delete from the jrun_root/servers/lib directory all ColdFusion MX hot fixes that were posted on the ColdFusion Hot Fixes page through August 1, 2004. These hot fixes are in files with names of the form hf*.jar.
  7. After the installation is complete, restart the services or JRun servers that you stopped in step 2.

Back to Contents

Updating a ColdFusion MX 6.1 J2EE configuration on JRun 4 on UNIX

This section explains how to install a ColdFusion MX 6.1 update on JRun 4 running on UNIX. Read the Installation Notes before you install the update.

Use this procedure on UNIX if you selected either of the following options in the ColdFusion MX 6.1 installer:

  • J2EE Configuration (ColdFusion MX with JRun 4)

    This option installs ColdFusion MX 6.1 and a full copy of JRun 4.

  • J2EE configuration (EAR/WAR file)

    This option lets you install ColdFusion MX 6.1 on an existing JRun 4 server.

Notes:

Updating ColdFusion MX 6.1 on JRun 4 does not update the JRun server. If you have not done so, Macromedia recommends that you run the latest JRun 4 Updater before updating ColdFusion MX 6.1. For more information on updating JRun 4, see the Macromedia JRun Hot Fix Main Page.

These instructions use the general term cfmx_updater_file to refer to the Updater file. The specific Updater 3 filename depends on the operating system, as follows:

Linux cfmx-61-updater-lin.bin
Solaris cfmx-61-updater-sol.bin
HPUX cfmx-61-updater-hpux.bin

To install the ColdFusion MX update on UNIX:

  1. Log in as root.
  2. Use the JRun Management Console or the JRun Launcher to stop the instance of JRun that runs the ColdFusion MX 6.1 application that you are updating.
  3. Using the cd command, go to the directory with the Cold Fusion MX Updater file.
  4. Ensure that the Updater file owner has full permissions and all others have read and execute permissions.
  5. Start the installation with the following command:

    ./cfmx_updater_file

    The installation program starts.

  6. Follow the instructions in the wizard.
    1. On the Configure Installer page, select the J2EE Configuration (ColdFusion MX with JRun 4) option.
    2. On the Configure ColdFusion MX page, specify the location of the WEB-INF directory of the ColdFusion MX 6.1 instance that you are updating. The wizard default value is the default location used by the Coldfusion MX 6.1 installer J2EE Configuration (ColdFusion MX with JRun 4) option.
    3. Let the installer run to completion.
  7. After the Pre-Installation Summary page of the wizard, the Updater copies updated files to your computer.
  8. When you have updated all JRun 4 servers on which you deployed ColdFusion MX 6.1, you can delete from the jrun_root/servers/lib directory all ColdFusion MX hot fixes that were posted on the ColdFusion Hot Fixes page through August 1, 2004. These hot fixes are in files with names of the form hf*.jar.
  9. Use the JRun Management Console or JRun Launcher to start the JRun server that has the ColdFusion MX 6.1 instance that you updated

Back to Contents

ColdFusion MX on JRun Installation Notes

These notes use the following path names:

cf_root refers to the directory that contains your ColdFusion MX 6.1 WEB-INF directory. This directory is typically jrun_root\servers\server_name\cfusion-ear\cfusion-war, where server_name is normally cfusion if you installed ColdFusion MX 6.1 using the J2EE Configuration (ColdFusion MX with JRun 4) option.

cf_webroot refers to the directory that contains the ColdFusion MX CFIDE directory. This directory is typically the active web server's root document directory. For example, for the default J2EE Configuration (ColdFusion MX with JRun 4) using the ColdFusion MX internal web server, this directory is the same as cf_root, jrun_root\servers\server_name\cfusion-ear\cfusion-war. If ColdFusion MX uses another web server, such as Microsoft IIS or Apache, the directory has a different path. You specify the location of this directory in one of the Updater Install Wizard steps.

  • The Updater writes the following information files:
    Macromedia_ColdFusion_MX _6.1_Updater_InstallLog.log Log file that provides installation details, including the files installed. Saved in the cf_root directory.
    cfmx_updater_installer_debug.txt Detailed debugging information that can be useful for Macromedia Technical Support. Saved in the cf_root\WEB-INF\cfusion.
  • The Updater checks for the existence of the following files before installing the update. If any of these files is missing, the Updater reports an error and does not install the update.
    In Windows cf_root\WEB-INF\cfusion\lib\bcel.jar
    cf_root\WEB-INF\cfusion\lib\cfusion.jar
    cf_webroot\CFIDE\administrator\Application.cfm
    On UNIX cf_root/WEB-INF/cfusion/lib/bcel.jar
    cf_root/WEB-INF/cfusion/lib/cfusion.jar
    cf_webroot/CFIDE/administrator/Application.cfm
  • The Updater puts copies of the original versions of all files that it updates in the cf_root\WEB-INF\cfusion\cumulative_hotfix_bkup directory tree. Each file's location in this directory tree reflects the original file's location relative to the cf_root\WEB-INF\cfusion directory, with the exception of the wwwroot subdirectory, which contains files in their location relative to the cf_webroot directory.

    Caution: If you reinstall an update that has already created backup files, the installation overwrites the original backup files and you will lose the ColdFusion MX 6.1 release versions of the files. If you must reinstall the update, copy the backup files to a place outside the cumulative_hotfix_bkup directory before you reinstall.

  • Due to compiler changes in this Updater, ColdFusion application code must be recompiled to work properly. To ensure this occurs, the Updater installer renames the existing cfclasses folder, located at cf_root\WEB-INF, to cfclasses_backup.

    You can use the cfcompile script installed in the cf_root\WEB-INF\cfusion\bin directory to recompile your ColdFusion applications. Recompiling your application helps to improve initial page request time, but is not necessary for the proper functioning of ColdFusion applications. Use the following commands to run this script:

    In Windows:

    cfcompile.bat cf_webroot [cf_app_file_dir]

    On UNIX:\

    ./cfcompile.sh -cfuser username -webroot cf_webroot
                   [-dir cf_app_file_dir]

The variable cf_webroot specifies your web root directory, such as C:\inetpub\wwwroot.

The variable cf_app_file_dir is the directory that contains the CFML files to be compiled. It must be underneath the web root directory. If you omit the -dir attribute, the script recompiles all ColdFusion pages in the web root directory and all its subdirectories.

In the UNIX command, username specifies the ColdFusion runtime user, and must correspond to the user under which ColdFusion MX runs (typically, nobody). (You specify the user in the Install Wizard.)

After successfully recompiling and testing your applications, you can remove the cfclasses_backup folder created by this installation

Back to Contents

Updating a non-JRun ColdFusion MX 6.1 J2EE configuration

This section explains how to install the ColdFusion MX 6.1 Updater on a system that is running the ColdFusion MX J2EE configuration on any J2EE server except JRun 4. It applies to all operating systems and all ColdFusion MX J2EE configurations except on JRun 4.

The Updater directly updates an existing ColdFusion MX 6.1 EAR or WAR file. It does not update expanded deployment directories. After performing the ColdFusion MX 6.1 update installation procedure, you must redeploy ColdFusion MX using the updated EAR or WAR file and your application-server-specific deployment procedure.

The Updater filename depends on the operating system, as follows:

Windows cfmx-61-updater-windows.exe
Linux cfmx-61-updater-linux.bin
Solaris cfmx-61-updater-solaris.bin
HPUX cfmx-61-updater-hpux.bin
Other platforms cfmx-61-updater-other.jar

Note: These instructions refer to the ColdFusion MX J2EE deployment instructions for your application server, which are available online at http://www.macromedia.com/go/cfmxj2ee-cert. The "Supported J2EE application servers" section includes links to the appropriate installation instructions for supported J2EE servers. The "Unsupported application servers for the archive install" section includes links to installation instructions for additional servers.

To install the update on ColdFusion MX J2EE configurations, you must do the following tasks:

  1. Save your ColdFusion MX application and configuration files.
  2. Undeploy your ColdFusion MX application from your J2EE server.
  3. If you do not have a ColdFusion MX 6.1 EAR or WAR file available:

    Run the ColdFusion MX 6.1 Installer to generate an EAR or WAR file.

  4. Run the Updater to update the ColdFusion MX 6.1 EAR or WAR file.
  5. Redeploy the updated ColdFusion MX EAR or WAR file on your J2EE server.
  6. Restore your ColdFusion MX configuration using the files you saved in task 1.

The following sections provide detailed descriptions of each of these tasks.

Task 1: Saving your ColdFusion MX application and configuration files

To save your ColdFusion MX information, make copies of the following files in a safe place. The location must not be under cf_root directory, because you will undeploy your ColdFusion MX application.

  • If your web root is under the cf_root directory, back up the files or directories that you have put in your web root. Do not back up the cfdocs, CFIDE, META-INF, or WEB-INF directory.
  • If you added custom tags, CFX files, CFC files, applets, or any other custom files in directories under the cf_root directory, save copies of these files. Review the ColdFusion MX Administrator Mappings, Java Applets, CFX Tags, and Custom Tag Paths pages to check for files that need to be backed up. For example, the directories such as the following might contain files that require backing up:

    cfusion\cfusion.ear\cfusion.war\WEB-INF\jsp
    cfusion\cfusion.ear\cfusion.war\WEB-INF\cfusion\cfx
    cfusion\cfusion.ear\cfusion.war\WEB-INF\cfusion\CustomTags

  • Back up the following ColdFusion MX 6.1 configuration files in the cf_root\WEB-INF\cfusion\lib\ directory:

    neo-query.xml
    neo-registry.xml
    neo-runtime.xml
    neo-security.xml
    neo-verity.xml
    neo-xmlrpc.xml
    neo-archivedeploy.xml
    neo-clientstore.xml
    neo-comobjmap.xml
    neo-cron.xml
    neo-debug.xml
    neo-graphing.xml
    neo-logging.xml
    neo-mail.xml
    neo-metric.xml
    neo-probe.xml

Task 2: Undeploying your ColdFusion MX application

Undeploy your ColdFusion MX application using your J2EE server's application or server undeployment procedure.

Note: If your deployment includes ColdFusion MX as an archived EAR or WAR file (typically, cfusion.ear or cfusion.war), save the file. You will use it with the Updater to create an updated EAR or WAR file.

  1. If you are running Windows and installed support for ODBC data sources, stop the following services:

    ColdFusion MX ODBC Agent
    ColdFusion MX ODBC Server

  2. As appropriate for your application server, either stop the ColdFusion application and RDS application (if it is running), or stop the application server.
  3. Undeploy your ColdFusion MX J2EE enterprise application, or the ColdFusion MX web application and the RDS application (if it is installed) from your application server, using the standard undeployment procedure for your J2EE server. For server-specific ColdFusion MX 6.1 deployment instructions, see the links at the lower part of the page at http://www.macromedia.com/go/cfmxj2ee-cert.

Task 3: Generating a ColdFusion MX 6.1 EAR or WAR file

If you do not have a cfusion.ear or cfusion.war file from your initial ColdFusion MX 6.1 installation, you must use the ColdFusion MX 6.1 installer to create one. Use the following steps to create a ColdFusion MX 6.1 cfusion.ear or cfusion.war file.

  1. Locate your ColdFusion MX 6.1 CD or installation file and start the ColdFusion MX installer.
  2. Follow the instructions in the Install Wizard .
  3. On the Install Configuration page, select the J2EE configuration (EAR/WAR file) option and select either EAR file or WAR file, depending on the requirements of your J2EE server.
  4. If you are generating an EAR file, the wizard displays a Choose Context Root page. On this page, specify the context root that you used for your initial ColdFusion MX installation.
  5. On the Installation Confirmation page, click the Install button. The installer creates an EAR file or WAR files in the directory that you specified in the wizard.

Task 4: Updating the ColdFusion MX 6.1 EAR or WAR file

Use the following steps to update your cfusion.ear file or cfusion.war file. You do not have to update the rds.war file.

For Windows, Linux, Solaris, and HPUX

  1. Start the ColdFusion MX 6.1 Updater and follow the instructions in the wizard.
  2. On the Configure Installation page, select the J2EE configuration (EAR/WAR file) option.
  3. On the summary page, click the Install button. The installer saves a copy of the original EAR or WAR file with an _original suffix added to the filename. It then updates the EAR or WAR file. It writes a Macromedia_ColdFusion_MX_6.1_Updater_InstallLog.log with information about the update including any error messages.

For AIX and all other platforms that require a Java-only ColdFusion installation

  1. Enter the following line in a console window to start the ColdFusion MX 6.1 updater. The Java-only updater works in consol mode:

    java -classpath cfmx-61-updater-other.jar install -i console

  2. Follow the instructions in the console and specify the file to be updated.
  3. When you press the Enter key in response to the Pre-Installation Summary, the installer saves a copy of the original EAR or WAR file with an _original suffix added to the filename and updates the EAR or WAR file. It writes a Macromedia_ColdFusion_MX_6.1_Updater_InstallLog.log with information about the update including any error messages.

    Press the Enter key to exit the installer.

Task 5: Redeploying an updated ColdFusion MX 6.1 application

Follow the normal deployment procedure for your J2EE server. Server-specific instructions for deploying ColdFusion MX 6.1 are available online at http://www.macromedia.com/go/cfmxj2ee-cert.

Note: The server-specific instructions assume that you are deploying ColdFusion for the first time. Undeploying the ColdFusion application does not remove JVM settings, so you do not have to do the JVM configuration steps described in these instructions.

Task 6: Restoring your configuration

Use the following procedure to restore your ColdFusion MX configuration after you deploy the updated EAR or WAR file.

  1. Ensure that your ColdFusion MX web application is not running. Depending on your J2EE server, stop either the J2EE server or the ColdFusion web application.
  2. Copy the files you saved in task 1 back to their original locations.
  3. Restart your J2EE server or ColdFusion application.

Back to Contents

Part 2 -- Issues Fixed in this Updater Release

Part 3 -- Installing ColdFusion MX with the Update and Uninstalling the Update

Top Support Topics

 

More ColdFusion Topics

Choose a category to see more topics.

Request Support

 

Additional ColdFusion Resources

 

ColdFusion Downloads

 

Outside Resources

 

Feedback

 

Community