Accessibility
 
Home / Products / ColdFusion / Support / Release Notes
Macromedia ColdFusion Support Center Release Notes

ColdFusion MX Updater Release 3
Release Notes Part 4 -
Installed Files, Uninstalling, and Installing the Update Silently

March 19, 2003

This document is the fourth part of the ColdFusion MX Updater Release 3 Release Notes. It contains additional information on the Updater.


Contents of Part 4
Files Installed by the Updater
Uninstalling the Update
Installing Silently on ColdFusion MX Server

Other Parts of the Release Notes
Part 1 -- Known Issues and Installation Instructions
Part 2 -- Issues Fixed in this Updater Release
Part 3 -- Issues Fixed in Previous Updater Releases

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



Files Installed by the Updater

Updater Release 3 installs the files listed in this section when it updates ColdFusion MX Server.

The Updater for ColdFusion MX for J2EE replaces all installed files. However, only files that correspond to those in this list differ from the original versions. Also, several of the listed files are required for the application server and web server that are included in ColdFusion MX Server; these files are not included in ColdFusion MX for J2EE.

For brevity, this list uses xx to indicate a language-identifier suffix. ColdFusion MX is available in German, English, French, Japanese, and Korean, indicated by the suffixes de, en, fr, jp, and ko, respectively. Therefore, each entry ending in _xx.xml corresponds to five language-specific files, all of which are installed.

All platforms

