...
org.bedework.app.bwcal.ucal.virtual-hosts=calendars.example.com
Adding Calendar Suites
For example to duplicate Each public calendar context is called a "calendar suite". It provides full calendar navigation, control over what public events are exposed, and access control to topical areas. Many sites may have only the one MainCampus suite. If you want to roll out departmental public calendar suites, follow these steps.
- Duplicate the "cal" webapp
...
- . For example, to create "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
...
- For each suite, you must add a configuration file named ConfigName.xml. You can manually copy and edit the SoEDept.xml file found at
jboss-5.1.0.GA/server/default/conf/bedework/client-configs/SoEDept.xml
- You must then specify the name of the configuration file for the calendar suite in the deploy configuration, 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
You must rebuild to generate the calendar suites. To configure them, see