Complete Contents
Preface
Chapter 1 Installation and Deployment
Chapter 2 Configuring Calendar Server
Chapter 3 Admininistering Calendar Server
Chapter 4 Monitoring the Calendar Server
Appendix A Commnand Line Utilities
Appendix B Monitoring Tools
Appendix C Time Zones
Appendix D Calendar Server LDAP Schema
Index
iPlanet Calendar Server: Administration Guide: Preface
Next Contents Index


Preface

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.


Who Should Read This Book
You should read this book if you are responsible for installing and deploying Calendar Server at your site.


What You Need to Know
Before you install and administer Calendar Server, you must be familiar with the following concepts:


What's in This Guide
If you want to...
See...
Learn more about Calendar Server and how to get started.
What is iPlanet Calendar Server? in this preface
Install and deploy Calendar Server.
Chapter 1, Installation and Deployment
Configure your Calendar Server.
Chapter 2, Configuring Calendar Server
Administer your Calendar Server using the command line utilities.
Chapter 3, Administering Calendar Server
Monitor and control your Calendar Server.
Chapter 4, Monitoring the Calendar Server
Learn about the complete syntax and usage of the command line utilities.
Appendix A, "Command Line Utilities"
Learn about the server monitor tools.
Appendix B, "Monitoring Tools"
Add or modify Calendar Server time zones.
Appendix C, "Time Zones"
See the LDAP schema extensions used by Calendar Server.
Appendix D, "Calendar Server LDAP Schema"
Find information in the guide.
Index


Document Conventions
Sidebar text
Sidebar text marks important information. Make sure you read the information before continuing with a task.

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.

Italicized Monospaced font—This typeface is used to represent text that you enter using information that is unique to your installation. It is used for server paths and names and account IDs.

For example, throughout this document you will see path references of the form:

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:

Also, all paths specified in this manual are in Unix format. If you are using a Windows NT-based Calendar Server, you should assume the Windows NT equivalent file paths whenever Unix file paths are shown in this book.


What is iPlanet Calendar Server?
iPlanet Calendar Server is the first readily deployable, Internet web-based solution that lets the ISP/Enterpise and Telecommunication service provider host personal event calendars to their base of subscribed customers. Using iPlanet Calendar Express, a web browser-based client application, customers can access data hosted on the Calendar Server to:

Built from the ground up to provide native support for the emerging set of internet calendar standards, iPlanet Calendar Server provides the following benefits:

Calendar Server Features
iPlanet Calendar Server offers the service provider the following administration capabilities:


Architectural Overview
The following sections provide a general overview of the iPlanet Calendar Server product architecture which consists of the following subsystem components:

Figure 1 illustrates iPlanet Calendar Server general architecture:

Figure 1    iPlanet Calendar Server Architectural Overview

HTTP Protocol
iPlanet Calendar Server provides a default web calendar client (Calendar Express) and a general purpose HTTP server to support HTTP clients that request calendar data. Figure 2 illustrates, at the highest level, how Calendar Server operates.

Figure 2    HTTP as Primary Transport

Calendar Server uses HTTP as its primary client. It receives commands encoded in HTML and sends replies as HTML and JavaScript. The data returned from requests is not formatted for display. The embedded JavaScript generates HTML which it sends to a visible frame accessed by a web browser. The user experience is the same as if the HTML was loaded from a server. The advantage is that for many operations, JavaScript can handle everything locally and does not need to contact the server. This provides a faster screen update for the user while lightening the load on the Calendar Server.

Web Calendar Access Protocol (WCAP)
The Web Calendar Access Protocol (WCAP) is a simple calendar protocol for storing, retrieving, and administering calendars. WCAP interprets HTTP requests and sends them to the core calendar services for execution. WCAP then receives commands from the core services, then encodes them into HTML format and returns them to the browser client.

Core Calendar Services
Commands enter through the HTTP protocol subsystem as WCAP. The core services make data requests to the calendar database where information is stored or retrieved and then returned in HTML format. The core system then translates:

Calendar Server Application Program Interface (CSAPI)
The Calendar Server Application Program Interface (CSAPI) enables third party application developers to add functionality to Calendar Server or change how it performs certain operations. CSAPI provides supports in four major functional areas:

For example, the default mechanisms used by Calendar Server for user authentication and storing user preferences relies on LDAP, but an ISP may have an existing infrastructure for authenticating users and saving user information that is not based on LDAP. An ISP can use CSAPI to override these default mechanisms and utilize their existing authentication and user directory services.

Supported Format Encoding
Calendar Server supports the following format encoding (all embedded within HTML):

Other formats can be added by third parties by developing a translator DLL or shared library using the Calendar Server Application Program Interface (CSAPI), an API for extending the Calendar Server.

Figure 3 is a detailed diagram of the iPlanet Calendar Server components and data flow design.

Figure 3   

Subsystems and Data Flow

Database Technology
The local database used by Calendar Server is the Berkeley DB which is included as part of the installation package and supports transactions and live backups.

Calendar Server uses three physical databases:


User Authentication and Preferences
By default, Calendar Server supports users that are defined and maintained in an LDAP directory, such as Netscape Directory Server. Calendar Server also supports the use of CSAPI plug-ins that you create and enable access to users defined in non-LDAP directories such as those stored in a standard Unix Authentication format or in a Windows NT User Manager database.

LDAP (Netscape DS 4.1)
If your users are already stored in an LDAP directory, the simplest solution to deploy Calendar Server is to upgrade your directory server to Netscape Directory Server 4.1 which includes the schema extension that enables users to access Calendar Server data. Otherwise, you can modify your directory schema manually to allow your users to access to Calendar Server data. For more information on how to modify a directory schema for Calendar Server, see Appendix D, "Calendar Server LDAP Schema."

External Directories
If your users are stored in a manner other than LDAP directory format, such as an OS specific or a proprietary authentication program, you can create a plug-in that uses CSAPI to authenticate users and give them access to data hosted on the Calendar Server.


Administration
Calendar Server provides several command line utilities that let you perform administrative tasks (such as enabling and disabling access to Calendar data) and changing Calendar properties (such as owners). For more information, see Chapter 3, Administering Calendar Server, and Appendix A, Command Line Utilities.

 

© Copyright 2000 Sun Microsystems, Inc. Some preexisting portions Copyright © Netscape Communications Corp. All rights reserved.