ColdFusion Support Center

Installing and Deploying ColdFusion MX 7 on BEA WebLogic 7 and 8.1

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 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 Install Wizard lets you install ColdFusion MX as an enterprise application or as a web application.

About this document

This document provides instructions for deploying ColdFusion MX in the J2EE configuration on BEA WebLogic 7 and 8.1. 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.

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 7, 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 JRun and ColdFusion directories:

  • cfmx_install_directory - The directory that contains the files extracted by the Install Wizard; for example, C:\cfmx or /opt/cfmx.
  • wl_root - The directory that contains WebLogic; for example, C:\bea.
  • wldomain_root - The directory that contains the WebLogic domain into which you deployed ColdFusion MX.
  • cf_webapp_root - The directory into which you deployed the ColdFusion MX web application; for example, C:\bea\user_projects\cfdomain\applications\cfusion-war.
  • java_home - The root directory of your Java 2 software development kit (J2SDK); for example, C:\j2sdk1.4.1.

Installing, deploying, and configuring ColdFusion MX 7

You can deploy ColdFusion MX 7 on BEA WebLogic 7 or 8.1 using either an EAR file or WAR files:

  • EAR file - Deploy ColdFusion MX 7 as an enterprise application with the ColdFusion web application located at the context root that you specified when you ran the Install Wizard. EAR deployment automatically manages the context root. These instructions do not cover EAR deployment.
  • WAR files - Deploy ColdFusion MX 7 as one or more web applications. These instructions describe WAR deployment.

The following procedures explain how to run the ColdFusion MX Install Wizard, how to deploy ColdFusion MX 7 using WAR files, and how to configure JRun Java virtual machine (JVM) settings for ColdFusion MX.

Note: If you are updating a currently deployed version of ColdFusion MX on WebLogic, see the instructions in Enabling and Using ColdFusion MX Features on Your J2EE Server before continuing.

