Accessibility
Adobe
Sign in Privacy My Adobe

ColdFusion Support Center

Installing and Deploying ColdFusion MX 7 on IBM WebSphere 5

You can deploy the Macromedia ColdFusion MX 7 J2EE configuration as an application running on a Java 2 Enterprise Edition (J2EE) application server. This document describes how to deploy this configuration on IBM WebSphere 5.

About this document

This document describes procedures that are specifically required to install and deploy the Macromedia ColdFusion MX 7 J2EE configuration on IBM WebSphere 5.1. It requires you to be familiar with, and refers to, information and instructions in Installing and Using ColdFusion MX, which is available on LiveDocs.

Before continuing, you should read the ColdFusion MX 7 Release Notes. You should also read the chapters "Preparing to Install ColdFusion MX 7" "Installing the J2EE Configuration", and "Configuring Your System" in Installing and Using ColdFusion MX.

Conventions in this document

This document uses the following conventions to reference WebSphere and ColdFusion directories:

  • websphere_root - The directory in which IBM WebSphere Application Server is installed; for example, C:\Program Files\WebSphere in Windows, and /opt/WebSphere on UNIX.
  • cf_webapp_root - The directory to which the ColdFusion web application is deployed; for example, C:\Program Files\WebSphere\AppServer\installedApps\MyHost\cfusion.ear\cfusion.war in Windows, and /opt/WebSphere/AppServer/installedApps/MyHost/cfusion.ear/cfusion.war on UNIX.
  • java_home - The root directory of your Java 2 software development kit (J2SDK); for example, C:\j2sdk1.4.1.

Installing and deploying Macromedia ColdFusion MX

Before you can run ColdFusion applications, complete the following procedures to install and deploy ColdFusion MX to your application server:

Note: This document describes how to install ColdFusion MX directly from the cfusion.ear file. You can also install ColdFusion MX as a WAR file, but the process is more complex. To install using a WAR file, you must expand the cfusion.ear file into its constituent WAR files and deploy the cfusion.war file, specifying a context root in the WebSphere Administrative Console. If you do not deploy ColdFusion at the / context root, you must also deploy the rds.war file and specify /CFIDE as its context root.

Installing the ColdFusion MX files

The specific file that you use to install ColdFusion MX for IBM WebSphere Application Server depends on your operating system. The following table lists the supported operating systems and the files on the product CD that you use to install ColdFusion MX:

Operating system Installation file
Windows coldfusion-70-win.exe
Linux coldfusion-70-lin.bin
Solaris coldfusion-70-sol.bin
AIX or other OS coldfusion-70-other.jar

These installers are available on the Macromedia website. There is no specific installer for WebSphere; you can download any version that matches your platform.

Use the following procedure to install the ColdFusion MX EAR file and installation documentation.

To install ColdFusion MX files:

  1. Ensure that your system environment meets the system requirements described in Installing and Using ColdFusion MX.
  2. Read the ColdFusion MX 7 Release Notes for any late-breaking information or updates.
  3. If you have the ColdFusion MX CD-ROM, insert the CD. Otherwise, download the installer file for your platform from the Macromedia website or a designated network.
  4. Start the installation program. Do one of the following, depending on your operating system:

    System Procedure
    Windows Double-click the installer file.
    Solaris or Linux

    Set the working directory to the directory that contains the installer file listed in the preceding table.

    Enter the installer file for your operating system, followed by the -i console switch; for example:

    ./coldfusion-70-lin.bin -i console
    AIX

    Set the working directory to the directory that contains the JAR file listed in the preceding table. Enter the following command, replacing java_home with the path to the bin directory for your JRE installation:

    java_home/java -jar coldfusion-70-other.jar -i console

  5. Follow the instructions in the installation program. Use the following information to complete J2EE-specific sections of the installation program. For information on other installation options, see Installing and Using ColdFusion MX.

    • On the Install Configuration page, select J2EE configuration and ensure that EAR file is selected.
    • ColdFusion asks you for the directory in which to install the files. These files are required to deploy ColdFusion on WebSphere, but are not required afterward. Therefore, you can specify a staging area or temporary file location.
    • On the Context Root page, specify a name for the ColdFusion MX application context root. The context root is the first part of the URL for all requests sent to the application. The application server uses the context root to determine which web application must service an incoming request The default value is cfmx.
    • On the Servlet API Version page, accept the default, Java Servlet API 2.3.
  6. The Install Wizard puts the EAR file and related information files in the specified location and displays the Installation Complete page. Click Done and continue with one of the following procedures:

    The installer creates the following log file: install_root/Macromedia_ColdFusion_MX_7_InstallLog.log, where install_root is the directory that you specify when you install the ColdFusion MX files. If you contact Technical Support for installation support, you must send them this log file.

