...
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=/EventregDSTransport 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.
...
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=SoEDeptmeans there will be a configuration file
jboss-5.1.0.GA/server/default/conf/bedework/client-configs/SoEDept.xml