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.
...
| Note | ||
|---|---|---|
| ||
If you build Bedework with "debug", Bedework will log more information. You may want to rebuild without it when you are in production. If you build with "clean", the build will remove all the built files before building. |
Build and Deploy the Bedework Timezone Server
As with the above examples, unless your configuration files are under <home>/bwbuild, specify where the configuration files come from (-quickstart/-bwchome) and unless you are using the "default" configuration, specify the name of your configuration folder (-bwc).
...
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
Use -quickstart, -bwchome, -bwc as appropriate.
...
This command builds bw-carddav.ear and deploys it to <qs>/jboss-5.1.0.GA/server/default/bwdeploy.
Deploy the Bedework Addressbook Client
Use -quickstart, -bwchome, -bwc as appropriate.
...
This command copies the files in <qs>bedework-carddav/clients/javascript/bwAddrbookClient to <qs>/jboss-5.1.0.GA/server/default/deploy/ROOT.war.
Build and Deploy webcache/urlbuilder
See this section.
Hot Deploys
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.