Home / Products / ColdFusion / Support
J2EE Support

Installing and Deploying ColdFusion MX 6.1 on Other J2EE Application Servers

Macromedia ColdFusion MX 6.1 supports 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 or as a web application. Web application support lets you deploy the ColdFusion MX J2EE configuration on stand-alone J2EE web containers.

About this document

Installing, deploying, and configuring ColdFusion MX 6.1

Undeploying ColdFusion MX

About this document

This document provides basic instructions for deploying and configuring ColdFusion MX in the J2EE configuration on any J2EE 1.3 compliant application server. It refers to overview information in Installing and Using ColdFusion MX, which is available on LiveDocs (English and Japanese only). Installing and Using ColdFusion MX also includes important information on configuring and uninstalling ColdFusion MX 6.1.

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 application server and ColdFusion directories:

  • cf_root - The directory into which you deployed ColdFusion MX; for example, C:\jakarta-tomcat-4.1.18\webapps\cfusion.
  • cf_context_root - The web server context root into which you deployed ColdFusion MX; for example, cfusion.
  • java_home - The root directory of your Java 2 software development kit (J2SDK); for example, C:\j2sdk1.4.1.
  • app_server_root - The directory that contains the application server; for example, C:\jakarta-tomcat-4.1.18.

Installing, deploying, and configuring ColdFusion MX 6.1

Because you store ColdFusion pages (CFM pages) under the ColdFusion MX context root, ColdFusion MX must run out of an open directory structure. However, not all J2EE application server deployment methods result in a working open directory structure. (For example, in JRun 4, deploying a compressed WAR file results in an expanded directory under SERVER-INF/temp; in BEA WebLogic 7, deploying in production mode results in a proprietary directory structure that you cannot use to deploy CFM pages.)

Most J2EE application servers either let you deploy an open directory in WAR or EAR format (that is, the directory structure contains j2eeapp/META-INF/application.xml and webapp/WEB-INF/web.xml files) or deploy by expanding the EAR or WAR file into a working open directory structure. For example, Tomcat autodeploy results in an open directory structure under the webapps directory.

