Yes, you are true, I could copy those XML config files. But, even this is a
manual process.
In my previous client.. they had a way to automagically transfer these
settings among the instances... so that when we change one CF instance's
CFADMIN settings... it would get copied.. from this instance
sounds dangerous to me in a way, but yeah you could just setup replication
via manual script or via the OS. Something as big as Websphere might have
this functionality built in for handling large soft-clusters. Is
sift-clusters a term? if no prior art there is now! :)
DK
On Thu, Oct 23, 2008
On Thu, Oct 23, 2008 at 8:57 AM, Arun Nallan [EMAIL PROTECTED] wrote:
Yes, you are true, I could copy those XML config files. But, even this is a
manual process.
There are a large number of potential solutions for automating this.
In my previous client.. they had a way to automagically
On Tue, Oct 21, 2008 at 1:19 PM, Arun Nallan [EMAIL PROTECTED] wrote:
Does anyone know how or have experience in getting the replication setup
(admin settings) from among the CF instances of a cluster? I understand if
that is not compatible for Windows environment, even if it works in a UNIX
We are considering the clustering options for load balancing/ failover in a
IIS/ JRun coldfusion environment.
That being said, would the J2EE clustering (or the ColdFusion Enterprise
Manager via CF Admin) be the best option to go for, or what would be my
other options available. We are going to
The J2EE clustering in the CF Admin is just a tool to manage the underlying
J2EE server, which by default is JRun. Unless you have a business reason to
run CF on something else, I usually would just stick to JRun. An argument
could be made that you get speed improvements from other J2EE
What's your server platform, Windows or Linux? I had a really bad experience
(ok, maybe not bad but extremely trying) with clustering CF on JRun on
Redhat Linux. Granted, this was CFMX 6 (and whatever JVM version) five years
ago so things should have improved by now, but we had to throw an
Thanks for your email.
Yes, I agree with you. Each situation is different. FYI.. We have a setup of
CF running on JRun... and IIS as our webserver. We have proxy connection
enabled on JRUN for each CF instance for communication with IIS. So, we have
turned off the internal JWS for our purposes
I've set this up before. Its a software approach to cluster/balancing.
JRun, the software, decides on where to route requests and such.
Failover was not very successful in my experience. If a instance failed,
users were still stuck pointing to it instead of getting re-directed. I
suspect
