Entries Tagged as “Connector”
Adobe ColdFusion 10 | Adobe ColdFusion 11 | Connector
Important update: Note that ColdFusion 10 and 11 have been updated to support Windows 10, a couple months after this blog post was first written. Consider applying that update rather than this manual configuration.
With Windows 10 out, there is a problem that most of the ColdFusion customers will face, configuring connectors for IIS 10. Wsconfig, the connector configuration tool, only supports till IIS 8.x. While the ColdFusion team is working on this issue and will try to provide the fix for it as soon as possible, there is already a KB article which can be referred for configuring the connectors manually. Although the article was originally written for CF10, it can be used for CF11 also. After following all the steps in the article, you need to do one more thing. Add index.cfm as default document for your website in IIS.
This solution is only recommended for development environments as thorough testing of the connectors with IIS 10 is still going on. So for production machines, you should wait for the actual release from Adobe.
Adobe ColdFusion 10 | Adobe ColdFusion 11 | Connector
Sometimes there is a requirement to know the realtime load on a ColdFusion Server. One way to get this information is through cfstat which displays the relevant information at CF server/Tomcat level. One more way to get this information is through Status worker which displays the information at Webserver/Connector level.
A status worker is a special type of worker which does not communicate with Tomcat. Instead it gathers configuration and load details from other workers and displays it. It can also be used to change some details dynamically. Configuring a status worker is pretty straightforward. After the connectors are successfully configured with wsconfig tool, we need to change worker.properties and uriworkermap.properties to enable status worker. In worker.properties, add a new worker:
In uriworkermap.properties, add a uri mapping to this worker:
/cf/status = cfstatus
Restart the webserver.
Now whenever a request comes at http://WebserverIP:Port/cf/status, it will be redirected to this status worker which will display the relevant information based on the query parameters in the request. Some of the common parameters are:
- mime: Specifies the output format. If someone is running a script to get status information and parse it, the value should be xml. If its only used for display purpose, then it should be html.
- cmd: Specifies what action you want to perform. list displays details of all the configured workers. show displays information of a specific worker.
- w: Specifies name of the worker. It should be used along with cmd=show.
- sw: Specifies name of subworker if w referred to a lbworker.
- opt: Specifies which information should not be displayed. It is bitmask of desirable options. The allowed values are:
0x0001: hide members of lb workers
0x0002: hide URL maps
0x0004: hide the legend (Works only with html)
0x0008: hide load balancer workers
0x0010: hide ajp workers
0x0020: only allow read_only actions for a read/write status worker.
0x0040: hide load balancer configuration (Works only with html)
0x0080: hide load balancer status summary (Works only with html)
0x0100: hide configuration for ajp and load balancer member workers (Works only with html)
Administrator | ColdFusion | ColdFusion 11 | Connector | creating a website | customers | Docs | General | productivity | Tomcat | web application | web application development
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.
Adobe ColdFusion | Adobe ColdFusion 10 | Adobe ColdFusion 11 | Connector
I have seen many customers getting confused in custom error pages and
onMissingTemplate feature in ColdFusion and IIS. So I thought of
blogging it for the use of larger audience. Before starting let me setup
Customer Eddard(name assumed) is using ColdFusion10(valid for ColdFusion11 too) configured with IIS. He has setup onMissingTemplate in Administrator of ColdFusion. Now Eddard expects ColdFusion to run this error page(mentioned in onMissinTemplate), let's call it 404.cfm, whenever user hits a page which doesn't exist. But suprisingly his browser is not showing the contents of 404.cfm and instead showing IIS 404 error page which is a static file(html file). After a lot of struggle he finds another confusing behavior that when he access the non existing page from machine where server is running(localhost) then his 404.cfm is getting executed. It's clear from the behavior that there is somehting in IIS which is handling this behavior.
You guys must be thinking what is the right approach then. I will give
three scenarios and you can chose any one depending upon your
1. Custom error page - Simply use custom error page and do not use onMissingTemplate. You have to opt for "Custom error pages" in "IIS->site->error pages->edit feature settings". And give a 404.cfm url against required status code like 404 in "IIS->site->error pages". This cfm will be executed whenever that error has been hit like a user requested for non existing page. The page will not be executed twice since you have not mentioned anything in onMissingtemplate.
Administrator | Adobe ColdFusion 10 | ColdFusion | Connector | General | Hotfix
We have seen that some of you have not been able to get the web server connector working after applying update 14.
We did our investigation and following is our finding.
The connector binaries of ColdFusion 10 update 14 are built on top of VC++ runtime 2012 update 4.
Installation of VC++ runtime requires admin privileges. If the ColdFusion service runs as administrator or system account, the update itself install the VC++ runtime as this account would have installation privileges.
If your ColdFusion service account is not running as administrator or system account, applying the hotfix from administrator can't install VC++ runtime and you will get "500 internal server error" after configuring the connector.
In this case, you need to manually install VC++ runtime 2012 32-bit and/or 64 bit depending on whether Web server is 32-bit or 64-bit.
You can download VC++ runtime here at:
When you install hotfix manually, administrator privileges are enforced and so the installation of VC++ runtime is automatically taken care by the updater.