Accessibility
 
Home / Products / ColdFusion / Support
J2EE Support

Installing and Deploying ColdFusion MX 6.1 on IBM WebSphere 5

Macromedia ColdFusion MX 6.1 supports both a server configuration (which includes an embedded version of JRun) and a J2EE configuration (which lets you deploy ColdFusion MX as a Java application running on a Java 2 Enterprise Edition (J2EE) application server.) When you run ColdFusion MX 6.1 in the J2EE configuration, you use the application server's deployment mechanism to deploy ColdFusion MX on a J2EE 1.3 compliant application server. The Installation Wizard lets you install ColdFusion MX as an enterprise application (EAR) or as a web application (WAR). For IBM WebSphere 5, you deploy ColdFusion MX 6.1 as an EAR file.

About this document

Installing and deploying Macromedia ColdFusion MX

Enabling and configuring specific ColdFusion MX functionality

Undeploying ColdFusion MX

About this document

This document describes the procedures for installing and deploying the Macromedia ColdFusion MX 6.1 J2EE configuration on IBM WebSphere 5. It refers to overview information in Installing and Using ColdFusion MX, which is available on LiveDocs (English and Japanese only).

The ColdFusion MX 6.1 J2EE configuration supports the following WebSphere versions:

  • IBM WebSphere Application Server – Express, Version 5.0, 5.0.2, 5.1
  • IBM WebSphere Application Server, Version 5.0, 5.0.2, 5.1
  • IBM WebSphere Application Server – Network Deployment, Version 5.0, 5.0.2, 5.1 Non-Clustered, Single Server Only**
  • IBM WebSphere Application Server for Developers 5.0

Before continuing, you should read the ColdFusion MX 6.1 Release Notes. You should also read the first and third chapters of Installing and Using ColdFusion MX.

These instructions contain application server-specific instructions on installing a new copy of ColdFusion MX. For instructions on updating an existing ColdFusion MX J2EE Server installation to ColdFusion MX 6.1, and for configuration information that is common to all J2EE servers, see "Enabling and Using ColdFusion MX Features on Your J2EE Server" before continuing.

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_root - The directory to which ColdFusion is deployed; for example, C:\Program Files\WebSphere\AppServer\installedApps\MyHost\Macromedia ColdFusion MX.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, you must complete the following procedures to install and deploy ColdFusion MX to your application server:

  1. Installing the ColdFusion MX files
  2. Deploying ColdFusion MX on WebSphere
  3. Running the Configuration and Settings Migration Wizard

Note: This chapter 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 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-61-win.exe

Linux

coldfusion-61-lin.bin

Solaris

coldfusion-61-ibm-sol.bin

AIX or other OS

coldfusion-61-other.jar

These installers are available on the Macromedia website. There is no WebSphere-specific installer; 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 Release Notes for any late-breaking information or updates.
  3. Close any applications that are currently running on the computer to which you are deploying ColdFusion MX.
  4. If you have the ColdFusion MX for IBM WebSphere Application Server evaluation or product CD-ROM, insert the CD. Otherwise, download the installer file for your platform from the Macromedia website or a designated network.
  5. 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.

In GUI mode (you must have XWindows Display configured), enter the installer file for your operating system, followed by the -i gui switch; for example:

./coldfusion-61-lin.bin -i guiIn console mode, enter the installer file for your operating system, followed by the -i console switch; for example:

./coldfusion-61-lin.bin -i console

AIX

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

In GUI mode (you must have XWindows Display configured):

java_home/java -jar coldfusion-61-other.jar -i gui

In console mode:

java_home/java -jar coldfusion-61-other.jar -i consoleor, for the evaluation version,