Replaced Files
cf_root/lib/cfusion.jar
cf_root/lib/jrpatch.jar
cf_root/lib/macromedia_drivers.jar
cf_root/lib/viewer.jar
cf_root/lib/webcharts.jar
cf_root/lib/webchartsJava2D.jar
cf_root/runtime/lib/java2wsdl.jar
cf_root/runtime/lib/jrun-ant-tasks.jar
cf_root/runtime/lib/jrun-comp.ear
cf_root/runtime/lib/jrun-xdoclet.jar
cf_root/runtime/lib/jrun.jar
cf_root/runtime/lib/jrun.policy
cf_root/runtime/lib/jrunwizard-installer.jar
cf_root/vruntime/lib/jrunwizard.jar
cf_root/runtime/lib/jspc.jar
cf_root/runtime/lib/migrate.jar
cf_root/runtime/lib/oem-xdoclet.jar
cf_root/runtime/lib/sniffer.jar
cf_root/runtime/lib/webservices.jar
cf_root/runtime/lib/wsconfig.jar
cf_root/runtime/lib/wsdl2java.jar
cf_root/runtime/lib/xdoclet.xml
cf_root/runtime/lib/xmlscript.jar
cf_root/runtime/servers/default/flashgateway.ear
cf_root/runtime/servers/default/SERVER-INF/default-web.xml
cf_root/runtime/servers/default/SERVER-INF/jndi.properties
cf_root/runtime/servers/default/SERVER-INF/jrun-jms.xml
cf_root/runtime/servers/default/SERVER-INF/jrun-users.xml
cf_root/runtime/lib/webservices.jar
cf_root/runtime/lib/wsconfig.jar
cf_root/wwwroot/CFIDE/administrator/Application.cfm
cf_root/wwwroot/CFIDE/administrator/datasources/odbcsocket.cfm
cf_root/wwwroot/CFIDE/administrator/logviewer/_searchlog_cfformat.cfm
cf_root/wwwroot/CFIDE/administrator/logviewer/_searchlog_other.cfm
cf_root/wwwroot/CFIDE/administrator/security/cfadminpassword.cfm
cf_root/wwwroot/CFIDE/administrator/Application.cfm
cf_root/wwwroot/CFIDE/administrator/analyzer/featureview.cfm
cf_root/wwwroot/CFIDE/administrator/analyzer/fileview.cfm
cf_root/wwwroot/CFIDE/administrator/analyzer/index.cfm
cf_root/wwwroot/CFIDE/administrator/archives/archivewizard.cfm
cf_root/wwwroot/CFIDE/administrator/archives/buildwizard.cfm
cf_root/wwwroot/CFIDE/administrator/archives/deploywizard.cfm
cf_root/wwwroot/CFIDE/administrator/archives/index.cfm
cf_root/wwwroot/CFIDE/administrator/archives/wizards/archivewizard_page_applets.cfm
cf_root/wwwroot/CFIDE/administrator/archives/wizards/archivewizard_page_cfdirectorymappings.cfm
cf_root/wwwroot/CFIDE/administrator/archives/wizards/archivewizard_page_cfxtags.cfm
cf_root/wwwroot/CFIDE/administrator/archives/wizards/archivewizard_page_datasources.cfm
cf_root/wwwroot/CFIDE/administrator/archives/wizards/archivewizard_page_save.cfm
cf_root/wwwroot/CFIDE/administrator/archives/wizards/archivewizard_page_schedulebuild.cfm
cf_root/wwwroot/CFIDE/administrator/archives/wizards/archivewizard_page_scheduledtasks.cfm
cf_root/wwwroot/CFIDE/administrator/archives/wizards/archivewizard_page_settings.cfm
cf_root/wwwroot/CFIDE/administrator/archives/wizards/archivewizard_page_todolist.cfm
cf_root/wwwroot/CFIDE/administrator/archives/wizards/archivewizard_page_veritycollections.cfm
cf_root/wwwroot/CFIDE/administrator/archives/wizards/deploywizard_buttons.cfm
cf_root/wwwroot/CFIDE/administrator/cftags/resources/archives_xx.xml
cf_root/wwwroot/CFIDE/administrator/cftags/resources/code_xx.xml
cf_root/wwwroot/CFIDE/administrator/cftags/resources/datasources_xx.xml
cf_root/wwwroot/CFIDE/administrator/cftags/resources/debugging_xx.xml
cf_root/wwwroot/CFIDE/administrator/cftags/resources/extensions_xx.xml
cf_root/wwwroot/CFIDE/administrator/cftags/resources/general_xx.xml
cf_root/wwwroot/CFIDE/administrator/cftags/resources/logging_xx.xml
cf_root/wwwroot/CFIDE/administrator/cftags/resources/logviewer_xx.xml
cf_root/wwwroot/CFIDE/administrator/cftags/resources/mail_xx.xml
cf_root/wwwroot/CFIDE/administrator/cftags/resources/migrate_xx.xml
cf_root/wwwroot/CFIDE/administrator/cftags/resources/migratelog_xx.xml
cf_root/wwwroot/CFIDE/administrator/cftags/resources/probe_xx.xml
cf_root/wwwroot/CFIDE/administrator/cftags/resources/reports_xx.xml
cf_root/wwwroot/CFIDE/administrator/cftags/resources/scheduler_xx.xml
cf_root/wwwroot/CFIDE/administrator/cftags/resources/security_xx.xml
cf_root/wwwroot/CFIDE/administrator/cftags/resources/settings_xx.xml
cf_root/wwwroot/CFIDE/administrator/cftags/resources/verity_xx.xml
cf_root/wwwroot/CFIDE/administrator/datasources/Application.cfm
cf_root/wwwroot/CFIDE/administrator/datasources/db2.cfm
cf_root/wwwroot/CFIDE/administrator/datasources/db2os390.cfm
cf_root/wwwroot/CFIDE/administrator/datasources/index.cfm
cf_root/wwwroot/CFIDE/administrator/datasources/informix.cfm
cf_root/wwwroot/CFIDE/administrator/datasources/odbcsocket.cfm
cf_root/wwwroot/CFIDE/administrator/datasources/oracle.cfm
cf_root/wwwroot/CFIDE/administrator/datasources/sybase.cfm
cf_root/wwwroot/CFIDE/administrator/enter.cfm
cf_root/wwwroot/CFIDE/administrator/extensions/webservices.cfm
cf_root/wwwroot/CFIDE/administrator/homepage.cfm
cf_root/wwwroot/CFIDE/administrator/include/udflibrary.cfm
cf_root/wwwroot/CFIDE/administrator/logging/index.cfm
cf_root/wwwroot/CFIDE/administrator/logging/settings.cfm
cf_root/wwwroot/CFIDE/administrator/logviewer/_searchlog_cfformat.cfm
cf_root/wwwroot/CFIDE/administrator/logviewer/_searchlog_other.cfm
cf_root/wwwroot/CFIDE/administrator/logviewer/_searchloglogic_cfformat.cfm
cf_root/wwwroot/CFIDE/administrator/mail/index.cfm
cf_root/wwwroot/CFIDE/administrator/migration/_migrate_schedule.cfm
cf_root/wwwroot/CFIDE/administrator/migration/dsmigrate/datasourcemigrate1.cfm
cf_root/wwwroot/CFIDE/administrator/migration/migratesettings.cfm
cf_root/wwwroot/CFIDE/administrator/migration/migrationcheck.cfm
cf_root/wwwroot/CFIDE/administrator/migration/runmigration.cfm
cf_root/wwwroot/CFIDE/administrator/navserver.cfm
cf_root/wwwroot/CFIDE/administrator/reports/_reportsi10n.cfm
cf_root/wwwroot/CFIDE/administrator/reports/rendersummary.cfm
cf_root/wwwroot/CFIDE/administrator/reports/settingssummary.cfm
cf_root/wwwroot/CFIDE/administrator/right.cfm
cf_root/wwwroot/CFIDE/administrator/scheduler/_getprobes.cfm
cf_root/wwwroot/CFIDE/administrator/scheduler/editprobe.cfm
cf_root/wwwroot/CFIDE/administrator/scheduler/probes.cfm
cf_root/wwwroot/CFIDE/administrator/scheduler/scheduleedit.cfm
cf_root/wwwroot/CFIDE/administrator/scheduler/scheduletasks.cfm
cf_root/wwwroot/CFIDE/administrator/security/_fileoptions.cfm
cf_root/wwwroot/CFIDE/administrator/security/cfadminpassword.cfm
cf_root/wwwroot/CFIDE/administrator/security/index.cfm
cf_root/wwwroot/CFIDE/administrator/security/sandbox.cfm
cf_root/wwwroot/CFIDE/administrator/settings/_licensedata.cfm
cf_root/wwwroot/CFIDE/administrator/settings/version.cfm
cf_root/wwwroot/CFIDE/administrator/verity/index.cfm
cf_root/wwwroot/CFIDE/administrator/verity/k2server.cfm
cf_root/wwwroot/CFIDE/administrator/welcome.cfm
cf_root/wwwroot/CFIDE/administrator/welcomedoc.cfm
cf_root/wwwroot/CFIDE/administrator/welcomeexapps.cfm
cf_root/wwwroot/CFIDE/componentutils/cfcexplorer_utils.cfm
cf_root/wwwroot/CFIDE/probe.cfm
cf_root/wwwroot/WEB-INF/cftags/applet.cfm
cf_root/wwwroot/WEB-INF/cftags/cache.cfm
cf_root/wwwroot/WEB-INF/cftags/component.cfc
cf_root/wwwroot/WEB-INF/cftags/dump.cfm
cf_root/wwwroot/WEB-INF/cftags/form.cfm
cf_root/wwwroot/WEB-INF/cftags/grid.cfm
cf_root/wwwroot/WEB-INF/cftags/gridcolumn.cfm
cf_root/wwwroot/WEB-INF/cftags/gridrow.cfm
cf_root/wwwroot/WEB-INF/cftags/input.cfm
cf_root/wwwroot/WEB-INF/cftags/savecontent.cfm
cf_root/wwwroot/WEB-INF/cftags/select.cfm
cf_root/wwwroot/WEB-INF/cftags/slider.cfm
cf_root/wwwroot/WEB-INF/cftags/textinput.cfm
cf_root/wwwroot/WEB-INF/cftags/trace.cfm
cf_root/wwwroot/WEB-INF/cftags/tree.cfm
cf_root/wwwroot/WEB-INF/cftags/treeitem.cfm
cf_root/wwwroot/WEB-INF/debug/classic.cfm
cf_root/wwwroot/WEB-INF/debug/dockable.cfm
cf_root/wwwroot/WEB-INF/debug/dreamweaver.cfm
cf_root/wwwroot/WEB-INF/exception/detail.cfm
cf_root/wwwroot/WEB-INF/exception/exception_xx.xml
cf_root/wwwroot/WEB-INF/server-config.wsdd