Deploying ColdFusion MX on WebSphere

This section describes how to deploy ColdFusion MX on WebSphere 51.

To deploy ColdFusion MX on WebSphere 5.1:

  1. Start the IBM WebSphere Application Server, if it is not running.
  2. Run the IBM WebSphere Administrative Console, if it is not running.
  3. Select Applications > Install New Application.
  4. The initial Preparing for the Application Installation page appears. Enter the path to the EAR file that you installed in the Installing the ColdFusion MX files procedure; for example, C:\CFusionMX7\cfusion.ear. Leave the Context Root box empty and click Next.

    Note: If you are running the Administrative console from a browser that is not on the same system where WebSphere is running (that is, not from localhost), use the Server Path option, which enables directory browsing on the server file system.

  5. Accept the default values on the second Preparing for the Application Installation page, if appropriate for your WebSphere configuration. Click Next.
  6. WebSphere might display an Application Security Warnings page with a message that starts as follows at the bottom of the page: "ADMA0080W: A template policy file without any permission set is included in the 1.2.x enterprise application." You can safely ignore this warning. Click Continue.
  7. The Step 1: Provide Options to Perform the Installation panel of the Install New Application procedure appears. Accept the default values, if appropriate for your WebSphere configuration. Click Next.

  8. In Step 2: Map Virtual Hosts for Web Modules, select the virtual host or hosts in which to install the ColdFusion MX application and Remote Development Services (RDS) support. RDS must be on the same virtual host and port as ColdFusion. Click Next.
  9. In Step 3: Map modules to Application Servers, if you have multiple application servers, select the application server in which to install the ColdFusion application and RDS support. Click Next.
  10. In Step 4: Summary, review the installation configuration and click Finish.
  11. When the "Application Macromedia ColdFusion MX installed successfully" message appears on the Installing page, click the Save to Master Configuration link, and click the Save button on the Save page to save your workspace.

    Note: If you changed the application name in step 7, the message uses your application name.

  12. Do the following to ensure that ColdFusion sandbox security secures Java access to files and network resources:
    1. On the WebSphere Administrative Console Security > Global Security panel, ensure that the Enforce Java 2 Security option is selected.
    2. If you made any changes in step a, save your configuration.
  13. If the Enforce Java 2 Security option is selected on the Security > Global Security panel (that is, you use the Java security policy manager), do the following:

    1. Add the following lines to the JVM's security policy file, java.policy (for example, C:\Program Files\WebSphere\AppServer\java\jre\lib\security\java.policy):
       
      grant {
          permission java.security.AllPermission;
          };
      
    2. Restart the application server.
  14. Proceed as follows:

Running the Configuration and Settings Migration Wizard

