...
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.
| Notetip | ||
|---|---|---|
| ||
Invoking the bw script without arguments displays very useful usage information. |
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 <timezoneUri> in bwbuild/myconfig/cal.options.xml.
Assuming your configuration mycompany is under bwbuild/myconfig in your home directory in the bwbuild subdirectory, run this command:
| Code Block |
|---|
./bw -bwc mycompanymyconfig clean.deploy.debug |
If you created a configuration area somewhere else in your filesystem, then
| Code Block |
|---|
./bw -bwchome configdir -bwc mycompanymyconfig deploy.debug |
To build with the jboss-mysql configurations shipped in the quickstart:
...
These commands build a number of EAR and WAR files in <qs><quickstart>/bedwork/dist/, then deploy them to <qs><quickstart>/jboss-5.1.0.GA/server/default/bwdeploy
| Note | |
|---|---|
| Tip | |
| false | 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 previously built files before building. |
...
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
Use -quickstart, -bwchome, -bwc as appropriate.
| Code Block |
|---|
./bw <config files args> -synch
|
This command builds the bw-synch.ear and deploys it to <qs>/jboss-5.1.0.GA/server/default/bwdeploy.
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.