Something the docs never made clear, but the default "cfusion" instance is NOT supposed to be used in production. It's there as a mechanism to create/control your other instances/clusters.
Of course, that's not to say you can't use it, but that isn't it's purpose. (I had a discussion with a member of the QA team about this a while back). That being said, I never use the Enterprise Manager as it's full of bugs ... I configure mine the "old" way. Andy On 28/08/06, Douglas Knudsen <[EMAIL PROTECTED]> wrote: > Ok, finally upgraded to CF7 this weekend. Something I found out the hard > way, and apparently overlooked during the alpha and beta programmes! We > use JRun/CF clusters. I installed CF 7 and hit the new enterprise manager > tool there. Nice but > > 1) You can't include the default CF install in the cluster > > 2) after creating two seperate CF instances then creating a cluster of them, > you have to use wsconfig to wire the cluster up to your website. This > diabled the CFAdmin enterprise manager tool completely. I tried wiring the > default cfusion to another website in IIS, but still didn't work. > > ??? > > -- > Douglas Knudsen > http://www.cubicleman.com > this is my signature, like it? > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:251337 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
