test

Sun Java System Calendar Server 6.3 Administration Guide

4.2 Configuring Calendars

This section contains the following topics:

ProcedureTo Configure User Calendars

  1. Log in as an administrator with permission to change the configuration.

  2. Stop Calendar Server services by issuing the stop-cal.

  3. Change to the /etc/opt/SUNWics5/cal/config directory.

  4. Save your old ics.conf file by copying and renaming it.

  5. Edit one or more of the parameters as shown in the following table:

    calstore.calendar.default.acl

    Specifies the default access control permissions used when a user creates a calendar. The format is specified by a semicolon-separated list of access control entry (ACE) argument strings. The default is:

    "@@o^a^r^g;@@o^c^wdeic^g;
@^a^fs^g;@^c^^g;@^p^r^g"

    For more information on the ACE format, see 15.4 Calendar Access Control Calendar Server utilities, see D.5 cscal.

    calstore.calendar.owner.acl

    Specifies the default access control settings for owners of a calendar. The default is: "@@o^a^rsf^g;@@o^c^wdeic^g"

    calstore.freebusy.include.defaultcalendar

    Specifies whether a user's default calendar is included in user's free/busy calendar list. The default is “yes”.

    calstore.freebusy.remove.defaultcalendar

    Specifies whether a user's default calendar can be removed from user's free/busy calendar list. The default is “no”.

    service.wcap.freebusy.redirecturl

    Specifies a URL to use to search for a calendar in a different database. This is only used while migrating calendar databases. During the time that calendars are split between two different databases, you can specify a URL other than the current Calendar Server database. The system searches the Calendar Server calendar database first and if it can’t find the user, checks to see if the redirect URL is available. This feature can be turned off by passing in the noredirect parameter set to 1 with the get_freebusy command.

    calstore.subscribed.include.defaultcalendar

    Specifies whether a user's default calendar is included in the user's subscribed calendar list. The default is “yes”.

    service.wcap.login.calendar.publicread

    If "yes", default user calendars are initially set to public read/private write. If no, default user calendars are initially set to private read/private write. The default is “no”.

    user.allow.doublebook

    Determines if a user calendar can have more than one event scheduled for the same time period:

    • "no" prevents double booking.

    • "yes" allows double booking, and is the default.

      This parameter is used only when a user calendar is created. Thereafter, Calendar Server checks the calendar properties file (ics50calprops.db) to determine if double booking is allowed.

      To change the value of the double booking calendar property, use cscal with the -k option.

    user.invite.autoprovision

    Determines if user calendar should be auto-created if the user receives an invitation but has no default calendar. The default is the enable this option ("yes").

  6. Save the file as ics.conf.

  7. Restart Calendar Server.

    cal-svr-base/SUNWics5/cal/sbin/start-cal

ProcedureTo Configure Resource Calendars

  1. Log in as an administrator with permission to change the configuration.

  2. Stop Calendar Server services by issuing the stop-cal.

  3. Change to the /etc/opt/SUNWics5/cal/config directory.

  4. Save your old ics.conf file by copying and renaming it.

  5. Edit one or more of the parameters as shown in the following table:

    resource.allow.doublebook

    Determines if a calendar that belongs to a resource (such as a conference room or audio visual equipment) can have more than one event scheduled for the same time slot when the calendar is created:

    • "no" prevents double booking, and is the default.

    • "yes" allows double booking.

    • This parameter is used only when a resource calendar is created.

      After a resource calendar is created, Calendar Server checks the calendar properties (ics50calprops.db) to determine if double booking is allowed.

      If you need to change the calendar properties for a resource calendar to allow or disallow double booking, use csresource with the -k option.

    resource.default.acl

    Specifies the default access control permissions used when a resource calendar is created. The default is: 

    "@@o^a^r^g;@@o^c^wdeic^g;
@^a^rsf^g"
    resource.invite.autoaccept

    When invitations are sent to resources should they be automatically marked as accepted? The default is "yes".

    resource.invite.autoprovision

    When a resource is invited to an event, if it has no existing calendar, should it be autoprovisioned?

    The default is "yes".

  6. Save the file as ics.conf.

  7. Restart Calendar Server.

    cal-svr-base/SUNWics5/cal/sbin/start-cal

ProcedureTo Configure Group Calendars

