This document describes the architecture of iPlanet Calendar Server, and provides a detailed description of the Web Calendar Access Protocol (WCAP), the protocol you use to access services, as well as the Calendar Server Application Programming Interface (CSAPI) that you use to modify server functionality.

• Core Architecture
• Calendar Database
• User Data
• Command Overview
• Command Formats
• Recurrence Handling
• Command Details
• Error Handling
• Examples of Command Usage
• CSAPI Architecture
• API Reference

Monospaced font—This typeface is used for any text that appears on the computer screen or text that you should type. It is also used for filenames, distinguished names, functions, and examples.

server-root/cal

In these situations, server-root represents the directory path in which you installed Calendar Server. For example, if you install your server in the default directory location suggested by the installation program:

• on Unix the actual path is: /opt/SUNWicsrv/cal
• on Windows NT the actual path is: c:\iplanet

• update personal schedules with their own appointments
• publish calendars for viewing by other people

• Massively Scalable. Scaling to the requirements of the largest service providers, it supports a hosting environment of up to several million personal event calendars.
• Low Cost of Ownership. Native support of LDAP lets a service provider centrally manage its entire customer base in a single user directory and minimizes the costs of administering the server while also providing a platform for extending the enhanced services a provider can offer its customers.
• Internet Calendaring and Scheduling. Native support for iCalendar calendaring standards lets users schedule personal events in a format that is easily shared across the internet.