Chris posted this comment:"I'm new to Tomcat and BlueDragon. Are there instructions on how to upgrade to 1.1? I tried to replace the .war file and I lost all my cfAdmin settings. Any help is appreciated."
I looked around and found we don't really have a good upgrade outline, so I'll add a step-by-step to the FAQs soon. This is particularly important for people who are new to the world of Java web applications.
In the mean time, here's my response to Chris:@Chris--feel free to post to our mailing list as well--always lots of great help there. But I'll take this as a prompt to write up something on upgrades for the wiki, and I'll copy your question and my response to the mailing list to make sure people get the benefit of the discussion if they don't see this comment thread on the blog.
The WAR is an entire web application so you definitely don't want to replace everything in your web app when upgrading to the new version of OpenBD. As you discovered, you may lose some things in the process.
The real "guts" of OpenBD are all contained in the web app's WEB-INF directory, more specifically in the WEB-INF/lib directory, so while you can simply copy the new version's JAR files into your WEB-INF/lib directory, in general it's better to replace the whole WEB-INF directory with the new version's WEB-INF because there is functionality in other directories. For example the CFVIDEOPLAYER resources are in the WEB-INF/webresources directory, so if you only copied over the new JAR files you might miss out on some things.
All of the administrator settings are stored in a single file, namely WEB-INF/bluedragon/bluedragon.xml. For an upgrade you can just copy that file to somewhere outside your WEB-INF directory before doing the upgrade, then replace the old WEB-INF directory with the new one, and copy your bluedragon.xml file back into the WEB-INF directory. Note that since you're free to put other things in your WEB-INF directory manually (which some people do since it's not browsable), you may want to just take a backup of the entire WEB-INF directory (or to be totally safe the entire webapp) before replacing it with the new version.
Also note that if you're doing this while Tomcat is running, you may have to stop the individual webapp you're upgrading since some of the files may be in use.
Hope that helps! Sorry you lost your admin settings. Follow up on the mailing list if you have additional questions. Thanks!
-- Matthew Woodward [email protected] http://www.mattwoodward.com/blogPlease do not send me proprietary file formats such as Word, PowerPoint, etc. as attachments.
http://www.gnu.org/philosophy/no-word-attachments.html
smime.p7s
Description: S/MIME Cryptographic Signature
