Page Comparison

Introduction

The quickstart includes the Calendar Suite MainCal.  You can think of a Calendar Suite as a window through which you manage and view your public events.   For many sites, the MainCal Calendar Suite is sufficient.  It's a full-sized window through which all public events are managed and viewed.   There are three likely motivations for adding another Calendar Suite:

1. You'd like to provide a smaller window for managing certain events.   This is usually done to restrict access to certain event tags (topical areas) to specific administrators.  As you'll see below, you can set up a Calendar Suite for this purpose by using the administrative client.
2. You'd like to provide a smaller window for managing and viewing certain events, and/or you'd like to create a second web site with an independent look and feel.  This is usually done to create an independent departmental instance of a fully-functioning Bedework calendar site.  As you'll see below, creating a fully-independent departmental site involves configuration work in the administrative client and making configuration changes to the Bedework system itself.  The Bedework system configuration changes involve defining a new web client to be built and deployed.

Add a New Calendar Suite

A Calendar Suite that is to have its own web context (e.g. http://localhost:8080/mydept ) must be built, and the resulting .war will be packaged up and deployed alongside the other suites.   If you wish to use calendar suites solely for limiting access to topical areas, you do not need to build it and may skip directly to Configure a Bedework Calendar Suite.

Build a Bedework Calendar Suite

1. Follow the instructions for setting up your build environment.
2. Add calendar suites to cal.properties and cal.options.xml, using the quickstart's example of SoEDept (the demo departmental public web client). Also add the suite to the list of applications to be built in the cal.properties file for the property: org.bedework.install.app.names.
3. Copy a template directory for use with the new calendar suite from an existing one, and name it with the name given the calendar suite. E.g. copy bedework/deployment/webpublic/webapp/resources/demoskins/MainCampus as ....demoskins/MyDept
4. Build Bedework

Configure a Bedework Calendar Suite

You must now define the Calendar Suite in the admin client and associate it with an administrative group.

...