Yep, Andrew, that's the way to view it. Of course, some never notice that (even if it were documented) and so just start using the cfusion instance as a "real instance", and then these things come back to bite them if they wanted a new "plain instance".
One other benefit of viewing the cfusion instances as just a "birther of new instances" (and not to be used for day-to-day processing) is that then you can stop the service (if using Windows) when not in use (and set the service to "manual"). That can save some precious memory, since the default behavior is for all instances to share the one default jvm.config (and yes, that can be changed by manual effort). Similarly, many don't know that the "admin" instance can also be stopped (and set to manual), as it's NOT used for CF Admin processing (which some suppose), but instead is like an appendix in the human body: it existed from the days before CF7 introduced the "Instance Manager" (in Enterprise Multiserver deployments, which is what we're talking about, to readers who may have missed that). Back then (and still now), you could instead use the JRun Admin to create new instances, clusters, etc. That's what the "admin" instance is about. So if you never use that JRun Admin, you can stop the "admin" instance. (Sadly, things have gotten a little muddier now that CFBuilder has introduced its own optionally available "admin" instance, which exists instead just for allowing CFBuilder to stop CF9 from within CFB itself. I do wish they'd called it something other than just another "admin" instance. But for now it does NOT create a windows service, so at least there's less chance of confusion there.) Finally, Andrew, while a lot about running multiple instances may not be as well-documented as it could be, I did cover the above and more in a preso I did (which is recorded): Getting Started with Multiple Instances in CF http://carehart.org/presentations/#gs_instances Hope that helps. /charlie > -----Original Message----- > From: [email protected] [mailto:[email protected]] On > Behalf Of Andrew > Sent: Thursday, April 21, 2011 2:09 AM > To: cfaussie > Subject: [cfaussie] Re: CF 9 Monitor Alerts still being sent even > though not enabled? > > So just for future reference. What I'm reading is telling me that > really rather than starting off using the default instance, I probably > should have created a new one and done everything in *there*, and left > the default instance as a template for creating future instances. Is > that correct? > > I'm sure it is well documented somewhere as Glen says...I guess I > didn't read that bit :) > -- You received this message because you are subscribed to the Google Groups "cfaussie" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en.
