Override default properties in cal.properties
Inside the bwbuild/.defaults directory, next to your configuration directory, you'll find a file named bwbuild/.defaults/cal.properties. cal.properties is referenced during the Bedework build and during deployment. You can override any of those properties by creating a bwbuild/myconfig/cal.properties in your configuration directory and editing in the overrides. cal.properties is divided into sections with different property prefixes.
Under Install Options, prune the org.bedework.install property
...
Multiple versions of each application type may be deployed, each configured differently. You can see how this works by comparing the stanza for the "Demo departmental public Web Client" to the stanza for the "Public Web Client".
...
Set the run time properties in cal.options.xml
bwbuild/myconfig/cal.options.xml contains run time properties and is divided into sections much like the cal.properties file. Most of the options are used to set field values in named classes so that the application will load the settings only once with a single call.
It is important to set the “system” properties for a new Bedework installation. These are found in the “syspars” section of the cal.options.xml file. A number of Most options can be left with the default values and some are not yet implemented. The three values it is particularly important to set (and their default settings) are:
...
systemid is used when generating uids for calendar entities. This name should relate to your organization for ease of identification. If you run multiple Bedework systems, use a different value for each. In addition, the systemid takes part in the creation and interpretation of calendar user addresses which appear in attendees. The part following “@” will probably be the domain to which imip messages are addressed (in some as yet undefined manner).
For example, your systemid might be "bedework@myorganization.com" or "bedework@myuniversity.edu".
Calendar user addresses take the form of a “mailto:” uri so that user “testuser01” on a system configured as above would have a calendar user address of
...