Accessibility
Adobe
Sign in Privacy My Adobe

ColdFusion Support Center

Installing and Deploying ColdFusion MX 7 on IBM WebSphere 4

Macromedia ColdFusion MX 7 supports the following configurations:

  • Server configuration - Lets you install one instance of ColdFusion MX 7 with an embedded Java 2 Enterprise Edition (J2EE) server. This configuration most closely resembles the ColdFusion MX base release and other releases prior to ColdFusion MX, such as ColdFusion 5 and ColdFusion 4.5. This was formerly known as the stand-alone configuration. For information on installing this configuration, see Installing and Using ColdFusion MX.
  • Multiserver configuration (Enterprise and Developer Editions only) - Installs Macromedia JRun and automatically deploys ColdFusion MX 7 in a separate JRun server instance. For information on installing this configuration, see Installing and Using ColdFusion MX.
  • J2EE configuration (Enterprise and Developer Editions only) - Lets you deploy ColdFusion MX 7 as a Java application running on a Java 2 Enterprise Edition (J2EE) application server, such as JRun 4, IBM WebSphere, or BEA WebLogic. These instructions tell you how to deploy ColdFusion MX 7 on JRun 4.

When you run ColdFusion MX 7 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 4, you deploy ColdFusion MX 7 as an EAR file.

About this document

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

Before continuing, you should read the ColdFusion MX 7 Release Notes. You should also read the "Preparing to Install ColdFusion MX 7" and "Installing the Multiserver Configuration" chapters in 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_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, you must 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 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-ibm-sol.bin
AIX coldfusion-70-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 7 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-70-lin.bin -i guiIn console mode, 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 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-70-other.jar -i gui

    In console mode:

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

    For the evaluation version:

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

  6. Answer the questions. When prompted, do the following:

    1. Select Developer Edition.
    2. Select J2EE configuration/WAR file
    3. Specify whether to install ODBC services (Windows only), search services, and supporting material.
    4. Specify the installation directories for ColdFusion MX and the Search Service.
    5. Select the Java Servlet API 2.3 or greater option.
    6. Specify a password for use with the ColdFusion MX Administrator.
    7. (Only if RDS is enabled) Specify a password for use with Remote Development Services (RDS).

      The Install Wizard places the cfusion.war and rds.war files in the installation directory.

    When the installation is complete, the EAR file and any backup files are put in the specified locations. The Installation Wizard closes 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 4.

Deploying ColdFusion MX on Single Server Edition

Use the following procedure to deploy ColdFusion MX on WebSphere 4 Advanced Edition Single Server.

To deploy on WebSphere 4 Advanced Edition Single Server:

  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, see the instructions in Upgrading to ColdFusion MX 7 in Enabling and Using ColdFusion MX 7 Features on Your J2EE Server before continuing.
  4. Open the Nodes > node_name > Enterprise Applications page and click Install.
  5. The Application Installation Wizard page appears. In the first Path box, 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 Application Name and Context Root fields empty. Click Next.
  6. Select the virtual host or hosts in which to install the ColdFusion application and Remote Development Services (RDS) support. Click Next.
  7. Review the installation summary; if it is correct, click Finish.
  8. Save the configuration and regenerate the Plug-in configuration.
  9. On AIX systems, if you are using the standard WebSphere JVM, Version 1.3.1, or any version other than 1.4.2, ensure that the ColdFusion application is not running, and replace cf_webapp_root/WEB-INF/cfusion/lib/tools.jar with the tools.jar from your JVM (normally websphere_root\AppServer\java\lib\tools.jar).
  10. Open the Enterprise Applications panel and ensure that the ColdFusion application is stopped. Add the following lines to the JVM's security policy file, java.policy (for example, C:\WebSphere\AppServer\java\jre\lib\security\java.policy):

    grant codeBase "<file:cf_webapp_root/WEB-INF/cfusion/lib/*>" {
    permission java.security.AllPermission;
    };
    grant codeBase "<file:cf_webapp_root/WEB-INF/lib/*>" {
    permission java.security.AllPermission;
    };
    

    Replace cf_webapp_root with your web application root directory; for example, C:\WebSphere\AppServer\ installedApps\MyHost\cfusion.ear\cfusion.war.

  11. Start the ColdFusion Application in the Enterprise Applications panel. Select the box next to Macromedia ColdFusion MX, and click Start.
  12. Continue with the next section of the instructions, Running the Configuration and Settings Migration Wizard.
  13. (Windows only, optional) Install the Report Builder and Dreamweaver extensions, as described in Installing optional components in Enabling and Using ColdFusion MX 7 Features on Your J2EE Server

