Usually, when I add a new website under IIS, I create a new instance in CF9, and use WSConfig to map the instance to the website. Its a straight-forward process.
CF9 wsconfig
With CF10, I can’t seem to find any documentation on how to do that. Running WSConfig no longer has an option with a drop-down of instances, so I was left scratching my head.
CF10 wsconfig
Adobe’s notes @ http://help.adobe.com/en_US/ColdFusion/10.0/Installing/WSc3ff6d0ea77859461172e0811cdec18a15-7ffb.html have no mention of instances.
After much digging, I figured out that you cannot use the Web Server Configuration Tool in the Windows menu, rather you have to go to \*cf dir*\*instance dir*\runtime\bin, and run wsconfig.exe and select the right website from the drop down.
Essentially, every time you create a new instance, you have a new wsconfig.exe that you will use to connect that instance to a website. The one in the Windows menu is only for the cfusion instance, which makes it useless if you are used to a more advanced setup, nor is this documented very well.
Why in the world, when you had the flexibility before, was that taken away and not documented well? Adobe!!!
Comments on: "ColdFusion 10 – Windows IIS & WSConfig Woes" (4)
People still use IIS?
I guess the issue would be independent of IIS. It would exists for Apache as well. I know, i know… my ideal would be NGINX->Tomcat->CF. Right now its NGINX->IIS->Tomcat->CF.
Yeah it is really weird, I logged an E/R so that the one tool could easily manage all instances, it is not like they can’t all the information is available in the xml files that they use.
Make each instance into a cluster. Yes, a cluster with just one instance. Then it will show in the dropdown menu.