Windows Replaced or added Files
cf_root\bin\connectors\Apache_connector.bat
cf_root\bin\connectors\ConnectorList.bat
cf_root\bin\connectors\IIS_connector.bat
cf_root\bin\connectors\iPlanet_connector.bat
cf_root\bin\connectors\Remove_ALL_connectors.bat
cf_root\bin\connectors\Upgrade_all_connectors.bat
cf_root\bin\updater_compile.bat
cf_root\runtime\bin\WindowsLogin.dll
cf_root\runtime\jre\lib\security\cacerts
Linux
Solaris
HP-UX
Replaced or added File
cf_root/bin/updater_compile.sh
cf_root/jre/lib/security/cacerts

Back to Contents


 

Uninstalling the Update

Use the following procedures to uninstall a ColdFusion MX Update.

Notes:

  • If you use ColdFusion MX Server with any web server except the built-in web server that comes with ColdFusion MX and JRun, you must follow the steps in the Resetting web server connectors section before uninstalling the Update.
  • If you uninstall both Updater 3 and Updater 2 and use Apache 2 as your web server, you must also replace the Apache 2.0.43 (or later) server with an earlier version of the server. To use ColdFusion MX with Updater 1 installed, you must have Apache 2.0.40. Macromedia does not recommend using ColdFusion MX with Apache 2 without an Updater.

