Home > Products > ColdFusion > Support > Clustering and Server Monitoring
ColdFusion Icon Macromedia ColdFusion Support Center - Clustering and Server Monitoring
Configuring distributed mode

Macromedia recommends that you use the following procedure to configure ColdFusion MX to run in distributed mode.

Note: If your web server computer currently has ColdFusion 5 installed, you must uninstall it.

To configure ColdFusion MX to run in distributed mode:

1 Install ColdFusion MX on the application server. During installation, select the built-in (stand-alone) web server option.
2 (Optional) If your web server computer is on a different network subnet than your application server computer, you must explicitly grant the web server computer permission to connect to the ColdFusion MX application server using the Java Naming and Directory Interface (JNDI). To do so, open cf_root\runtime\lib\ and add the web server IP address to the jrun.trusted.hosts= entry.
For example, if the IP address of your web server is, change the line as follows: jrun.trusted.hosts=
3 On the application server computer, restart ColdFusion MX.
4 (Optional) If you do not already have a Java Runtime Environment (JRE) on your web server computer, install one. Macromedia recommends Java 2 Runtime Environment, Standard Edition 1.3.1_03, available at
5 Copy the cf_root\runtime\lib\wsconfig.jar file from your application server computer to your web server computer.
You can copy this file to anywhere on the web server computer. You use its location (C:\temp in this example) in the next step of this procedure.
6 On the web server computer, run the connector installation command. Append -host IP_address to the end of the command, where IP_address is the IP address of the application server machine to which the web server will connect.
For example, if the IP address of your application server is, add -host to the web server connector installation command, as follows: C:\Progra~1\JavaSoft\JRE\1.3.1_03\bin\java -jar c:\temp\wsconfig.jar -ws IIS -site "0" -map .cfm,.cfc,.cfml,.jsp -v -host
A confirmation message displays upon successful completion.
Depending on your JRE, the JRE path might be different. The preceding example reflects the location of a manually installed JRE. The default path for the JRE that ColdFusion MX installs is cf_root\runtime\jre\bin\java.
For details on selecting the connector installation command that corresponds to your web server and operating system, see the Installing ColdFusion MX manual.
7 Copy the cf_root\wwwroot\CFIDE subdirectory from the application server to the web_root directory of the web server.
8 On the web server computer, verify that you can run the ColdFusion MX Administrator by entering http://web_IP/CFIDE/administrator/index.cfm in your web browser, where web_IP is the IP address of the web server machine.
9 In the ColdFusion MX Administrator, select Server Settings > Mappings to change the "/" ColdFusion mapping to reflect the new web_root directory (for example, C:\Inetpub\wwwroot\).
This physical directory must exist on both the web server computer and the application server computer; for example, if C:\Inetpub\wwwroot does not exist on the application server computer, you must create it.
10 On the application server computer, open the cf_root\runtime\servers\default\SERVER-INF\jrun.xml file and locate the following code:
<service class="jrun.servlet.http.WebService" name="WebService">
<attribute name="port">8500</attribute>
<attribute name="interface">*</attribute>
<attribute name="deactivated">false</attribute>
11 Change the value of the deactivated attribute from false to true .
The built-in web server is disabled on the application server computer.
12 Save your changes to the jrun.xml file.
13 Restart ColdFusion MX.
Note: All content that will be processed by ColdFusion MX—such as, files with .cfm or .cfc extensions—must reside on the application server in the same physical path as the web server. All other web content—such as files with .htm, .jpg, .gif, or .swf extensions—should reside on the web server computer. For simplicity, it is often easiest to mirror site content in an identical directory structure on both the web server and the application server.

Submit feedback about this tutorial.

To Table of Contents Back to Previous document