After you deploy ColdFusion MX, run the Configuration and Settings Migration Wizard, as follows:

  1. Start the ColdFusion Application in the WebSphere Administrative Console Applications > Enterprise Applications panel, if it is not already running: Select the box next to Macromedia ColdFusion MX (or the application name that you specified when you deployed ColdFusion MX), and click Start. You might have to stop and restart the application server on which the ColdFusion application runs before you can start ColdFusion MX.
  2. Run the Configuration and Settings Migration wizard in your browser by entering the URL for the ColdFusion MX Administrator. The URL has the following form:

    http://host:[port]/cf_context_root/CFIDE/administrator
    for example:
    http://localhost:9080/cfmx/CFIDE/administrator

  3. ColdFusion runs the Configuration and Settings Migration Wizard. Enter the Administrator password that you specified when you installed ColdFusion MX files.
  4. The wizard runs. You do not have to specify information, but you must click the Next button after each step completes. When the wizard displays the Finish page, click OK to open the ColdFusion MX Getting Started page. You can select ColdFusion Administrator at the bottom of the page to open the Administrator and configure ColdFusion features. Running the Administrator confirms that the installation procedure was successful. If you upgraded from an earlier ColdFusion MX version, you can confirm that the wizard successfully migrated your old Administrator settings.

Note: The next time you specify http://host:[port]/cf_context_root/CFIDE/administrator in a browser, the ColdFusion MX Administrator appears. To display the Getting Started page and learn more about ColdFusion MX 7, select Getting Started from the Administrator's top navigation bar.

Installing optional components

ColdFusion MX 7 includes optional features that you must install separately:

  • Report Builder
  • Dreamweaver extensions for ColdFusion

If you do not install the Verity search service when you install ColdFusion MX 7, you can also install it separately. To do so, follow the instructions in the "Installing the Verity search server separately" section in Installing and Using ColdFusion MX.

When you install ColdFusion MX 7, the installer puts installation programs for the Report Builder and Dreamweaver extension in cf_webapp_root\CFIDE\installers directory.

  • To install the Report Builder, double-click the CFReportBuilderInstaller.exe file.
  • To install the Dreamweaver extensions, double-click the CFMX7DreamWeaverExtensions.mxp file.

Updating an existing ColdFusion MX installation

If you previously deployed ColdFusion MX for J2EE or the ColdFusion MX 6.1 J2EE configuration on your application server, you must also perform the following steps as part of the installation procedure.

Caution: This procedure requires you to undeploy your existing ColdFusion MX application. Make sure to back up all the files and settings that you want to carry over to your updated installation, as described in steps 3 and 4.

  1. In the WebSphere Administrative Console, stop the ColdFusion application and RDS application (if it is running).
  2. (Windows only) If you installed the SequelLink ODBC Agent, stop the ColdFusion MX or ColdFusion MX 6.1 ODBC Agent and ODBC Server services before you start the installation wizard.
  3. Save your application files by copying them to a backup directory that is not under cf_webapp_root.
  4. Save settings by copying the ColdFusion MX 6.1files cf_webapp_root/WEB-INF/cfusion/lib/neo-*.xml to a backup directory.
  5. Undeploy the existing copy of the ColdFusion J2EE application. Do the following:
    1. On the WebSphere Administrative Console Applications > Enterprise Applications page, select the ColdFusion application (the default name is Macromedia ColdFusion MX). If the application is running, click Stop; when it has stopped, select it again. Click Uninstall.
    2. WebSphere might display the warning "The operation did not complete in the expected amount of time. It may have completed successfully. Check the logs for details." This message indicates that uninstalling the application is taking some time; it does not necessarily indicate a problem. You can check the J2EE server logs (for example, C:\Program Files\WebSphere\AppServer\logs\server1\SystemOut.log) for any errors before proceeding.
  6. When the uninstall operation completes, do the following:
    1. In the Messages box at the top of the Administrative Console page, click the Save link to apply changes to the master configuration. Then click the Save button on the Save page to save your workspace; this might take some time. When the configuration is saved, the main Administrative Console page appears.
    2. Stop the WebSphere Application Server.
    3. Delete the root directory of the ColdFusion enterprise application; for example, C:\Program Files\WebSphere\AppServer\ installedApps\MyNode\cfusion.ear.
    4. Restart the WebSphere Application Server.
  7. If you have not already done so, follow the instructions in Installing the ColdFusion MX files.
  8. Follow the instructions in Deploying ColdFusion MX on WebSphere.
  9. Open the WebSphere Administrative Console Enterprise Applications panel and ensure that the ColdFusion application is stopped.
  10. Copy the application files in the backup directory that you specified in step 3 back to your cf_webapp_root directory (for example, C:\Program Files\WebSphere\AppServer\installedApps\MYNODE\cfusion.ear\cfusion.war).
  11. Create a directory named cf6settings in the cf_webapp_root/WEB-INF/cfusion/lib directory.
  12. Copy the setting files that you saved in step 4 to the cf_webapp_root/WEB-INF/cfusion/lib/cf6settings directory.
  13. Edit the cf_webapp_root/WEB-INF/cfusion/lib/adminconfig.xml file by setting the value of the runmigrationwizard and the migratecf6 switch to true.
  14. Restart the ColdFusion MX 7 application.
  15. Run the Configuration and Settings Migration Wizard, as described in Running the Configuration and Settings Migration Wizard.