java_home/java -jar coldfusion-61-ibm-eval-other.jar -i console

  1. Follow the instructions in the installation program. Use the following information to complete certain sections of the installation program:
    • Before installing, determine the location of a working directory into which the ColdFusion MX for J2EE EAR file should be installed.
    • The initial installer screen lets you select the language for the installer. This selection also determines the language for the online Help and installed documentation.
    • On the License Agreement page, you must select I accept the terms of the License Agreement before you can click Next.
    • On the Install Type page, select the type of installation you are making, including whether you are updating a ColdFusion MX installation to ColdFusion MX 6.1, or installing a new version of ColdFusion MX. If you select the Update option, the installer backs up your application files, including configuration files. This is required because you must undeploy your ColdFusion application as part of the update procedure. You then use the backup files to restore the application.
    • On the Install Configuration page, select J2EE configuration and make sure 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.
    • If you specify an update installation, the installer asks you to select the directory in which to back up your ColdFusion application files, and the location where you deployed the ColdFusion MX web application you want to back up, such as C:\Program Files\WebSphere\AppServer\installedApps\MyNode\Macromedia ColdFusion MX.ear\cfusion.war. If you have multiple ColdFusion MX web applications, you must run the installer once for each web application, to ensure that all files get backed up properly, and specify a different backup directory each time.

      Note: Do not specify a backup directory that is inside your current application directory. For example, do not specify a directory such as C:\Program Files\WebSphere\AppServer\ installedApps\MyNode\Macromedia ColdFusion MX.ear. When you deploy the updated version of ColdFusion MX, you first undeploy your old version of ColdFusion, which deletes files in the application directory.

    • 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 ColdFusion MX Administrator password page, enter the password to require for the ColdFusion MX Administrator.
    • Review the options in the Pre-Installation Summary section and accept them to complete the installation.

    When the installation is complete, the EAR file and any backup files are put in the specified locations. The installation wizard exits and a product registration page appears. Continue with the next section of the instructions, Deploying ColdFusion MX on WebSphere.

    Note: The installer creates the following log file: install_root/Macromedia_ColdFusion_MX_J2EE_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 5.

To deploy ColdFusion MX on WebSphere 5:

  1. Start the IBM WebSphere Application Server, if it is not running.
  2. Open the Run the IBM WebSphere Administrative Console, if it is not running.
  3. If you are updating an existing ColdFusion MX application, you must uninstall the existing copy of ColdFusion. Do the following:
    1. In Windows, if the ODBC services are installed, open the Services panel and make sure that the ColdFusion MX ODBC server and the ColdFusion MX ODBC agent are stopped.
    2. 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.
    3. 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.
    4. 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 it is complete, the main Administrative Console page appears.
    5. Stop the WebSphere Application Server.
    6. Delete the cf_root directory; for example, C:\Program Files\WebSphere\AppServer\ installedApps\MyNode\Macromedia ColdFusion MX.ear.
    7. Restart the WebSphere Application Server.
  4. Open the Applications > Install New Application page.
  5. The Preparing Application Install page appears. Enter the path to the EAR file that you installed in the Installing the ColdFusion MX files procedure; for example C:\CFMXJ2ee\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.

  6. Accept the default values on the Preparing Application Install page, if appropriate for your WebSphere configuration. Click Next.
  7. Accept the default values in the Step 1: Provide Options to Perform the Installation panel of the Install New Application procedure, if appropriate for your WebSphere configuration. Click Next.

    Note: You might want to change the application name in this step. The default name, Macromedia ColdFusion MX, is long and results in an application deployment directory name (Macromedia ColdFusion MX.ear) that is long and has spaces. These instructions use the default name, however.

  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.
  12. On AIX systems, if you are using the standard WebSphere JVM, Version 1.3.1, or any version other than 1.4.2, make sure the ColdFusion application is stopped and replace cf_root/WEB-INF/cfusion/lib/tools.jar with the tools.jar from your JVM (normally websphere_root\AppServer\java\lib\tools.jar).
  13. 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, make sure the Enabled option and Enforce Java 2 Security option are both selected.
    2. If you made any changes in step a, save your configuration.
    3. Continue with step 14.
  14. If the Enabled option and Enforce Java 2 Security option are 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 codeBase "<file:cf_root/WEB-INF/cfusion/lib/*>" {
      permission java.security.AllPermission;
      };
      grant codeBase "<file:cf_root/WEB-INF/lib/*>" {
      permission java.security.AllPermission;
      };
      

      Replace cf_root with your cf_root directory, for example, "C:\Program Files\ WebSphere\AppServer\installedApps\MyNode\Macromedia ColdFusion MX.ear\ cfusion.war".

    2. Restart the application server.
  15. If you are updating an existing ColdFusion MX application, when the workspace is saved, do the following:
    1. Open the Enterprise Applications panel and ensure that the ColdFusion application is stopped.
    2. Copy the files in the backup directory that you specified in the Installing the ColdFusion MX files procedure back to your cf_root directory (for example, C:\Program Files\WebSphere\AppServer\installedApps\ Macromedia ColdFusion MX.ear\cfusion.war). Ensure that the files from the backup directory tree overwrite any files with the same names in the cf_root directory tree.
  16. Start the ColdFusion Application in the Enterprise Applications panel. Select the box next to Macromedia 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.
  17. Continue with the next section of the instructions, Running the Configuration and Settings Migration Wizard.