Resetting web server connectors

If you are using ColdFusion MX Server with any web server other than the built-in web server that comes with ColdFusion and JRun, you must reset the web server connectors before you uninstall the ColdFusion MX Update.

To reset the web server connectors:

  1. Use the updated wsconfig.jar to uninstall the current connectors, as follows:
    In Windows:
    cf_root\runtime\jre\bin\java -jar cf_root/runtime/lib/wsconfig.jar-v -u

  2. On UNIX:
    cf_root/jre/bin/java -jar cf_root/runtime/lib/wsconfig.jar-v -u

  3. Replace the updated wsconfig.jar with the original JAR file in the backup folder (cf_root/cfmx_updater/cfmx_updater_XX/runtime/lib/wsconfig.jar).


  4. If you use the connector with Microsoft IIS web server, shut down IIS and delete the cf_root\\runtime\lib\wsconfig\jrunwin32.dll file.


  5. To reinstall the connectors, use one of the scripts supplied with ColdFusion MX in cf_root/bin/connectors or see the latest ColdFusion MX Release Notes.

Uninstalling a ColdFusion MX Server update from Windows

This section explains how to uninstall a ColdFusion MX update from a Windows platform.

To uninstall a ColdFusion MX update from Windows:

  1. Stop the following services:
    ColdFusion MX Application Server
    ColdFusion MX ODBC Agent
    ColdFusion MX ODBC Server


  2. Delete the cf_root\lib\jrpatch.jar file.

  3. Move all of the files in the backup folder for the update, cf_root\cfmx_updater\cfmx_updater_XX (where XX corresponds to the update you are uninstalling), to their original locations, replacing the updated files. (The file locations in the backup folder directory tree correspond to their locations relative to the cf_root directory.)


  4. Delete the ColdFusion MX generated class files from the cf_root\wwwroot\WEB-INF\cfclasses directory.


  5. Restart the services that you stopped in step 1. You might also have to restart your web server.