To install ColdFusion MX 6.1 using EAR or WAR files:

  1. Run the ColdFusion MX 6.1 Installation Wizard after downloading the platform-specific installer:
    • Windows - coldfusion-61-win.exe
    • Linux - coldfusion-61-lin.bin
    • Solaris - coldfusion-61-sol.bin
    • Other platforms - coldfusion-61-other.jar (run with java_home/bin/java -jar coldfusion-61-other.jar -i console)

    These installers are available on the Macromedia website.

  2. Answer the questions. When prompted, do the following:
    1. Select Developer Edition or upgrade (if you are upgrading an existing ColdFusion MX installation).
    2. Select J2EE configuration and either EAR or WAR file, depending on your J2EE server's application deployment method.
    3. Specify the installation directory in which to place the EAR or WAR files. You can use a temporary directory as the installation directory.
    4. If you are deploying using an EAR file, specify the context root. Macromedia recommends the context root /cfusion, but you can deploy cfusion.war at any context root, including /, as supported by your application server.
    5. Specify a password for use with the ColdFusion MX Administrator.

      The Installation Wizard places the cfusion.ear or cfusion.war and rds.war files in the installation directory.

  3. Do the following, depending on whether you are deploying ColdFusion MX as an EAR file or as WAR files.
    • If you are deploying as an EAR file, follow your application server's configuration procedures to deploy the cfusion.ear file that you created in step 1. This deploys both the Macromedia ColdFusion MX and the CFMX RDS Applications. Depending on your application server, you might have to expand the archives and deploy the expanded directory structure.
    • If you are deploying using WAR files, deploy the cfusion.war web application. Macromedia recommends the context root /cfusion, but you can deploy cfusion.war at any context root, including /, as supported by your application server.

      To support RDS, deploy the rds.war web application at the /CFIDE context root. If you install cfusion.war at /, you do not need the RDS web application.

  4. Restart your application server, if necessary.
  5. Stop your application server.
  6. The ColdFusion MX 6.1 tools.jar file is compatible with a 1.4.2 level JVM. If your J2EE server uses a different JDK version, rename your cf_root/WEB-INF/cfusion/lib/tools.jar file to something else (for example, tools.old).
  7. (Windows, Linux, and Solaris) Add ColdFusion MX binary file directories to the JVM argument for the native library path (java.library.path). These directories are as follows:

    ColdFusion MX binaries - cf_root/WEB_INF/cfusion/lib

    Verity binaries - cf_root/WEB_INF/cfusion/lib/platform/bin (where platform is _nti40, _ilnx21, or _solaris)

    jIntegra binaries (Windows only, COM support) - cf_root/WEB-INF/cfusion/jintegra/bin and cf_root/WEB-INF/cfusion/jintegra/bin/international

    Each J2EE application server has a different method of defining JVM arguments. Depending on your server, you can update variables in a batch file or shell script, define arguments in an administrative interface, modify the java.library.path JVM argument directly, or modify the system path directly.

  8. Depending on your operating system, you might have to add the following to the java.args JVM argument:

    COM (Windows only) Add the following arguments:


    CORBA (optional) Copy vbjorb.jar to WEB-INF/cfusion/lib and define the following argument:


    Charting Define the following argument, or ensure that WEB-INF/cfusion/lib is in the JVM's classpath:


    Charting (UNIX only) Define the following argument:"

    Note: For JDK 1.4.1 and later versions, specify instead of

    Security In addition to enabling sandbox security in the ColdFusion MX Administrator, the application server must be running a security manager (java.lang.SecurityManager), and you must define the following JVM arguments:"cf_root/WEB-INF/cfusion/lib/coldfusion.policy""cf_root/WEB-INF/cfusion/lib/neo_jaas.policy"

    Additionally certain application servers require that you disable server-specific policy-file permissions in order to enable the ColdFusion security manager.

  9. If you use RDS, on some application servers you must follow the procedure in Setting the crossContext attribute to enable RDS.
  10. Restart the J2EE Application server and monitor startup messages to ensure that all configurations were applied successfully.
  11. Start the ColdFusion MX Administrator by using a URL of the form http://hostname:portnumber/cf_context_root/CFIDE/administrator/index.cfm, as follows:
    • hostname - The machine name, IP address, localhost, or
    • portnumber - The port number of the web server.
  12. The Administrator runs the Configuration and Settings Migration Wizard. Select whether to install the ODBC database drivers and the ColdFusion example programs (including the data sources and code used by Getting Started Building ColdFusion MX Applications).
  13. Code and test ColdFusion MX (CFM) pages. Store these pages in the cfusion web application root directory. For example, to display a CFM file located at /Jakarta-4.1.18/webapps/cfusion/eisapp/index.cfm, you could specify the URL as

Setting the crossContext attribute to enable RDS

To use RDS, you might have to set the crossContext attribute to True for the CFIDE web application by editing the server.xml file. The following procedure shows the change you must make for Apache Tomcat. Other servers might have similar requirements.

  1. Open the app_server_root/conf/server.xml file in a text editor.
  2. Add the following line under the Engine element:
    <Context className="org.apache.catalina.core.StandardContext" 
    charsetMapperClass="org.apache.catalina.util.CharsetMapper" cookies="true" 
    crossContext="true" debug="0" displayName="CFMX RDS Application" 
    path="/CFIDE" privileged="false" reloadable="false" swallowOutput="false" 
    useNaming="true" wrapperClass="org.apache.catalina.core.StandardWrapper">
  3. Save and close the server.xml file.

Undeploying ColdFusion MX

To undeploy ColdFusion MX in the J2EE configuration, you use application server-specific undeploy tools and methods.

To undeploy ColdFusion MX in the J2EE configuration:

  1. Remove all ColdFusion MX specifications from the java.args and java.library.path JVM arguments used by your application server.
  2. (Windows only) If you installed ODBC support, remove the ODBC Windows services by navigating to the cf_root\WEB_INF\cfusion\db\SequeLink Setup directory and executing the RemoveSequeLink.bat file.
  3. If necessary, copy and save CFM pages from the ColdFusion MX web application root.
  4. Undeploy the ColdFusion MX web application, using application server-specific undeploy functionality. In JRun 4, you undeploy by deleting the jrun_root/server/servername/cfusion-ear directory.
  5. If necessary, restart the application server.