Yes, this helps a lot. Thanks for the detailed response. Unfortunately, it doesn't appear that this feature will be of much use to us. When we install apps in corporate environments, we're usually provided with servers and perform the installations ourselves. Besides those apps, most of the stuff we write has to run in shared hosting environments (though they might not necessarily be deployed to shared hosting environments). We simply don't see a lot in between.
Ben Rogers http://www.c4.net v.508.240.0051 f.508.240.0057 > -----Original Message----- > From: Dave Carabetta [mailto:[EMAIL PROTECTED] > Sent: Tuesday, February 08, 2005 11:23 AM > To: CF-Talk > Subject: Re: Sourceless deployment in BlueDragon (was: CFMX 7 is released) > > On Tue, 8 Feb 2005 10:54:25 -0500, Ben Rogers <[EMAIL PROTECTED]> wrote: > > > Regarding serial numbers, it's your choice as to whether or not you > > > include it when you compile the application. If you're selling a > > > product to another company/customer, you would not include the serial > > > number, as they would need their own serial number for their own > > > servers. However, if you're simply moving the EAR/WAR file from one > > > server in your setup to another, and you already have the serial > > > number needed on the target server (the server you will be deploying > > > the EAR/WAR file on), then you can plug it in up front so that you > > > don't have to include the CF Administrator (or use the Admin API CFCs > > > to programmatically set it). > > > > This all makes sense, except, why would the customer, having purchased a > > full copy of ColdFusion Enterpirse, want a crippled installation of > > ColdFusion Enterprise (i.e. sans the ColdFusion Administrator)? > > OK, here's a use case. One of the reasons that ColdFusion hasn't been > adopted at some shops is that they run a pure J2EE environment. > ColdFusion MX's past deployment experience has not followed this > pattern, even though it is a valid J2EE application. You used to have > to buy the CF server, install it separately into a J2EE instance, and > then deploy your CFML code separately on top of that. That was an > awkward experience for J2EE sys admins who wanted to have one neat > EAR/WAR file that they could drop in and deploy which contained all of > CFMX plus the CFML application. Now, to you and me as CF-ers, it's > probably not that big of a deal because it's what we're used to, but > for these pure J2EE shops, it was a hassle they didn't want to deal > with so they stuck with technologies such as JSP. For a real-world > example of this, I believe Mario Ciliotta who just posted to the list > yesterday that his sys admins at Credit Suisse First Boston only > wanted a EAR/WAR file to deploy if they were going to use CFMX 7. > > Keeping that use case in mind, CFMX 7 has the EAR/WAR packaging > feature to satisfy this awkwardness for pure J2EE shops. If you think > about it, in these big shops, they are theoretically not going to need > to access the CFMX Administrator after the initial deployment, and any > tweaking that does need to be done can now be done programmatically > via the Admin API included (see LiveDocs for more on this). > > > > > > As for the license, it only applies to the server to which the EAR/WAR > > > file is being deployed to -- it has nothing to do with your files. So > > > if the server you're moving to is a 2-CPU server, you'll need to > > > purchase a CFMX Enterprise license for a 2-CPU server to be in license > > > compliance. Further, since the license is for the physical server (and > > > the CPU licensing is for each *physical* CPU, not virtual CPUs, by the > > > way), you can deploy any number of instances/applications on that > > > server; you are not restricted in any way on that front. > > > > I'm still having trouble seeing a use for EAR/WAR file deployment. Can > you > > package your application up as an EAR/WAR file without ColdFusion (i.e > for > > deployment on a running instance of ColdFusion)? Or, is ColdFusion > always > > included in EAR/WAR file? > > No, and this is really more because of the nature of how EAR/WAR files > are used in the J2EE world. They are intended to be full standalone > applications that you can literally just drop in and deploy without > dependencies. If you already have CF installed into the instance > you're deploying to, the combination of WinZip and sourceless > deployment via the included cfcompile utility achieves the same goal. > > Hope this helps? > > Regards, > Dave. > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:193646 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