Uninstalling a ColdFusion MX Server update from UNIX

This section explains how to uninstall a ColdFusion MX update from a UNIX platform.

To uninstall a ColdFusion MX update from UNIX:

  1. Stop ColdFusion MX with the following command:
    /cf_root/bin/coldfusion stop


  2. Delete the cf_root//lib/jrpatch.jar file.

  3. Move all of the files in the backup folder for the update, cf_root/cfmx_updater/cfmx_updater_XX (where XX corresponds to the update you are uninstalling) to their original locations, replacing the updated files. (The file locations in the backup folder directory tree correspond to their locations relative to the cf_root directory.)


  4. Delete the ColdFusion MX generated class files from the cf_root/wwwroot/WEB-INF/cfclasses directory.


  5. Restart ColdFusion MX with the following command:
    /cf_root/bin/coldfusion start
    You might also have to restart your web server.

Uninstalling a ColdFusion MX for J2EE update

This section explains how to uninstall a ColdFusion MX for J2EE Update from your application server and revert to your original installation of ColdFusion MX for J2EE.

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

To uninstall a ColdFusion MX for J2EE update:

  1. Follow steps 1-5 of the Installing the ColdFusion MX for J2EE Update procedure. These steps create a backup of your
  2. current ColdFusion MX configuration and any files that are not part of the ColdFusion installation. You will not use the EAR or WAR files that this step creates.

  3. Undeploy your Coldfusion
  4. MX J2EE application from your application server. Follow the procedures in the ColdFusion MX for Application Servers installation instructions for your application server. However, if you are uninstalling an update on a Windows system, and your uninstallation instructions tell you to run the uninstall.bat command, do NOT run it.

  5. Install and deploy your original version of ColdFusion MX for J2EE. Follow the ColdFusion MX for Application Servers installation instructions for your application server. If you are using the "phase 2" archive-based installers, do not open the ColdFusion MX Administrator or run the Startup wizard; you should also not need to perform the postdeployment steps in the ColdFusion MX for J2EE installation instructions, such as configuring security settings or Verity support.

  6. Follow steps 8-12 of the Installing the ColdFusion MX for J2EE Update procedure to restore your configuration and other files.

Back to Contents


 

Installing Silently on ColdFusion MX Server

A silent installation of the Updater for ColdFusion MX server does not interact with the user. This is useful when you must install on multiple computers with the same installation options. You cannot install the Update silently on ColdFusion MX for J2EE.

To Install ColdFusion MX silently, you do the following:

  1. Configure the properties file.
  2. Stop the servers.
  3. Run the updater silently.

Configuring the installer properties file

The installer properties file is an ASCII text file that defines parameters for your installation.

Naming the installer properties file

If you name your installer properties file installer.properties and put it in the same directory as the ColdFusion MX Updater file, when you run the installer from the installer file's directory, the Updater automatically uses the installer.properties file. You can name it something else or save it in a different directory, but if you do, you must always explicitly reference the properties file to use it in an installation.

Note: The name of your installer properties file must end with .properties, not .txt.

If you require more than one installer properties file for the Updaterfor example, to use different properties for installing within or outside of your organizationMacromedia recommends that you give each a descriptive name. Ensure that the name ends with .properties.

Creating the installer properties file

You must specify the following settings in the installer properties file:

INSTALLER_UI Must have the value INSTALLER_UI=silent.
REBOOT Required for Windows only. Not used for UNIX. Must have the value REBOOT=1
USER_INSTALL_DIR Location of the cf_root directory in which ColdFusion MX is installed.
USER_MAGIC_FOLDER_1 Location of the CFIDE directory on your system.

A sample installer properties file might contain the following text on a UNIX system:

INSTALLER_UI=silent
USER_INSTALL_DIR=/opt/coldfusionmx
USER_MAGIC_FOLDER_1=/var/www/html/CFIDE