Enabling and configuring specific ColdFusion MX functionality

For some ColdFusion MX functionality to work properly, you must manually configure your application server.

This section provides instructions for procedures that are specific to WebSphere 5. These instructions describe what to do for the following functionality:

Additional procedures are identical for all J2EE platforms and are documented in Chapter 5, "Configuring Your System" in Installing and Using ColdFusion MX.

Enabling features with operating system-specific binaries

This step is required to support the following features that use binaries that are specific to your operating system:

  • CFX tags written in C++
  • Microsoft Access driver with Unicode support (Windows only)

These features work on Windows, Linux, and Solaris only.

Use the procedure for your operating system to configure the search paths to find the required binary files. This files are located in the cf_webapp_root\WEB-INF\cfusion\lib directory in Windows, and the cf_webapp_root/WEB-INF/cfusion/lib directory on UNIX.

To configure operating system-specific binary support in Windows:

  1. Make a backup copy of the setupCmdLine.bat file, located in the websphere_root\AppServer\bin directory.
  2. Open the original file for editing and add the following on a single, long line before the line that starts with SET WAS_CLASSPATH:

    SET CFMX_APPS_PATH=cf_webapp_root\WEB-INF\cfusion\lib

    Replace cf_webapp_root with the path to your web application directory; for example, enter the following:

    SET CFMX_APPS_PATH=%WAS_HOME%\installedApps\%WAS_NODE%\
    cfusion.ear\cfusion.war\WEB-INF\cfusion\lib

  3. Add the CFMX_APPS_PATH variable to the WAS_CLASSPATH by appending the following text to the path statement:

    ;%CFMX_APPS_PATH%

    The WAS_CLASSPATH line should look similar to the following:

    SET WAS_CLASSPATH=%WAS_HOME%/properties;%WAS_HOME%/lib/bootstrap.jar;
    %WAS_HOME%/lib/j2ee.jar;%WAS_HOME%/lib/lmproxy.jar;%WAS_HOME%/lib/urlprotocols.jar;%CFMX_APPS_PATH%

  4. Save the file.
  5. Add the full path to the cf_webapp_root\WEB-INF\cfusion\lib directory to the WAS_PATH variable in the setupCmdLine.bat file. The WAS_PATH line should look similar to the following:

    SET WAS_PATH=%WAS_HOME%\bin;%JAVA_HOME%\bin;%JAVA_HOME%\jre\bin;%PATH%; C:\Program Files\IBM\WebSphere MQ\bin;C:\Program Files\IBM\WebSphere
    MQ\java\bin;C:/Program Files/IBM/WebSphere MQ/WEMPS\bin;%WAS_HOME%\
    installedApps\%WAS_NODE%\cfusion.ear\cfusion.war\WEB-INF\cfusion\lib

  6. Save the file and restart your WebSphere Application Server.

