...
org.bedework.install defines which applications are built and deployed to jboss. For each name on the list, there should be a corresponding section prefixed with "org“org.bedework.app.<name>" <name>” and also a corresponding section in the options file.
...
Review the Global Section of the file
The section prefixed "“org.bedework.global" ” defines properties global to the whole deployment process. This is the section where jboss's datasource (database) is defined. If you based your configuration on the sample configuration that corresponds to your database system, then you may not have to alter any settings in this section.
...
The section with properties prefixed "“org.bedework.app.<name>" ” are the application deployment properties, one section per named application.
Two properties define the project and type of application. The value of the property "“org.bedework.app.<name>.project" ” defines which project the application is a part of. Currently these can be
- "caldav" “caldav” - a caldav server
- "caldavTest" “caldavTest” - a caldav test package
- "webapps" “webapps” - a web client
- "dumprestore" “dumprestore” - a dump/restore application
- "freebusy" “freebusy” - the freebusy aggregator
The value of the property "org“org.bedework.app.<name>.type" type” corresponds to the name of a subdirectory in bedework/deployment, e.g. webpublic, webadmin, etc. So to define the administrative client named CalAdmin of type webadmin we have the fragments:
...
It is important to set the "system" “system” properties for a new Bedework installation. These are found in the "syspars" “syspars” section of the cal.options.xml file. A number of 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).
Calendar user addresses take the form of a "mailto“mailto:" ” uri so that user "testuser01" “testuser01” on a system configured as above would have a calendar user address of
...