A sample installer properties file might contain the following text on a Windows system:

INSTALLER_UI=silent
REBOOT=1
USER_INSTALL_DIR=C:\\CFusionMX
USER_MAGIC_FOLDER_1=C:\\Inetpub\\wwwroot\\CFIDE

The following rules apply to the properties file:

  • The directories that the file specifies must exist. Otherwise, the Updater does not function properly.
  • The propreties file must have all three entries.
  • If you use backward slashes (\) in file paths in the properties file, you must escape them by using double backslashes (\\), as shown in the example.

Stopping the servers

If ColdFusion is running on the system on which you are installing, your installation script must stop ColdFusion before you run the Updater. On Windows systems, the script must also stop IIS services.

Stopping servers on Windows

On Windows systems, the install script must issue the following commands to stop services before running the silent installer:

NET STOP "ColdFusion MX Application Server"
NET STOP "ColdFusion MX ODBC Agent"
NET STOP "ColdFusion MX ODBC Server

If you use IIS as your web server for ColdFusion MX, stop the World Wide Web Publishing Service, as follows:

NET STOP "World Wide Web Publishing Service"

If you use a web server other than IIS or the ColdFusion MX built in web server, stop the web server.

Note: To install ColdFusion MX Updater, the jrun.exe and inetinfo.exe programs must be stopped. In a small number of cases, requesting Windows to stop the services might not ensure that these programs are stopped.

Stopping servers on UNIX and Linux

On UNIX and Linux systems, run the following command to stop ColdFusion:

cf_root/bin/coldfusion stop

You should also stop the web server.

Running the Updater

Note: These instructions use the general term cfmx_updater_file to refer to the Updater file. The specific Updater file name differs, based on the operating system. The file names for Updater 3 are as follows:

Windows cfmx_updater_windows_r3.exe
Linux cfmx_updater_linux_r3.bin
Solaris cfmx_updater_solaris_r3.bin
HPUX cfmx_updater_hpux_r3.bin

The Updater command has the following format:

On UNIX:
./cfmx_updater_file -i mode [-f propertiesFilePath]

On Windows:
cfmx_updater_windows_r3 -i mode [-f propertiesFilePath]

The mode argument specifies the mode for the installation. The following table describes the valid mode values:

Mode Description

silent

Do not display any interface (requires an installer properties file).

console

Display a command-line console interface (default for UNIX, not supported for Windows).

gui

Display a graphical user interface for the Updater (default for Windows).

To run the Updater silently, you must specify -i silent.

The propertiesFilePath argument specifies the installer properties file that contains specific instructions for the Updater. The path can be an absolute file path or a path relative to the directory containing the Updater setup command file.

You do not require the propertiesFilePath argument if all of the following are true:

  • The properties file is called installer.properties.
  • The properties file is located in the same directory as the installer file.
  • You are running the Updater setup command file from within this directory.

If these are true, the Updater uses the installer.properties file by default.

Use the following command to run from the Updater from within the directory that contains the ColdFusion MX Updater setup command file and use the default installer.properties file located in the same directory:

On UNIX:
./cfmx_updater_file -i silent

On Windows:
cfmx_updater_windows_r3 -i silent

The following sample command shows how you can run the Updater from outside the installer directory and uses an installer properties file that is located in a different directory on a Linux system. You enter the command on a single line; it spans two lines for display.

/home/jdoe/software/cfmx_updater_linux_r3.bin -i silent
     -f /home/jdoe/config/cfmx_updater_installer.properties

The following is a similar command line for Windows:

C:/downloads/CFUpdater/cfmx_updater_windows_r3 -i silent
     -f C:/downlads/CFUpdater/config/cfmx_updater_installer.properties


Back to Contents
Part 1 -- Known Issues and Installation Instructions
Part 2 -- Issues Fixed in this Updater Release
Part 3 -- Issues Fixed in Previous Updater Releases