Complete Contents
Chapter 1 Preparing for Installation
Chapter 2 Running the Setup Program on Unix
Chapter 3 Running the Setup Program on Windows NT
iPlanet Calendar Server: Installation Guide: Preparing for Installation
Previous Next Contents Index

Chapter 1 Preparing for Installation

This chapter contains the following sections to help you prepare for installation of iPlanet Calendar Server 2.1:

Note. For the most recent information about known problems with this release, please see the iPlanet Calendar Server release notes online listed at the following site:

Installation Overview
There are three basic steps involved in installing iCS:

  1. Gathering Your Installation Information.
  2. Installing and Configuring an LDAP Server.
  3. Installing iPlanet Calendar Server. See Installing Calendar Server on Unix or Installing Calendar Server on Windows NT.
On Unix:

System Requirements
Before you install iPlanet Calendar Server, you must make sure you have met the minimum hardware and operating system requirements.

Supported Platforms
This release of iPlanet Calendar Server supports the following platforms:

Hardware Requirements
The basic minimum hardware requirements for installing iCS 2.1 are as follows:

Software Requirements
iCS 2.1 has the following software requirements:

For information on kernel tuning your OS, see the iPlanet Calendar Server 2.1 release notes listed at:

Note. A web browser, such as Netscape Communicator 4.61, is required to use the Calendar Express client bundled with the Calendar Server. An LDAP server, such as Netscape Directory Server 4.1, is required to store user authentication and user preference information. An SMTP server, such as Netscape Messaging Server 4.1, is required for mail notifications of calendar entries. On Unix systems, the installation package is a GNU-zipped tar file. To unzip it, you will need a copy of gunzip.

Installation Privileges
It is recommended that you install iPlanet Calendar Server logged in as root (Unix) or administrator (Windows NT). Superuser privileges (root or administrator) are required for Calendar Server 2.1 installations.

Gathering Your Installation Information
Before beginning the installation process, it is helpful to gather the installation and configuration information you will need. The information will differ according to the type of installation you select. The two installation types are:

Typical Installation. This is the simplest type of installation. Most options are automatically configured with default values, but some require that you choose and enter the value you wish to use. This type of installation is recommended for most administrators or for any installation that does not require a custom configuration. For checklist information on completing this type of installation, see Typical Installation Checklist.

Custom Installation. This is a more complex installation than the typical installation. You must choose and enter all configuration values. This type of installation is recommended for advanced administrators only. For checklist information on completing this type of installation, see the Custom Installation Checklist.

Typical Installation Checklist
You need the following information to complete the installation procedure for a Typical Installation.

Component Selection
Choose one or more of the following:

Installation Directory
Determine the name and path of the directory in which you want the server to be installed. For example, /opt. If the installation is for a large deployment, ensure that it is installed on a machine with a storage device large enough to handle the load, such as a high capacity hard drive with adequate free space, or a Redundant Array of Inexpensive Disks (RAID).

Service Ports
The TCP ports that you want Calendar Server services to listen on:

Server User and Group Account (Unix only)
These accounts are the Unix user and group identity under which server will run. It is recommended to use the defaults icsuser and icsgroup. These accounts will be created automatically by the installation program if they do not already exist.

Calendar Server Administrator
This is the LDAP user account that can manage your iPlanet Calendar Server. This user account must be a userid that already exists in your user authentication LDAP directory. This user account will be used by the administration utilities to authenticate to the Calendar Server for commands to perform actions such as stopping the Calendar Server or listing all the logged-in users. No verification is done to check if this userid exists in the directory.

Email and Email Alarms Address
Identify the following:

LDAP Server Information
Identify the following LDAP server information for user authentication and preferences:

Custom Installation Checklist
In addition to the information in the Typical Checklist, you will need the following information to complete the Custom Installation procedure:

System Resources
Select desired values for the following system resources:

Calendar Database Directory
Specify the directory to place the server database.

Installing and Configuring an LDAP Server
For information on how to install and configure the Netscape Directory Server 4.1, go to:

Note. If you are using Netscape Directory Server version 4.1, it has the iPlanet Calendar Server schema already configured into the default schema and requires no additional preparation.

If you, however, you are using Netscape Directory Server version 4.0:

  1. Install iPlanet Calendar Server 2.1.
  2. Copy the ns-wcal-schema.conf file from the server-root/SUNWicsrv/cal/bin/config directory into the Directory Server 4.0 server-root/slapd-machinehostname/config directory.
  3. Edit the ns-schema.conf file (in the same directory that you copied the ns-wcal-schema.conf file to) so that it includes the file ns-wcal-schema.conf.
  4. Stop the Calendar Server if it is running.
  5. Stop and restart the Directory Server.
  6. Start the Calendar Server.

Important Considerations
Note the following considerations before installing iPlanet Calendar Server:


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