Latest Articles:
Committee Members:
Alert Email
Get a short email alert whenever a new entry is published.
Confidential, secure it's piece of cake to keep uptodate.
Upgrading OpenBD
You may be wondering how you can upgrade your own installation of OpenBD with the latest features and enhancements without losing all your existing settings. The engineers at OpenBD know only too well the hassles and stress that can come with software management and they strive to make this as easy and as painless as possible.
As an example, the OpenBD plugin technology makes adding new features to your installation by simply dropping a JAR file into the /WEB-INF/lib/ folder and restarting the engine. No complicated README files, no control panels to visit. To remove it, you simply remove the JAR file. All software distribution should be this easy.
Upgrading the core engine is no harder.
All you have to do is to replace all the JAR files located in your we bapp's /WEB-INF/lib/ folder with the JAR files from the latest release or nightly build.
- Locate your /../yourserver/WEB-INF/lib/ for your server/webapp
- Download OpenBD WAR file from the nightly build or new release from http://www.openbluedragon.org/download.cfm
- Unzip the downloaded WAR file into a temporary directory
- Delete all the files inside /../yourserver/WEB-INF/lib/ (backup just incase you want to go back)
- Copy the contents of the /openbdwar/WEB-INF/lib/ to /../yourserver/WEB-INF/lib/
- Restart
That is all there is to it. Remember if you have dropped any plugin's into your installation you will have to copy back over again (or don't delete those in the first place). In the vast majority of cases, you can simply get away with just replacing the /WEB-INF/lib/OpenBlueDragon.jar file. But it is generally safer to just replace all the JAR files, just incase.
Now you can start playing with all the latest and greatest features that OpenBD is pioneering for the CFML world.
Comments (5)
Yeah, I should probably include a diff -r with a warning about supporting JAR files being changed.
Awesome Joseph--one caution is that on occasion other JAR files in the WAR will get updated, and you can run into cases where updating OpenBlueDragon.jar alone won't be enough.
I use the following script to snatch and deploy the main OpenBlueDragon.jar from nightly builds:
http://svn.lamoree.com/svn/admin/coldfusion/openbluedragon-nightly-updater.shQuick addition--if your zip file handler doesn't recognize a WAR file as a zip file, just change the file extension to .zip.





I updated the script to support a minimal or (practically) complete upgrade. It also doesn't require downloading from openbluedragon.org every time, if the file exists locally.
http://svn.lamoree.com/svn/admin/coldfusion/openbluedragon-nightly-updater.sh