ColdFusion Support Center

Deploying ColdFusion MX 7 on J2EE Application Servers

One of the main advantages of ColdFusion MX 7 is that you can install it as an integrated server (the server configuration) or deploy it as a Java application on a standards-based Java 2 Enterprise Edition (J2EE) application server (the multiserver and J2EE configurations). In addition to greater flexibility, this lets your ColdFusion applications leverage features of the J2EE architecture, such as support for multiple application instances and multiple-instance clustering.

This document describes the ColdFusion MX J2EE configuration and provides links to deployment instructions for a variety of J2EE application servers.

Note: If you are using ColdFusion MX 6.1, see the version 6.1 instructions.


You can deploy ColdFusion MX 7 in the J2EE configuration using a third-party J2EE application server. When you select the J2EE configuration, the Install Wizard creates a web application archive (WAR) or enterprise application archive (EAR) file, which you then deploy using the tools provided by your chosen application server.

This document provides background information to help you understand the concepts and components of the ColdFusion MX J2EE configuration. It also contains links to instructions that you can use to install and deploy ColdFusion MX 7 on a variety of J2EE application servers. The instructions also include functionality limitations as well as support status. Not all J2EE application servers are supported for production use; not all platforms are supported.

To learn more about the ColdFusion MX J2EE configuration, see the ColdFusion MX Support Center. To learn more about ColdFusion MX, see the product information and FAQ and visit the Macromedia Development Centers.

J2EE application servers and support status

Because all J2EE-compliant application servers support EAR and/or WAR deployment, you should be able deploy ColdFusion MX in the J2EE configuration on any J2EE-certified application server. However, due to configuration and platform nuances, official support is not available for all J2EE application servers.

Supported J2EE application servers

The following list summarizes the application servers supported by the ColdFusion MX J2EE configuration:

For detailed information on system requirements for each supported application server, see the ColdFusion MX System Requirements page.

Unsupported application servers for the archive install

As mentioned previously, although you can deploy the ColdFusion MX 2EE configuration on any J2EE-compliant application server, not all are supported for production use. Therefore, the following instructions are provided for use in development or evaluation environments only.

Choosing EAR or WAR deployment

If your computer is already running a J2EE application server, the Install Wizard creates an EAR file or WAR files, which you deploy using application-server-specific tools.

The ColdFusion MX J2EE configuration must run from an expanded directory structure. The J2EE application servers have different requirements for deployment and an expanded directory structure, as follows:

Deploying a compressed archive to working directory - On some J2EE application servers (such as IBM WebSphere), the deployment process expands the EAR or WAR file into a working directory and, from that point forward, the expanded directory is considered to be the application. For these application servers, you deploy the compressed EAR or WAR file and work in the resulting directory structure.

Deploying an expanded archive as working directory - On other application servers (such as JRun 4 and BEA WebLogic), the deployment process expands the EAR or WAR file into a temporary directory and (conceptually) the compressed EAR or WAR file is still considered to be the application. For these application servers, you must expand the EAR or WAR file manually and then deploy the expanded directory structure, which becomes your working directory.

The server-specific instructions tell you whether to deploy the compressed archive or an expanded archive.

Context root

Because the J2EE environment supports multiple, isolated web applications running in a server instance, each J2EE web application running in a server has a unique base URL, called a context root (or context path). The J2EE application server uses the initial portion of the URL (that is, the portion immediately following http://hostname) to determine which web application services an incoming request. For example, if you are running ColdFusion MX with a context root of cfmx, you display the ColdFusion MX Administrator using the URL http://hostname/cfmx/CFIDE/administrator/index.cfm.

Most J2EE application servers allow one application in each server instance to use / (forward slash) for the context root. The Remote Development Services (RDS) web application is not required if you use a context root of /.

When you deploy the ColdFusion MX EAR file, it uses the context root that you specified when you ran the Install Wizard; the Install Wizard copied your specification to the context-root element of the META-INF/application.xml file. When you deploy ColdFusion MX as a WAR file, you use application-server-specific functionality to define the context root.

Platforms and functionality differences

When you deploy the ColdFusion MX archive file, you can run basic ColdFusion pages and start the ColdFusion MX Administrator. However, certain types of ColdFusion MX functionality are performed through platform-specific binary files (that is, compiled C++ files, not Java bytecode), which are provided for Windows, Solaris, and Linux. In addition, some of these features require server-specific environment settings. The following table lists platform-specific functionality and the steps you must perform to enable their use:

Feature Customization
COM (Windows only)

Add jIntegra binary directories to the JVM's native library path. The directories are as follows:

  • cf_root/WEB-INF/cfusion/jintegra/bin
  • cf_root/WEB-INF/cfusion/jintegra/bin/international
C++ CFX cfreport tag (Crystal Reports only, Windows only)

Add cf_root/WEB-INF/cfusion/lib to the JVM's classpath.

If your J2EE server runs on an operating system other than Windows, Solaris, or Linux, use coldfusion-70-other.jar, the all-Java installer, to generate EAR or WAR files that do not include platform-specific binary files. You can still run ColdFusion MX, but the functionality in the previous table is unavailable.

In addition to platform-specific customization, you might have to perform the following additional customization steps:

Feature Customization
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
Charting (UNIX only)

Add the following JVM argument:


After you enable sandbox security in the ColdFusion MX Administrator, you must also define the following JVM arguments (on a single line):"cf_webapp_root/WEB-INF/cfusion/lib/coldfusion.policy""cf_webapp_root/WEB-INF/cfusion/lib/neo_jaas.policy"

To enable sandbox security, the application server must be running a security manager (that is, an implementation of java.lang.SecurityManager).

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

Top Support Topics


More ColdFusion Topics

Choose a category to see more topics.

Request Support


Additional ColdFusion Resources


ColdFusion Downloads