Sun Java System Calendar Server 6 2005Q4 Administration Guide

Creating Calendars

This section contains the following topics:

Creating a User Calendar Using cscal

To create a new calendar, use the cscal utility create command. The user or resource entry must already exist in the LDAP directory. Refer to Chapter 14, Administering Users and Resourcesfor information on adding users and resources to your LDAP directory.

If your site is using the LDAP Calendar Lookup Database (CLD) plug-in, you must create all of the calendars for a particular user or resource on the same back-end server, as indicated by the icsDWPHost LDAP attribute in the user or resource entry. If you try to create a calendar on a different back-end server, the cscal utility returns an error. For information about the LDAP CLD plug-in, see Chapter 6, Configuring Calendar Database Distribution Across Multiple Machines.

For example, to create a new calendar with the calendar ID (calid) jsmith:

cscal -o jsmith -n JohnSmithCalendar create jsmith


To create a calendar with the viewable name Hobbies that is owned by John Smith and uses the default access control settings for group scheduling:

cscal -n Hobbies -o jsmith create Personal


The following example creates a new calendar similar to the previous example, but it also associates the calendar with the category named sports, enables double booking, and specifies Ron Jones as another owner:

cscal -n Hobbies -o jsmith -g sports -k yes -y rjones create Personal


The following example creates a calendar similar to the previous example, but it also sets specific access control settings for group scheduling:

cscal -n Hobbies -o jsmith -a "@@o^a^sfr^g" create Personal

where -a "@@o^a^sfr^g" grants other owners schedule, free/busy, and read access privileges to both the components and calendar properties of this calendar for group scheduling.

Preparing to Create Resource Calendars

A resource calendar is associated with things that can be scheduled, such as meeting rooms, notebook computers, overhead projectors and other equipment. Resource calendars require access control lists.

As shown in table Table 15–3, two configuration parameters in the ics.conf file apply to resource calendars:

To change the default values for these parameters (shown in table Table 15–3), edit the ics.conf file. Changes to the default values will apply only to new resource calendars; it will not change the values for existing resources.

For Schema 1, use the Calendar Server Utility cscal to change values for an existing resource calendar. The csresource utility does not have a modify command.

For Schema 2, use the Delegated Administrator Utility command commadmin resource modify. The Delegated Administrator Console does not allow you to change these values for calendar resources.

Note –

The Calendar Server notification software is not programmed to send notifications to resources, only to users.

Table 15–3 Resource Calendar Configuration Parameters in the ics.conf file


Description and Default Value  


This parameter determines the default access control permissions used when a resource calendar is created. The default permissions are specified by the following Access Control List (ACL): 


This ACL grants all calendar users read, schedule, and free/busy access to the calendar, including both components and properties. 

To change the permissions for a resource, use the-a option when you create the calendar using the csresource utility create command.


This parameter determines if a resource calendar allows doublebooking. Doublebooking allows a resource calendar to have more than one event scheduled for the same time. 

The default is "no"— Do not allow doublebooking.

To allow doublebooking for a resource calendar, use the -k option when you create the calendar using the csresource utility create command.

Creating a Resource Calendar

Calendar Server does not have autoprovisioning of resource calendars. For every resource required at your site, you must use of the following methods:

Note –

If there is an existing LDAP entry for the resource, csresource creates only the calendar. It will not create a duplicate LDAP entry.

For more information about the Delegated Administrator Utility, see Sun Java System Communications Services 6 2005Q4 Delegated Administrator Guide.

For more information about the Delegated Administrator Console, see the online help.

For more information about csresource, see Appendix D, Calendar Server Command-Line Utilities Reference.

Allowing Double Booking of Resource Calendars

By default, Calendar Server does not allow double booking for a resource calendar (resource.allow.doublebook parameter). This default prevents scheduling conflicts for resources such as rooms and equipment. However, if you want to allow double booking for a resource calendar, set the csresource -k option to “yes” when you create the calendar.

The following command creates a resource LDAP entry and calendar, but the -k option allows double booking on the calendar, the -o option specifies bkamdar as the owner of the calendar, and the -y option specifies jsmith as another owner:

csresource -m -c aud100 -k yes
    -o bkamdar -y jsmith create Auditorium

Limiting Access to Resource Calendars

To control who can schedule a specific resource, consider limiting the users who have write access to the resource calendar. For example, you might want to allow only certain users to schedule meeting rooms or reserve equipment.

If you do not specify an owner for a resource calendar, the value is taken from the service.admin.calmaster.userid parameter in the ics.conf file.