To configure operating system-specific binary support on Solaris and Linux:

  1. Make a backup copy of the startServer.sh file, located in the websphere_root/AppServer/bin directory.
  2. Open the original file for editing, and in the PLATFORM case block, just above the LD_LIBRARY_PATH line, add the following entry on a single, long line.

    Note: The path specifications in these instructions assume that you deployed ColdFusion using the standard application name (Macromedia ColdFusion MX) and did not rename the application.

    On Solaris:
    CFMX_APPS_PATH=cf_webapp_root/WEB-INF/cfusion/lib

    Replace cf_webapp_root with the path to your web application root directory; for example, enter the following:

    CFMX_APPS_PATH="$WAS_HOME"/installedApps/"$WAS_NODE"/
    cfusion.ear/cfusion.war/WEB-INF/cfusion/lib

    On Linux:
    CFMX_APPS_PATH=cf_webapp_root/WEB-INF/cfusion/lib

    Replace cf_webapp_root with the path to your web application root directory; for example, enter the following:

    CFMX_APPS_PATH="$WAS_HOME"/installedApps/"$WAS_NODE"/
    cfusion.ear/cfusion.war/WEB-INF/cfusion/lib

  3. Append the CFMX_APPS_PATH environment variable to the LD_LIBRARY_PATH entry. The resulting line should be similar to the following:

    LD_LIBRARY_PATH="$WAS_LIBPATH":$LD_LIBRARY_PATH:$CFMX_APPS_PATH

  4. Save the file and restart your WebSphere Application Server.

Enabling access to COM objects (Windows only)

This section describes how to enable Component Object Model (COM) support in Windows after installing ColdFusion MX. COM support is required to use the cfreport tag with Crystal Reports. It is not required for the ColdFusion Report Builder or any reports that you create with the ColdFusion reporting feature.

To enable COM support:

  1. In the WebSphere Administrative Console, open the Node Name > Servers > Application Servers panel, select the application server for your ColdFusion MX application, and select the Process Definition link in the Additional Properties box of the Configuration tab. Select the Java Virtual Machine link in the Process Definition Additional Properties panel and add the following line to the Generic JVM Arguments entry:

    -DJINTEGRA_NATIVE_MODE -DJINTEGRA_PREFETCH_ENUMS

  2. Click OK
  3. Save your configuration file.
  4. Make a backup copy of the setupCmdLine.bat file, located in the websphere_root\AppServer\bin directory.
  5. Open the original file for editing and add the following on a single, long line:

    SET PATH=%PATH%;cf_webapp_root\WEB-INF\cfusion\jintegra\bin;cf_webapp_root\WEB-INF\
    cfusion\jintegra\bin\international

    Replace cf_webapp_root with the path to your web application root directory; for example, enter the following:

    SET PATH=%PATH%;%WAS_HOME%\installedApps\%WAS_NODE%\cfusion.ear\cfusion.war\WEB-INF\cfusion\jintegra\bin;%WAS_HOME%\installedApps\
    %WAS_NODE%\cfusion.ear\cfusion.war\WEB-INF\cfusion\
    jintegra\bin\international

  6. Save the file and restart your computer.

In some cases, you might also have to do the following to register the Microsoft Type viewer:

  1. Open a console window and go to cf_webapp_root\WEB-INF\cfusion\lib.
  2. Register TypeViewer.dll by issuing the following command:

    regsvr32 TypeViewer.dll

Enabling charting and graphing (UNIX)

This section describes how to configure your application server to use ColdFusion MX charting and graphing (cfchart, cfchartdata, and cfchartseries tags) on AIX, Linux, and Solaris systems. This step is not required to enable charting and graphing in Windows.

Note: For instructions on enabling charting on servers that use a 1.3.x JVM, see cf_webapp_root\WEB-INF\cfusion\charting\java1.3\readme.txt

To enable charting and graphing:

  1. Open the WebSphere Administrative Console.
  2. In the left navigation bar, select Node_name > Servers > Application Servers.
  3. Select your J2EE application server; for example, Server1.
  4. On the Configuration tab of the Application server page, click the Process Definition link in the Additional Properties box.
  5. On the Process Definition page, click the Java Virtual Machine link in the Additional Properties box.
  6. If you are running ColdFusion MX on a system without a monitor, do the following:
    1. In the Additional Properties box at the bottom of the page, click the Custom Properties link.
    2. On the Custom Properties page, click New and add a system property, completing the fields as follows:

      Name java.awt.headless
      Value true

    3. Click OK to return to the Java Virtual Machine page.
  7. Click OK.

