Tanguy and any others who might be using CFML on WebLogic--

Take a look at BlueDragon, BEA WebLogic Edition:

http://www.bea.com/framework.jsp?CNT=index.htm&FP=/content/products/weblogic
/bluedragon/

You should find that both the installation difficulty and size of required
CFML app server resources is significantly less when deploying BlueDragon
than you're finding them to be when deploying CFMX.

Josh 

-----Original Message-----
From: Tanguy Rademakers [mailto:[EMAIL PROTECTED] 
Sent: Monday, August 07, 2006 11:59 AM
To: CF-Talk
Subject: Re: what if the next CF...

>You do realize this is possible now, right? If you install CFMX 7 using 
>the Multiserver installation option on, say, your laptop, you can write 
>your application, create an EAR/WAR which contains the entire CF 
>runtime, and give it to some J2EE app server admin and tell him to 
>deploy it. Of course, it's not free - you have to either include your 
>own license information (thus invalidating it on your own machine, 
>legally) or have that information added post-deployment.

We use the J2EE version of MX (equivalent to "Multiserver installation"?),
deploying in Weblogic, and i've got to say that, in my experience, it's a
little more hairy than that:

1) In Weblogic, CF has to be deployed as an exploded war / ear (as i recall,
this has something to do with needing read / write access to the
license.properties file). This means that the ear or war has to be uploaded
to each machine in the cluster, exploded, deployed from the weblogic
console, and then the license information needs to be updated separately in
each instance using the cf admin (although i think there are "cluster
friendly" serial numbers available). Contrast this with a "normal" java web
app, where you upload the war/jar/rar/ear using a web form on the weblogic
console and it is automatically deployed on all of the machines in the
cluster.

2) You have to deploy a full cf instance every time. Even if your app is a
simple five pager that doesn't need scheduled tasks,web services, or
whatever - you still need to deploy hundreds of megabytes of code, which
does affect memory usage and startup time for you app server. 

These are just our experiences in our environment, not enough to draw any
binding conclusions about the state of the product. But, here, small apps
that would be a natural for CF's feature set keep losing out to struts based
apps packaged as wars because the perception is that they are "easier to
setup and manage"... :(

/t



~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
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:249240
Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm
Unsubscribe: 
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4

Reply via email to