Do I need to rebuild?
Bedework comes with a full set of demonstration web applications. If you wish to create a pruned version of the system - or add more calendar suites - you will need to rebuild with your own configuration. Note that the build configuration only affects what is built. The run-time configuration of the system is all set by the files described in Configuring Bedework
Copy the deployment configurations properties file
The final configuration of deployed applications is set by the deployment properties file bedework/config/deploy.properties. Copy the file to some other location.
Edit the file to set the values needed for your deployment. You may find you don't need to change much. At the start of the file are properties defining the input, and intermediate directory and the deployment directory. you may want to change the final property if you want to deploy the resulting ears yourself.
The following are the kind of change you may need to make.
Datasource names
You probably shouldn't change these but if necessary they are specified with the following
org.bedework.global.jboss.db.datasource.jndiname=/CalendarDS
org.bedework.global.jboss.carddb.datasource.jndiname=/CardDS
org.bedework.global.jboss.synch.datasource.jndiname=/SynchDS
org.bedework.global.jboss.eventreg.datasource.jndiname=/EventregDS
Transport Guarantees
These are what determine if connections are made over SSL or in plain-text. The two allowable values are NONE and CONFIDENTIAL. If you run jboss behind a web server such as apache - and if that web server handles ssl for you - then you don't need to modify this setting. The global default of NONE is fine. Otherwise you need to set it to CONFIDENTIAL for those applications that require SSL. You will also need to install certificates in jboss.
Virtual hosts
If you need to set the virtual hosts for the applications you can set them all to the same value(s) with the property
org.bedework.global.virtual-hosts=host1.example.com,host2.example.com
or change them for one ear only e.g. for ear "bwcal"
org.bedework.app.bwcal.virtual-hosts=host1.example.com,host2.example.com
or per application: e.g. for application "ucal" in ear "bwcal"
org.bedework.app.bwcal.ucal.virtual-hosts=calendars.example.com
Adding Calendar Suites
For example to duplicate the "cal" webapp as "soedept" in the ear "bwcal" add the property
org.bedework.app.bwcal.copy.soedept=cal
You then need to add any specific configuration options for that calendar suite, e.g.
org.bedework.app.bwcal.soedept.virtual-hosts=calendars.example.com
In particular you will need to specify the name of the configuration file for the calendar suite, e.g.
org.bedework.app.bwcal.soedept.config.name=SoEDept
means there will be a configuration file
jboss-5.1.0.GA/server/default/conf/bedework/client-configs/SoEDept.xml