Disabling RDS

For security reasons, Macromedia recommends that you disable RDS on a production server. If you enable RDS when you install ColdFusion MX 7, you can disable it at a later time, as described in the following instructions.

Note: If you disable RDS, the following ColdFusion MX 7 features do not work: the Browse Server button in the ColdFusion MX Administrator (for example, on the ColdFusion Mappings page), and the Query Builder and charting in the ColdFusion Report Builder.

To disable RDS:

  1. Disable the ColdFusion MX web module RDS Servlet. Doing so ensures that ColdFusion MX cannot respond to any RDS requests.
  2. If your ColdFusion MX application context root is not /, disable or undeploy the RDS redirector web module.

Disabling the RDS Servlet

To disable the RDS Servlet:

  1. Stop ColdFusion. In the WebSphere Administrative Console, select the Applications > Enterprise Applications panel, select the Macromedia ColdFusion MX application, and click Stop.
  2. Do the following in both the cf_webapp_root\WEB-INF\web.xml and the websphere_root\AppServer\config\cells\NodeName\applications\
    cf_application_name.ear\deployments\cf_application_name\cfusion.war\WEB-INF\web.xml files (or the equivalent paths in UNIX). For example, change the following files:

    C:\Program Files\WebSphere\AppServer\installedApps\MYNODE\cfusion.ear\cfusion.war\WEB-INF\web.xml

    C:\Program Files\WebSphere\AppServer\config\cells\MYNODE\applications\cfusion.ear\deployments\
    Macromedia ColdFusion MX\cfusion.war\WEB-INF\web.xmll

    1. Back up the ColdFusion web module web.xml file.
    2. Open the original web.xml file for editing.
    3. Comment out the RDS Servlet definition, as follows:

        <!--
        <servlet id="macromedia_servlet_8789"> <servlet-name>RDSServlet</servlet-name> <display-name>RDS Servlet</display-name> <servlet-class>coldfusion.bootstrap.BootstrapServlet</servlet-class> <init-param id="InitParam_103401311065856789"> <param-name>servlet.class</param-name> <param-value>coldfusion.rds.RdsFrontEndServlet</param-value> </init-param> </servlet> -->
      

      Some of the text in the servlet definition might vary.

    4. Comment out the RDS Servlet mapping, as the following example shows:

      <!--
        <servlet-mapping id="macromedia_mapping_9">
          <servlet-name>RDSServlet</servlet-name>
          <url-pattern>/CFIDE/main/ide.cfm</url-pattern>
        </servlet-mapping>
      -->
      

      Note: The servlet-mapping id value might vary.

    5. Save the file.
  3. Restart the ColdFusion MX application.

RDS is disabled on the ColdFusion MX server.

Disabling the RDS redirector

If you installed ColdFusion MX at a context root other than /, use the following procedure to disable the RDS redirector web module without undeploying it.

Note: If you disable (or undeploy) the RDS redirector and do not disable the RDS servlet, RDS services are still available using the ColdFusion MX application context root, but tools that use RDS and require a context root of /, such as Dreamweaver and older versions of HomeSite, do not work.

To disable the RDS web module:

  1. In the WebSphere Administrative Console, select Node_name > Applications > Enterprise Applications.
  2. Stop the Macromedia ColdFusion MX application if it is running.
  3. Click the Macromedia ColdFusion MX Application link to display the Configuration page, and then select the Local Topology tab.
  4. Expand the Macromedia_ColdFusion_MX entry in the Applications tree, and then expand the Web Module folder and click the rds.war link to display the rds.war configuration page.
  5. Click the Target Mappings link in the Additional Properties box, and click the link to your application server; for example, Server1.
  6. On the Configuration page General Properties box, clear the Enabled check box, and click OK.
  7. Click the Save to Master Configuration link at the top of the Target Mappings page and click the Save button on the Save page to save your workspace.
  8. When the configuration has been saved and the main Administrative Console page appears, stop and restart the application server.
  9. Start the ColdFusion Application, if necessary.