To install ColdFusion MX 7 on WebLogic 7 or 8.1:

  1. Run the ColdFusion MX 7 Install Wizard, downloading and executing the platform-specific installer:
    • Windows - coldfusion-70-win.exe
    • Linux - coldfusion-70-lin.bin
    • Solaris - coldfusion-70-sol.bin
    • Other platforms - coldfusion-70-other.jar (run with java_home/bin/java -jar coldfusion-70-other.jar -i console)

    These installers are available from the CD or on the Macromedia website. There is no WebLogic-specific installer; you can download any version that matches your platform.

  2. Answer the questions. When prompted, do the following:
    1. Select Enterprise Edition, Developer Edition, or Trial, as appropriate.
    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 later 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 WAR files in the install directory.

  3. Determine the WebLogic domain in which to deploy ColdFusion MX. Optionally, create a domain.
  4. Because ColdFusion MX must run from an expanded directory structure, expand the cfusion.war and rds.war files manually, and expand the web applications by doing the following:
    1. Open a console window, navigate to the directory that contains the WAR files, and create a directory for the ColdFusion WAR file (named whatever you'd like the context root to be) and the RDS WAR file (named CFIDE in all capital letters):
      cd cfmx_install_directory
      md cfusion (Windows, mkdir cfusion on UNIX)
      md CFIDE (Windows, mkdir CFIDE on UNIX) 
    2. Change to the cfusion directory and expand the cfusion.war file with the jar command:
      cd cfusion
      java_home/bin/jar -xvf ../cfusion.war
    3. Go up one level to the install directory:

      cd ..
    4. Change to the CFIDE directory and expand the rds.war file with the jar command:

      cd rds-war
      java_home/bin/jar -xvf ../rds.war
  5. (If using a JVM 1.3.x) Download, install, and configure the Java Cryptography Extension (JCE) 1.2.2 by performing the following steps:

    1. Download the JCE installer from the Sun website.
    2. Install the JCE.
    3. Copy all the JAR files in the jce_root/lib directory to the wl_root/jdk/jre/lib/ext directory.
  6. Open the wl_root/weblogic700/server/lib/weblogic.policy file (the path to this file is different in WebLogic 8) in a text editor, comment out the restrictive permissions, and add permission; to the default permissions section, as the following example shows:

    // default permissions granted to all domains
    grant {
    	permission java.util.PropertyPermission "java.version", "read";
    permission java.util.PropertyPermission "java.vendor", "read";
    ... permission java.util.PropertyPermission "", "read"; */ }; ...
  7. Deploy the cfusion and CFIDE directory structures using your site-specific WebLogic deployment method.
  8. Review the console messages and server log to ensure that ColdFusion MX deployed successfully.
  9. Start the ColdFusion MX Administrator and run the Configuration Wizard. You start the Administrator using a URL of the form http://hostname:portnumber/context-root/CFIDE/administrator/index.cfm, as follows:

    • hostname - The machine name, IP address, localhost, or
    • portnumber - The port number of the WebLogic web server; for example, 7001.
    • context-root - The name of the directory that contains the expanded ColdFusion WAR file (If you deploy an EAR structure, this is the context root that you specified in the Install Wizard.)
  10. Successful login to the ColdFusion MX Administrator is a confirmation that the install procedure was successful. However, you must perform the tasks described in Editing the server startup script before the complete ColdFusion MX functionality is available.
  11. Code and test ColdFusion MX (CFM) pages.

    Store these pages in the cfusion-war web application root directory. For example, to display a CFM file located at wl_root/user_projects/domain1/applications/cfusion-war/eisapp/index.cfm, with a context root of cfusion, you could specify the URL as

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

Editing the server startup script

To enable full ColdFusion MX functionality, you must customize JVM arguments in the WebLogic server startup script. ColdFusion MX requires this configuration because certain types of ColdFusion MX functionality require server-specific environment settings. Also, certain ColdFusion MX features use platform-specific binary files (that is, compiled C++ files, not Java bytecode), which are provided for Windows, Solaris, and Linux.

Note: If your WebLogic version runs on an operating system other than Windows, Solaris, or Linux, you can still run ColdFusion MX, but platform-specific functionality is unavailable.

To enable support for COM, graphing, and sandbox security:

  1. Locate the startup script for the WebLogic domain. This is typically wldomain_root\startWebLogic.cmd (Windows) or wldomain_root/ (UNIX).
  2. Make a backup copy of this file.
  3. Open the startup script.
  4. Establish the following basic variables at the beginning of the script:
    • CF_WEB_INF

    For example:


    SET CF_WEB_INF=cf_webapp_root\WEB-INF
    SET CF_SHARED_LIB_DIR=%CF_WEB_INF%\cfusion\lib


  5. (Windows only) Enable ColdFusion MX Jintegra COM support by establishing the following variables:

    • PRE_PATH

    For example:

    SET JINTEGRA_PATH= %CF_WEB_INF%\cfusion\jintegra\bin; %CF_WEB_INF%\cfusion\jintegra\bin\international

    Note: Alternatively, you can use WebLogic JCOM support instead of ColdFusion MX JIntegra COM support. To use WebLogic JCOM support, see Enabling WebLogic jCOM support (Windows only).

  6. Enable access to Verity binary files through the following variables:
    For example:

    @rem Set up shared library path for CFMX to pick up Verity
    @rem shared libs. Use path syntax - entries separated by colon.
    # Set up shared library path for CFMX to pick up Verity
    # shared libs. Use path syntax - entries separated by colon.
    # Use _solaris/bin for Solaris and _ilnx21/bin for Linux
  7. Enable ColdFusion MX security and graphing support by establishing or appending to the following variables:
    • CF_COM_JVM_OPTIONS (Windows-only)
    • MEM_ARGS (append -Xms32m -Xmx256m -Xss64k -XX:MaxPermSize=128m to the existing MEM_ARGS line of the startup script)
    • JAVA_OPTIONS (append the CF_SECURITY_JVM_OPTIONS and CF_GRAPHING_JVM_OPTIONS variables to the existing JAVA_OPTIONS line of the startup script)

    For example:


    @rem Security options are only required if enabling sandbox security
    @rem You must append %CF_SECURITY_JVM_OPTIONS% to the existing JAVA_OPTIONS value.
    set\bea\weblogic700\server\lib\cacerts %CF_SECURITY_JVM_OPTIONS% %CF_COM_JVM_OPTIONS%
    @rem You must append the following to the existing MEM_ARGS value.
    @rem -Xms32m -Xmx256m -Xss64k -XX:MaxPermSize=128m


    # Security options are only required if enabling sandbox security
    # to the existing JAVA_OPTIONS value.
    # You must append the following to the MEM_ARGS variable coded
    # in the server startup file:
    # "-Xmx512m -XX:MaxPermSize=128m"

    Charting (1.3.x JVMs only) - 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.

  8. Save the startup script and restart the WebLogic Server.

Usage notes

This section describes issues related to running ColdFusion MX 7 on WebLogic 7 and 8.1.

Disabling RDS

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

To disable RDS:

  1. Disable the ColdFusion MX web module RDS Servlet, as described in Enabling and Using ColdFusion MX Features on Your J2EE Server.
  2. If your ColdFusion MX application context root is not /, disable the RDS web application by undeploying the RDS web application. If you deployed an EAR file, disable the RDS web application in the cfusion-ear/META-INF/application.xml file or by modifying the enterprise application deployment descriptor in the WebLogic Console.

If RDS is disabled, the Browse Server button does not work in the ColdFusion MX Administrator (for example, on the ColdFusion Mappings page).


This sections describes WebLogic-specific troubleshooting tips.

Failed to add HTML Header error or other problems when calling JSP pages

If your application uses the CFML GetPageContext function to include a JSP page, you must call the cfflush tag before calling the JSP page.

If you do not call the cfflush tag first, the ColdFusion output appears after the JSP output.

Enabling WebLogic jCOM support (Windows only)

ColdFusion MX includes jIintegra COM support, which you enable through the WebLogic Server startup script. Alternatively, you can use WebLogic jCOM.

Note: ColdFusion MX jIntegra COM support uses native mode, which disables COM objects that use DCOM. WebLogic jCOM supports DCOM or native mode, however, ColdFusion MX COM functionality requires native mode.

To use WebLogic jCOM as the ColdFusion MX Java to COM bridge:

  1. Omit the COM support step in "Editing the server startup script".
  2. Enable jCOM support by opening the WebLogic Administrator, navigating to domainname > Servers > servername > connections > JCOM, and selecting enable COM, enable Native Mode, and Prefetch ENums.
  3. Open a console window, go to wl_root\weblogic700\server\bin (the path to this file is different in WebLogic 8.1), and run the regjvmcmd tool to register the JVM for COM, as the following example shows:

    regjvmcmd /native servername

Undeploying ColdFusion MX 7

To undeploy ColdFusion MX:

  1. (Windows only) If you installed ODBC support, remove the ODBC Windows services by going to the cf_webapp_root\WEB_INF\cfusion\db\SequeLink Setup directory and running the RemoveSequeLink.bat file.
  2. Open the WebLogic Administrator.
  3. Open the WebLogic Administration Console (http://hostname:portnumber/console) and go to domainname > Deployments > Applications.
  4. Click the trash can to the right of the ColdFusion MX application.
  5. Click Yes.
  6. The WebLogic Administrator undeploys the web application.
  7. Perform steps 4 - 6 for the CFIDE (RDS) web application.
  8. Open the startup script for the WebLogic domain and remove ColdFusion MX-specific entries, as follows:

    • CF_WEB_INF
    • LD_LIBRARY_PATH (UNIX only, remove ${CF_SHARED_LIBS})
    • (Windows only) JINTEGRA_PATH (also remove JINTEGRA_PATH from PRE_PATH)
    • (Windows only) Remove jintegra.jar from PRE_CLASSPATH
    • Remove ColdFusion MX arguments from MEM_ARGS

    For more information, see Editing the server startup script.

  9. Stop and restart the WebLogic Server.
  10. Delete the cf_root directory.

Top Support Topics


More ColdFusion Topics

Choose a category to see more topics.

Request Support


Additional ColdFusion Resources


ColdFusion Downloads