Running the Configuration and Settings Migration Wizard

After you deploy ColdFusion MX, you run the ColdFusion MX 6.1 Configuration and Settings Migration Wizard. To run the wizard in your browser, enter 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

When you first access the Administrator, ColdFusion runs the Configuration and Settings Migration Wizard. Provide the wizard with the following information:

Note: When you upgrade a ColdFusion MX installation, the wizard might skip some of the following steps.

  • Enter the Administrator password you specified when you installed ColdFusion MX files.
  • Specify the RDS password. To maximize security, disable RDS on production servers. For information on disabling RDS, see Disabling RDS.
  • (Windows only) Specify whether to install the ODBC socket JDBC driver, which lets ColdFusion MX access ODBC data sources.
  • Specify whether to install example applications and supporting files (including data sources) for the ColdFusion MX Getting Started tutorial. For security reasons, Macromedia recommends that you do not install example applications on production servers.
  • The System Configuration page might tell you that you must do additional configuration steps to enable full ColdFusion MX functionality. You do not need to make these changes when you run the wizard; click Next. For information on the additional configuration steps you must take to enable all available ColdFusion MX features, see Enabling and configuring specific ColdFusion MX functionality

When the wizard displays the Finish page, click OK to open the ColdFusion MX Administrator. When the Administrator opens, you can configure ColdFusion features. Running the Administrator confirms that the installation procedure was successful. However, you must perform the tasks described in the Enabling and configuring specific ColdFusion MX functionality section before complete ColdFusion MX functionality is available.

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. It describes what to do for the following functionality:

Additional procedures are identical for all J2EE platforms and are documented in Enabling and Using ColdFusion MX Features on Your J2EE Server.

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:

  • Verity search engine and the cfcollection, cfindex, and cfsearch tags
  • CFX tags written in C++
  • The cfreport tag
  • Microsoft Access driver with Unicode support (Windows only)

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

Note: To do searches in languages other than English, including both European and Asian languages, you must also install language-specific Verity Search Packs. For more information, see Enabling and Using ColdFusion MX Features on Your J2EE Server .

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_root\WEB-INF\cfusion\lib directory in Windows, and the cf_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_root\WEB-INF\cfusion\lib;cf_root\WEB-INF\cfusion\
    lib\_nti40\bin
    

    Replace cf_root with the path to your cf_root directory; for example, enter the following:

    SET CFMX_APPS_PATH=%WAS_HOME%\installedApps\%WAS_NODE%\
    Macromedia ColdFusion MX.ear\cfusion.war\WEB-INF\cfusion\lib;
    %WAS_HOME%\installedApps\%WAS_NODE%\Macromedia ColdFusion MX.ear\
    cfusion.war\WEB-INF\cfusion\lib\_nti40\bin
    

  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;%CFMX_APPS_PATH%
    

  4. Save the file
  5. Add the full path to the cf_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%\Macromedia ColdFusion MX.ear\cfusion.war\WEB-INF\cfusion\lib
    

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