The RDS web module is disabled. You can re-enable the RDS web module by repeating this procedure and selecting the Enabled check box.

Limitations and Troubleshooting

The following sections describe issues limitations and issues that are specific to ColdFusion MX 7 on WebSphere.

If you encounter problems with your ColdFusion MX installation that are not described in this section, see the "Troubleshooting" chapter in Installing and Using ColdFusion MX. This chapter includes troubleshooting information for specific problems, including information on handling unsupported keysize or algorithm parameter errors. If you need additional information, consult the ColdFusion MX 7 Release Notes and the ColdFusion Technical Support website.

Running ColdFusion MX on clustered systems

ColdFusion MX is not supported on WebSphere vertical clusters, where two or more ColdFusion instances share a common file system on a single machine, but use separate JVMs. This limitation is caused because the instances share resources that have permanently configured pathnames.

You can use WebSphere horizontal clusters, which have separate file systems on separate machines. In this case, ColdFusion resources are not shared. Each ColdFusion instance has a separate ColdFusion MX Administrator, and must be administered independently. You should limit the cluster size to no more than ten instances, however. You can use ColdFusion MX J2EE session sharing if you enable IBM memory-to-memory session replication.

Pages with double-byte characters are blank

If you use IBM JVM 1.4.x on UNIX or Linux and the CFML page is encoded in a character encoding that does not match the Java default file encoding (which is determined by the local setting), the page appears blank on the user's browser.

You use the CFML cfprocessingdirective tag pageEncoding attribute to identify the page encoding.

To avoid this issue, do any of the following:

  • Write the CFML page using the Java default file encoding.
  • Write the CFML page using UTF-8 and with a byte order mark (BOM).
  • Add the following entry to the JVM configuration:

    -Dibm.stream.nio=true

The enctype attribute causes errors with multi-byte characters in form data

If you set the enctype attribute of the cfform CFML tag or form HTML tag, multi-byte characters, such as those in the Chinese big5 encoding, in text submitted by the form are not received in the action page Form scope variable; single-byte characters in the string are received. This issue is independent of the operating system locale.

The workaround is to remove the enctype parameter from the cfform or form tag.

Undeploying ColdFusion MX

This section describes how to undeploy ColdFusion MX from IBM WebSphere Application Server.

To undeploy ColdFusion MX:

  1. (Windows only) If the ODBC services are installed, remove the services by navigating to the cf_webapp_root\WEB_INF\cfusion\db\SequeLink Setup directory and running the RemoveSequeLink.bat file.
  2. Open the WebSphere Administrative Console.
  3. Select the Node_name > Applications > Enterprise Applications page. If the ColdFusion application status is Started, select the check box next to the Macromedia ColdFusion MX entry and click Stop.
  4. When the ColdFusion application server has stopped, select the check box next to the Macromedia ColdFusion MX entry again and click Uninstall.
  5. WebSphere uninstalls the ColdFusion application. Save the new configuration by clicking the save link in the messages box. The Save panel appears. Click Save.
  6. Stop the WebSphere Application Server.
  7. If WebSphere did not delete the cf_webapp_root directory, delete it. You might have to restart your computer before you can delete the files.
  8. If you installed the Verity search service or the Report Builder on Windows, use the Add or Remove Programs control panel to uninstall these programs. If you installed the Verity search service on Linux or Solaris, run verity-uninstall.sh, located in the directory where you installed Verity.

Top Support Topics

 

More ColdFusion Topics

Choose a category to see more topics.

Request Support

 

Additional ColdFusion Resources

 

ColdFusion Downloads

 

Outside Resources

 

Feedback

 

Community