Entries Tagged as 'Docs'

ColdFusion documentation goes live at http://helpx.adobe.com/coldfusion/home.html 

For the last two years, we have had a wiki-based model for ColdFusion documentation, with some of the revered ColdFusion experts in the industry editing the documentation and helping us keep it fresh and up-to-date. I am sure a large number of us have benefited from meaningful code samples and other documentation input that ColdFusion community experts shared. We would like to thank each of our ColdFusion community experts for their involvement and selfless commitment. We would like to specifically shout out a BIG THANK YOU to Adam Cameron, Aaron Neff, Charlie Arehart, and Raymond Camden.  Not to forget, Dave Ferguson, Carl Von Stetten, Adam Tuttle, Peter Freitag, Steve Blades, Matt Dyer, Kev McCabe, Sam Farmer, Andrew Myers, Matt Busche, Nicholas Tunney, Ryan Guill and Steven Neiland for the value add they have provided.

However, we have had several issues with the wiki service and implementation, causing us to look for a better solution. Owing to this, we are constrained to move away from the wiki model temporarily. Having said that, please rest assured that we are diligently working toward evaluating various options and we will partner with ColdFusion community experts to set the right collaborative authoring process.

In the meantime, we most certainly want to continue seeking the expertise of ColdFusion community experts in adding value to ColdFusion documentation. We request you to continue interacting with us through https://forums.adobe.com/community/coldfusion/documentation. We will now closely monitor the forums threads and will update the documentation accordingly. You could also leave your feedback on every help page using the yellow ticker that says “Was this Helpful?”.  

comment ticker

We will review each comment that is posted using this ticker. You can also directly reach us at the email alias chl-cf@adobe.comWe are eager to continue our collaboration with you and hence we are making several means available for you to continue providing your valuable input.

We look forward to your continued support as we navigate through the temporary changes. Thank you once again for being so supportive of us in keeping ~4000 pages of ColdFusion documentation updated and useful to the community.

You might want to set up ColdFusion in a distributed environment where ColdFusion is running on one machine and Web server is running on a different machine.

Following are the set of steps that have to be performed to achieve this (less error-prone):

This applies to both ColdFusion 10 and ColdFusion 11.

1) Have ColdFusion server installed in a machine.

2) Next thing is to download and install VC Runtime.

             - The version of VC Runtime that you have to install depends on the version of ColdFusion.

                Say, ColdFusion 11 needs VC Runtime 2012

                 (32-bit VC Runtime for 32-bit Web server and 64-bit VC Runtime for 64-bit Web server.

                  If you are not sure, you can install both)


                and ColdFusion 10 needs VC Runtime 2010


3) Copy the following contents from the machine where ColdFusion is running to the machine where Web server is running at the same location.







4) Open a Command prompt and run wsconfig tool

   C:\ColdFusion11>jre\bin\java -jar cfusion\runtime\lib\wsconfig.jar

    It will open a configuration window where you have to provide AppServer Host as the ColdFusion Server IP.

    Configure the connector.

Distributed environment is ready for use. Send requests to the Web server's URL with cfm files under web server root and same files under ColdFusion's Web root.

Web server would redirect these to ColdFusion, which is on some other machine.



During first week of December 2014, we had released Full installers for ColdFusion 11 with update 3 in-built. The build number was 11,0,3,292480.

There were two issues with the build that was released(Full Installers only).

1) After Enabling J2EE Session Variables server hangs on restart/start.

2)On Japanese OSes, installer doesn't recognize the Japanese locale.

If you have applied the update 3 through Hotfix, these 2 issues won't arise for you. And also, #1 is not applicable for J2EE deployments done as EAR or WAR.


These two issues are fixed and we have refreshed the Full installers this week. The build number is: 11,0,3,292866

If you have come across #1, either you can download and use the new installer or apply the workaround on your existing server itself.

The workaround is:

Open the xml file C:\ColdFusion11\cfusion\runtime\conf\context.xml (Change it as per your installation path)

and uncomment the tag: <Manager pathname="" />


    <Manager pathname="" />

Change it to:

    <Manager pathname="" />


If you have come across #2, you have to download and install.


There is a bit of confusion whether to use JRE or JDK with ColdFusion when you want to use an externally installed one.

This blog entry clarifies on whether to use jre7 or jdk7.

Note:Unless there is a specific reason, it is generally recommended to use the latest patched JRE/JDK of major Java version supported. As of 8th March 2013, for Java 1.7 the latest patched version is Java 1.7 Update 17.

The decision on whether JRE or JDK should be used is determined by whether JRE/JDK contains Server VM or not as ColdFusion runs only on top of Server VM. ColdFusion can't run on Client VM.

For all platforms, JRE that comes along with JDK contains server VM.

Even the public JRE that is available from Oracle contains Server VM for all platforms except for Windows 32-bit JRE.

So, from this it can be derived as follows:

1. For Win 64, Linux 32, Linux 64, Solaris 64-bit, Mac 64-bit you can use any of public JRE from Oracle or the JRE that is contained within JDK. We would recommend you to use Public JRE from Oracle. For Mac OS X there is an extra note below before which you want to conclude whether to use public JRE or JDK's JRE.

2. For Windows 32-bit, you can use the JRE that is contained within JDK


You can use the Win 32- Public JRE by customizing it to contain Server VM.

(To customize it you can copy <JDK_HOME>\jre\bin\server\ directory and its content to Public JRE (jre\bin\server ). It would at same directory level as client directory.

Note for Mac OS X Installations:

For Mac also public JRE as well JDK contained JRE contains server VM.
If you are using Web Services you would need one file from JDK(tools.jar). JRE doesn’t contain this file.
Since full version of ColdFusion 10 is shipped before Java 7  and Mac OS X used to ship JDK earlier which contains this file by default, we never shipped it along with ColdFusion installation.
With update 8 for Java 1.7 support on mac OS X, we are just copying this tools.jar from installed JDK to <ColdFusion_Home>\cfusion\lib\.
Going forward we will be shipping it along with ColdFusion installer for Mac as well but for ColdFusion 10 this file is not there.
So, consider using JRE or JDK depending on the need for Mac OS X
Just use JRE itself and only if needed you can copy tools.jar(it is same for all platforms) to <ColdFusion_Home>\cfusion\lib.
So if you are using ColdFusion 10 on Mac OS X with JRE 1.7 you might want to copy tools.jar to <ColdFusion_Home>\cfusion\lib\



Please find link to ColdFusion 10 release notes here.