You can now use Verity in ColdFusion MX.

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 you deployed ColdFusion using the standard application name (Macromedia ColdFusion MX) and did not rename the application.

    On Solaris:

    CFMX_APPS_PATH=cf_root/WEB-INF/cfusion/lib:cf_root/WEB-INF/cfusion/
    lib/_solaris/bin
    

    Replace cf_root with the path to your cf_root directory; for example, enter the following:

    CFMX_APPS_PATH="$WAS_HOME"/installedApps/"$WAS_NODE"/Macromedia ColdFusion MX.ear/cfusion.war/WEB-INF/cfusion/lib:"$WAS_HOME"/installedApps/"$WAS_NODE"/Macromedia ColdFusion MX.ear/cfusion.war/WEB-INF/cfusion/lib/_solaris/bin
    

    On Linux:

    CFMX_APPS_PATH=cf_root/WEB-INF/cfusion/lib:cf_root/WEB-INF/cfusion/
    lib/_ilnx21/bin
    

    Replace cf_root with the path to your cf_root directory; for example, enter the following:

    CFMX_APPS_PATH="$WAS_HOME"/installedApps/"$WAS_NODE"/Macromedia ColdFusion MX.ear/cfusion.war/WEB-INF/cfusion/lib:"$WAS_HOME"/installedApps/"$WAS_NODE"/Macromedia ColdFusion MX.ear/cfusion.war/WEB-INF/cfusion/lib/_ilnx21/bin
    

  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.

You can now use Verity in ColdFusion MX.

Enabling access to COM objects (Windows only)

This section describes how to enable Component Object Model (COM) support in Windows after installing ColdFusion MX.

To enable COM support:

  1. In the WebSphere Administrative Console, open the Node Name > 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. Save your configuration file.
  3. Make a backup copy of the setupCmdLine.bat file, located in the websphere_root\AppServer\bin directory.
  4. Open the original file for editing and add the following on a single, long line:

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

    Replace cf_root with the path to your cf_root directory; for example, enter the following:

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

  5. 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_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.

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. In the Additional Properties box at the bottom of the page, click the Custom Properties link.
  7. On the Custom Properties page, click New and add a system property, completing the fields as follows:

    Name java.awt.graphicsenv

    Value com.gp.java2d.ExGraphicsEnvironment

    Note: For JDK 1.4.1 and later versions, specify com.gp.java2d.ExHeadlessGraphicsEnvironment instead of com.gp.java2d.ExGraphicsEnvironment.

  8. Click OK to return to the Java Virtual Machine page.
  9. In the General Properties box of the Java Virtual Machine page, type the following in the Boot Classpath field:

    cf_root/WEB-INF/cfusion/lib/webchartsJava2D.jar

  10. Click OK.

Disabling RDS

For security reasons, Macromedia recommends that you disable RDS on a production server.

Note: If you disable RDS, the Browse Server button does not work in the ColdFusion MX Administrator (for example, on the ColdFusion Mappings page).

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. Back up the ColdFusion web module web.xml file.

    By default, this file is in the cf_root\WEB-INF directory in Windows, and the cf_root/WEB-INF directory on UNIX.

  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>Apache-Axis 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>
    -->
    

    Note: 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_5">>
    <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.

RDS is disabled on the ColdFusion MX server.

Disabling the RDS redirector

Use the following procedure to disable the RDS redirector web module.

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, then select the Local Topologies tab.
  4. Expand the Macromedia_ColdFusion_MX entry in the Applications tree, 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 reenable the RDS web module by repeating this procedure and selecting the Enabled check box.

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_root\WEB_INF\cfusion\db\SequeLink Setup directory and executing the RemoveSequeLink.bat file.
  2. Open the WebSphere Administrative Console.
  3. Open 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_root directory, delete it. You might have to restart your computer before you can delete the files.

 


 

** Vertical and horizontal clustering not supported. Use of the Network Deployment console for deployment of ColdFusion applications is also not supported.