I've been working a bit with the CF10 beta on one of my dev boxes and have a couple questions regarding the new server update capability (which is very nice, BTW):
1. Most of the time this box sits on a corporate network behind a proxy; will the server update capability function? And if I need to tweak anything to get it to work, what might that be?
2. Our production boxes are configured in such a way that they will not be able to initiate a connection to the Adobe update servers; any thoughts on how updating will work? I see the ability in the CFadmin server update settings page to specify an alternate location for server updates. Can anyone provide guidance on how/if that might be used to work around either 1, above, or this scenario?
3. What's the process for updating the Tomcat installation that is put in place when ACF10 is installed? Will the server update function provide a means of updating that portion of the stack (given that at 7.0.23, it is now 3 minor updates behind the latest official version)?
In my mind this works tho maybe there is an official other way:
1 Download hotfix on CF10 dev system for later installation. I guess one is
going to trial it before production anyway.
2 Move files from dev over to prod <cf_home>/hf-updates/ area
3 At command prompt:
java -jar <jar-file-name>
Follow the on screen instructions
The CF10 help page is useful in this matter:
Thanks for the response. That does cover the process of installing manually, and that's almost certainly the approach we will end up using for the production servers. My question regarding updating from behind a proxy still stands, however (recognizing that the manual download/install process may be the only viable approach).
I'm even more curious about the process for updating Tomcat, given Andrew Scott's recent blog post indicating that this is not a stock Tomcat install but rather a custom Adobe Tomcat and further that ACF10 isn't necessarily supported on stock Tomcat (both of which are, at least on the surface, potentially troubling). More here: http://www.andyscott.id.au/2012/3/8/ColdFusion-10-installed-on-top-of- Tomcat-may-not-be-supported
Can someone from the Adobe team weigh in on some of these questions regarding the update framework and updating of the other portions of the stack?
This blog in part says tomcat will be patched by CF10 updater:
@rupesh: Thanks for the quick response.
What's the timeline for updating Tomcat, given that
- the official Tomcat project is now four point-releases ahead of that at 7.0.27,
- 7.0.23 is almost 6 months old, and
- your blog post linked above indicates updates will occur "soon" after Tomcat comes out with critical fixes?
While you await his reply, I’ll point out that I’ve seen other discussions where he and others have said that they do plan to use the new automated hotfix feature of CF10 to roll out even updates to Tomcat. I wouldn’t be surprised if they were in feature lock down for weeks or longer prior to the final release today, and perhaps we may see such an update to Tomcat (if indeed there’s a substantial security concern) soon. But I’ll let Adobe clarify if they would be any more specific. Hope that’s helpful.
Oh, and I meant to add to my last note in this thread: if anyone ever wonders what version of Tomcat CF is running, it’s displayed in the CF Admin, on the System Information page (click the “I” icon in the top right corner). Note that it is NOT displayed on the “settings summary” page (whose link is on the left in the CF Admin). The two pages often feel like they’re nearly the same, but there is much that does not overlap.