A group calendar can be scheduled with events similar to a user calendar. However, a user should not log into a group calendar. To view a group calendar, the user should subscribe to it. To configure a group calendar, edit the ics.conf file as shown in the steps that follow.

  1. Log in as an administrator with permission to change the configuration.

  2. Stop Calendar Server services by issuing the stop-cal.

  3. Change to the /etc/opt/SUNWics5/cal/config directory.

  4. Save your old ics.conf file by copying and renaming it.

  5. Edit one or more of the parameters as shown in the following table:

    group.allow.doublebook

    Specifies whether the group calendar can be double booked. The default is yes.

    group.default.acl

    Specifies the default ACL for group calendars:

    "@@o^a^r^g;@@o^c^wdeic^g;@^a^rsf^g"

    group.invite.autoprovision

    Specifies whether autoprovisioning is enabled or disabled. The default is "yes" (enabled).

    group.invite.autoaccept

    Specifies whether a group invitation will automatically have PARTSTAT=ACCEPTED.

    group.invite.expand

    Determines if a group should be expanded for invitations.

    If “yes”, the list will be expanded if it meets the constraints of the calstore.group.attendee.maxsize parameter. If the expansion fails, or this parameter is set to "no", only the group name shows up on the attendee list and no RSVP is required.

    calstore.group.attendee.maxsize

    Specifies whether groups can be expanded. A value of "0" means no expansion limits. A group of any size can be expanded.

    If expansion is allowed, but not unlimited. The value of the parameter indicates the maximum number of attendees allowed in an expanded group. If the number in the group exceeds the maximum size, then the group is not expanded.

    A value of "-1" means no expansion allowed.

    If expansion is not allowed because it exceeds the maximum size, only the group name appears in the attendee list and an error is returned to the organizer.

  6. Save the file as ics.conf.

  7. Restart Calendar Server.

    cal-svr-base/SUNWics5/cal/sbin/start-cal
See Also

For instructions on configuring groups, see To Configure Calendar Server for Groups.

ProcedureTo Disable Autoprovisioning of Calendars

Autoprovisioning of user , resource and group calendars is enabled by default. That is, if a user attempting to log in does not yet have a default calendar, the system creates a user calendar with default settings.

If a user, resource or a group is invited to an event, but it does not yet have a default calendar, the system creates a resource or group calendar with default settings.

If you want to disable any of these calendars from being autoprovisioned, change the appropriate parameter in the ics.conf file as shown in the steps that follow.

  1. Log in as an administrator with permission to change the configuration.

  2. Stop Calendar Server services by issuing the stop-cal.

  3. Change to the /etc/opt/SUNWics5/cal/config directory.

  4. Save your old ics.conf file by copying and renaming it.

  5. Disable autoprovisioning of user, resource and group calendars by editing the following parameters:

    local.autoprovision

    Specifies whether autoprovisioning of user calendars is enabled (“yes”), or disabled (“no”). The default is “yes”.

    resource.invite.autoprovision

    Specifies whether autoprovisioning of resource calendars is enabled (“yes”), or disabled (“no”). The default is “yes”.

    group.invite.autoprovision

    Specifies whether autoprovisioning of group calendars is enabled (“yes”), or disabled (“no”). The default is “yes”.

    autoprovisioning

    Specifies whether auto-inviting of user calendars is enabled (“yes”), or disabled (“no”). The default is “yes”.

  6. Save the file as ics.conf.

  7. Restart Calendar Server.

    cal-svr-base/SUNWics5/cal/sbin/start-cal

ProcedureTo Configure Free-Busy Lookup

The free-busy view is used for several purposes. There are a number of ics.conf parameters that can be set to customize how the free-busy view is generated.

  1. Log in as an administrator with permission to change the configuration.

  2. Stop Calendar Server services by issuing the stop-cal.

  3. Change to the /etc/opt/SUNWics5/cal/config directory.

  4. Save your old ics.conf file by copying and renaming it.

  5. Edit one or more of the following ics.conf parameters shown in the following table:

    service.wcap.freebusybegin

    Specifies the offset from the current time in days for get_freebusy for beginning of the range. The default is "30".

    service.wcap.freebusyend

    Specifies the offset from the current time in days for get_freebusy for end of the range. The default is "30".

    calstore.freebusy.include.defaultcalendar

    Specifies whether a user's default calendar is included in user's free/busy calendar list. The default is "yes".

    calstore.freebusy.remove.defaultcalendar

    Specifies whether a user's default calendar can be removed from user's free/busy calendar list. The default is "no".

  6. Save the file as ics.conf.

  7. Restart Calendar Server.

    cal-svr-base/SUNWics5/cal/sbin/start-cal