This manual explains how to install and administer iPlanet Calendar Server 2.1 and its accompanying software components. Calendar Server is a powerful and flexible cross-platform solution using open Internet standards that lets service providers of all sizes host personal scheduling calendars for their customers.
basic administrative procedures of your operating system (UNIX or Windows NT)
using a web browser to access the internet
Lightweight Directory Access Protocol (LDAP) if you plan to use an LDAP directory to store user information
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 the server-root is opt/SUNWicsrv where:
on Unix the actual path is: /opt/SUNWicsrv/cal
on Windows NT the actual path is: c:\iplanet
maintain personal schedules with their own appointments
publish calendars for viewing by other people
general reminders
browse other people's calendars
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.
Works with any LDAP server.
Enables customization of the Calendar Express client user interface (e.g., login screen, colors, and templates).
Delivers calendar data in multiple formats (e.g., XML, iCAL, and Javascript) wrapped within HTML.
Provides command line utilities to manage calendar data and calendar users, and to monitor and control the Calendar Server.
HTTP Protocol
Web Calendar Access Protocol (WCAP)
Core Calendar Server services
Calendar Server Application Program Interface (CSAPI)
Calendar Database
Figure 1 iPlanet Calendar Server Architectural Overview
Figure 2 HTTP as Primary Transport
low-level format information into the format requested by WCAP commands which is then encoded into HTML format and returned to the browser client.
stored data into the binary format used by the calendar database.
authentication
user attributes and preferences
data translators
Calendar Application Program Interface (CAPI)
HTML/JavaScript (default)
HTML/XML
HTML/iCalendar
Figure 3
Subsystems and Data Flow
A calendar database that stores information such as the properties, events and tasks, and alarm notifications belonging to each calendar. The calendar database files are located in the server-root/cal/bin/lock directory.
A sessions database that stores information about user sessions such as the login state time outs of calendar users. The sessions database files are located in the server-root/cal/bin/sessions directory.
A counter database that stores statistics about the Calendar Server such as the total number of successful and failed server logins. The counter database file (which is actually a memory mapped file rather than a Berkeley database) is located in the server-root/cal/bin/ directory.
Subsystems and Data Flow