Sun Java System Calendar Server 6.3 Administration Guide

15.5 Creating Calendars

This section contains conceptual information and instructions on how to create calendars.

This section contains the following topics:

15.5.1 Creating a User Calendar with the `cscal`Utility

This section contains the following topics and examples:

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

The string -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.

15.5.1.1 Overview of Creating a New Calendar

To create a new calendar, use the cscal utility with the create command. The user or resource entry must already exist in the LDAP directory. Refer to Chapter 14, Administering Users, Groups, 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 5, Configuring Calendar Database Distribution Across Multiple Machines in Calendar Server Version 6.3.

15.5.1.2 Creating New Calendars

To create a new calendar, the minimal command is the following:

cscal -o uid  create calid

For example, for the user John Smith with a unique ID and calendar ID of jsmith the command would look like the following:

cscal -o jsmith create jsmith

The command has the following parts:

cscal: The name of the utility.
-o: The unique ID (uid) of the primary owner for this calendar.
create: The command to create the new calendar.
calid: The calendar ID to be assigned to this calendar.

For more information about the cscal utility, see D.5 cscal also located in this guide.

Tip –

The default access control settings are defined by calstore.calendar.default.acl in the ics.conf file.

15.5.1.3 Creating Another Calendar for a User

You can create multiple calendars for any user. However, they are always identified as sub-calendars of the default calendar. The fully qualified name of the new calendar will have the default calendar name on the left of a colon separator and the new calendar's name on the right of the colon separator.

The following example demonstrates how to create another (non-default) calendar for a user, John Smith, with the name of the new calendar as Personal:

cscal -o jsmith@sesta.com create Personal

The parts of the command are as follows:

cscal

The name of the utility.

-o jsmith@sesta.com

The unique ID (uid) of the primary owner for this calendar.

create

The command to create the new calendar.

Personal

The second half of the calendar ID (calid) to be assigned to this calendar.

The fully qualified calendar ID is jsmith@sesta.com:Personal.

15.5.1.4 Creating a Calendar with a Viewable Name

This example shows how to give a separate viewable name, “Hobbies”, to the Personal non-default calendar created in the previous example.

cscal -o jsmith@sesta.com -n Hobbies create Personal

-o

jsmith@sesta.com Specifies the user ID of the primary owner.

-n

Hobbies Specifies the viewable name of the calendar.

Personal

The name of this new additional calendar for John Smith.

The entire calid becomes: jsmith@sesta.com:Personal.

15.5.1.5 Creating a Calendar with Other Properties

The following example creates a new calendar, Personal, 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 command has the following parts:

cscal

The name of the utility.

-o jamsith@sesta.com

The unique ID (uid) of the primary owner for this calendar.

-g sports

This option associates the calendar, Personal, with a category named sports.

-y

The value rjones@sestas.com specifies another owner of the calendar.

-k yes|no

This option enables or disables double booking of events in one time slot.

A value of yes enables double booking. A value of no would disable double booking.

create

The command to create the new calendar.

Personal

The calendar ID to be assigned to this calendar.

15.5.2 Configuring the Calendar Server for Resources

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:

resource.default.acl: A default access control list.
resource.allow.doublebook: A parameter that allows or disallows doublebooking.

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 version 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 version 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


Parameter	Description and Default Value
`resource.default.acl`	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): `"@@o^a^r^g;@@o^c^wdeic^g;@^a^rsf^g"` 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.
`resource.allow.doublebook`	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 value 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.
`resource.invite.autoprovision`	The default value is `"yes".`
`resource.invite.autoaccept`	The default value is `"yes"`.

15.5.3 Creating Resources and Resource Calendars

Tip –

If the value of the ics.conf parameter resource.invite.autoprovision is "yes", the resource calendar will be created upon first invitation. That is, if this resource does not already have a default calendar, the first time its scheduled in an invitation, a resource calendar will be created.

To create a resource, use one of the following methods:

Calendar Server Utility (Schema version 1)

Use csresource create

This utility creates both the LDAP entry and the default calendar for the resource.

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

For example, to create a resource LDAP entry and calendar with the calendar ID aud100, viewable name Auditoriumwith the default settings, use the following command:

csresource -m aud100@siroe.com -c aud100 create Auditorium

Delegated Administrator Utility and Calendar Server utility

Use a combination of two commands:

The Delegated Administrator Utility command commadmin resource create to create the LDAP entry.
The Calendar Server Utility command csresource create to create the default calendar.

Delegated Administrator Console

To create the LDAP resource with the Console, select the organization where this resource will reside from the Organizations List. From the Calendar Resources page for this organization, click New to bring up the Create New Calendar Resource Wizard.

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.

15.5.4 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@sesta.com as another owner:

csresource -m aud100@siroe.com -c aud100 -k yes
    -o bkamdar -y jsmith@sesta.com create Auditorium

15.5.5 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.siteadmin.userid parameter in the ics.conf file.