Building Bedework
Building and Deploying Bedework
The Bedework release is made of up a number of related parts which are built and deployed through the action of the bw (bw.bat on Windows) script found in the quickstart directory.Â
- To run bw, first cd to the quickstart directory.
The bw commands that immediately follow deploy the bedework core: the calendar server (including the caldav server) and the web clients. You'll need to reinvoke the bw command with different arguments to build and deploy the timezone server, the carddav server, the addressbook client, etc. Those commands are covered in the sections below.Â
Invoking the bw script without arguments displays very useful usage information.
To insure you have the latest bug fixes, it is a good idea to update the Bedework source prior to building. See Applying Fixes and Updates to Bedework.
Apart from the Bedework core, only the timezone server is critical to getting Bedework running. You'll need to rebuild the timezone server after you change <tzid> in bwbuild/myconfig/cal.options.xml.
Assuming your deploy configuration is mydeploy.properties in your home directory, run this command:
./bw -dc mydeploy.properties deploy
This command build a number of EAR and WAR files in <quickstart>/bedwork/dist/, then deploy them to <quickstart>/jboss-5.1.0.GA/server/default/bwdeploy
If you build with "clean", the build will remove all the previously built files before building.
./bw -dc mydeploy.properties clean.deploy <-- builds with clean
./bw -dc mydeploy.properties deploy <-- builds without clean
Build and Deploy the Bedework Timezone Server
As with the above examples, you need to specify and special deploy configuration.
./bw -dc mydeploy.properties -tzsvr
This command builds bw-tzsvr.ear and deploys it to jboss-5.1.0.GA/server/default/bwdeploy.
Build and Deploy the Bedework CardDAV Server
./bw -dc mydeploy.properties -carddav
This command builds bw-carddav.ear and deploys it to <qs>/jboss-5.1.0.GA/server/default/bwdeploy.
Deploy the Bedework Addressbook Client
./bw -dc mydeploy.properties -carddav deploy-addrbook
This command copies the files in <qs>bedework-carddav/clients/javascript/bwAddrbookClient to <qs>/jboss-5.1.0.GA/server/default/deploy/ROOT.war.
Deploy the Bedework Synch Server
./bw -dc mydeploy.properties -synch
This command builds the bw-synch.ear and deploys it to <qs>/jboss-5.1.0.GA/server/default/bwdeploy.
Hot Deploys
Currently hot deploys of the calendar server and clients always results in a broken system.
If you build and deploy Bedework while Bedework is running, JBoss <<should>> undeploy what was already running in favor of the newer packages. Often it works as advertises. Sometimes it doesn't. Stopping Bedework, re-deploying, and starting Bedework is safer.  If you succeed in "hot deploying", you might want to schedule a restart for the next convenient time.  Even successful hot deploys are likely to result in a larger memory footprint.
Bedework Enterprise Calendar Server, version 3.10