Deploying ColdFusion MX on Advanced Edition

Use the following procedure to deploy ColdFusion MX on WebSphere 4 Advanced Edition.

To deploy on WebSphere 4 Advanced Edition:

  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, see the instructions in Upgrading to ColdFusion MX 7 in Enabling and Using ColdFusion MX 7 Features on Your J2EE Server before continuing.
  4. Select Enterprise Applications > Install Enterprise Application.
  5. On the first page of the Install Enterprise Application Wizard, specify the node, path to the ColdFusion MX EAR file that you installed in the Installing the ColdFusion MX files procedure, and the application name (for example, cfusion). Click Next.
  6. Click Next to skip the next seven screens of the wizard.
  7. On the Selecting Virtual Hosts for Web Modules page, select the virtual host or hosts for ColdFusion MX and RDS. Click Next.
  8. On the Selecting Application Servers page, select the application servers for ColdFusion MX and RDS. Click Next.
  9. On the Completing the Application Installation Wizard page, click Finish.
  10. Do the following:

    1. Open the Enterprise Applications panel and ensure that the ColdFusion application is stopped.
    2. 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_webapp_root/WEB-INF/cfusion/lib/*>" {
      permission java.security.AllPermission;
      };
      grant codeBase "<file:cf_webapp_root/WEB-INF/lib/*>" {
      permission java.security.AllPermission;
      };
      

      Replace cf_webapp_root with your web application root directory; for example, C:\WebSphere\AppServer\ installedApps\MyHost\cfusion.ear\cfusion.war.

  11. 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 not running, and replace cf_webapp_root/WEB-INF/cfusion/lib/tools.jar with the tools.jar from your JVM (normally websphere_root\AppServer\java\lib\tools.jar).
  12. Select the application name that you specified from the Enterprise Applications list and click the Start button on the toolbar to Start the ColdFusion MX application.
  13. Continue with the next section of the instructions, Running the Configuration and Settings Migration Wizard.
  14. (Optional, Windows-only) Install the Report Builder and Dreamweaver extensions, as described in Installing optional components in Enabling and Using ColdFusion MX 7 Features on Your J2EE Server.

Running the Configuration and Settings Migration Wizard

After you deploy ColdFusion MX, you run the 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.

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 4. 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:

  • 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_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 root directory; for example, enter the following:

    SET CFMX_APPS_PATH=%WAS_HOME%\installedApps\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;%CFMX_APPS_PATH%
    
  4. Save the file and restart your computer.

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

  1. Make a backup copy of the setupCmdLine.sh file, located in the websphere_root/AppServer/bin directory.
  2. Open the original file for editing, and add the following entry on a single, long line: 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=/opt/WebSphere/AppServer/installedApps/cfusion.ear/cfusion.war/WEB-INF/cfusion/lib
    

    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=/opt/WebSphere/AppServer/installedApps/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=$LD_LIBRARY_PATH:$CFMX_APPS_PATH

  4. Ensure that LD_LIBRARY_PATH is exported (export LD_LIBRARY_PATH).
  5. Save the file and restart WebSphere.

Enabling sandbox security (AIX)

To enable sandbox security in AIX, you must grant everyone full security permissions for accessing class files. To grant full permissions, ensure that you have a websphere_root/AppServer/properties/java.policy file with the following contents:

// PERMISSIONS GRANTED TO EVERYONE
grant {
  permission java.security.AllPermission;
   };

Note: Sandbox security cannot restrict Java access to files and network resources on WebSphere 4.

Enabling access to COM objects (Windows)

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

To enable COM support:

  1. In the WebSphere Administrative Console, add the following line to your JVM arguments. In Advanced Edition Single Server, add the text to the Generic Command Line Arguments entry of the Nodes > Node Name > Application Servers > Default Server > Process Definition > JVM Settings panel. In Advanced Edition, add it to the Command Line Arguments entry of the Advanced JVM dialog, accessed from the JVM Settings tab of the Nodes > Node Name > Application Servers > Application Server Name panel.

    -DJINTEGRA_NATIVE_MODE -DJINTEGRA_PREFETCH_ENUMS

  2. Make a backup copy of the setupCmdLine.bat file, located in the websphere_root\AppServer\bin directory.
  3. 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\internationa
    

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

    SET PATH=%PATH%;%WAS_HOME%\installedApps\cfusion.ear\cfusion.war\WEB-INF\cfusion\jintegra\bin;%WAS_HOME%\installedApps\cfusion.ear\cfusion.war\WEB-INF\cfusion\jintegra\bin\international
    
  4. Save the file and restart your computer.

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 UNIX. In addition to these steps, you must add the -Djava.awt.headless=true JVM argument, regardless of JVM version.

You do not have to perform these steps to enable charting and graphing in Windows.

Advanced Edition Single Server

This section explains how to enable charting and graphing in ColdFusion MX for IBM WebSphere Application Server Advanced Edition Single Server.

To enable charting and graphing (1.3.x JVM only):

  1. Open the WebSphere Administrative Console.
  2. In the left navigation bar, select Nodes > computer_name > Application Servers > Default Server > Process Definition > JVM Settings.
  3. On the JVM Settings page, type the following in the Boot Classpath field:

    On Windows, Linux, and Solaris: cf_webapp_root/WEB-INF/lib/webchartsJava2D.jar

    On AIX: cf_webapp_root/WEB-INF/cfusion/lib/webchartsJava2D.jar

  4. Under Advanced Settings at the bottom of the page, click System Properties.
  5. On the System 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.

  6. Click OK.
  7. Click OK on the System Properties page, and then on the JVM Settings page.

Advanced Edition

This section explains how to enable charting and graphing in ColdFusion MX for IBM WebSphere Application Server Advanced Edition.

To enable charting and graphing (1.3.x JVM only):

  1. Open the WebSphere Administrative Console.
  2. In the left navigation bar, select Nodes > computer_name > server_name for the server to which ColdFusion MX was deployed.
  3. On the JVM Settings tab, add the following system properties:

    Name java.awt.graphicsenv

    Valuecom.gp.java2d.ExGraphicsEnvironment

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

  4. Click Advanced JVM Settings.
  5. In the Boot Classpath (Append) field, type the following:

    cf_webapp_root/WEB-INF/lib/webchartsJava2D.jar

  6. Click OK on the Advanced JVM Settings page.
  7. Click OK.

You can now use ColdFusion MX charting and graphing without any errors.

Supporting messages from a POP mail server (pre-Fix Pack 4)

WebSphere 4 prior to Fix Pack 4 uses JavaMail 1.1, and the cfpop tag does not work with this version. To remedy this, install IBM WebSphere 4 Fix Pack 4.

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_webapp_root\WEB-INF directory in Windows, and the cf_webapp_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

To disable the RDS redirector web module, undeploy or disable the CFMX RDS Application web module.

Undeploying ColdFusion MX

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

To undeploy ColdFusion MX on Advanced Edition Single Server:

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

    WebSphere uninstalls the ColdFusion application.

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

To undeploy ColdFusion MX on Advanced Edition:

  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 executing the RemoveSequeLink.bat file.
  2. Open the WebSphere Administrative Console.
  3. Expand the Enterprise Applications tree.
  4. Right-click the ColdFusion MX entry and select Stop.
  5. When the ColdFusion application server has stopped, right-click the ColdFusion MX entry and select Remove.
  6. 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.

Top Support Topics

 

More ColdFusion Topics

Choose a category to see more topics.

Request Support

 

Additional ColdFusion Resources

 

ColdFusion Downloads

 

Outside Resources

 

Feedback

 

Community