Chapter 1 Installation and Deployment

This chapter contains the following sections to help you prepare for installation:

• Installation Process Overview


• Before You Begin the Installation


• System Requirements


• Installation Privileges


• Installation Packages


• Installation Guidelines

1. Transferring the Calendar Server Installation Files
2. Running the Installation Program

• Roughly 500 MB of disk space for a standard installation. For production systems, you should plan at least 1 GB to support the product binaries, database, and log files; 2 GB and or greater for very large calendar stores.
• 32 MB of RAM. For large production systems, however, plan from 256 MB to 1 GB of RAM for best performance.
• Adequate space for your calendar user data.
• RAID storage for fast access (optional).

• Solaris 2.6 with recommended patches. See:

http://access1.sun.com/patch.recommended/rec.html

• Microsoft Windows NT 4.0 with Service Pack 3 or later.
• HP-UX 11.00 with the following required operating system patches:

PHNE_13208

PHNE_13405

PHNE_14279

iPlanet Calendar Server 2.1.

Provides a powerful and flexible cross-platform solution to the Calendar Server hosting needs of service providers of all sizes. Using an open, Internet-standard approach to calendar hosting, it offers rapid processing of calendar scheduling data scalable to many thousands of simultaneous users.

Calendar Server API (CSAPI).

A high performance interface to enhancing and modifying the feature-set of the Calendar Server. This API lets you create very fast runtime shared objects which outperform both system executable programs and scripts in any language in terms of speed, memory footprint, and load time. CSAPI is a shared-object runtime interface to Calendar Server functions that supports the use of plugin CSAPI modules to manipulate server data when the server receives requests and sends responses. This package also includes Web Calendar Access Protocol (WCAP), a high level command-based protocol that clients use to communicate with iPlanet Calendar Server through CSAPI.

• Typical Installation. This type of installation asks the questions required to install the server. Some options are automatically configured with default values, but some require that you choose or enter the value you wish to use. Typical Installation is recommended for beginning or intermediate users or for any installation that does not require custom configuration.
• Custom Installation. This is the most complex type of installation. You must choose and enter all configuration options. Custom Installation is recommended for expert users only. Use this type of installation if you want to perform advance activities during installation such as specifying network ports other than the default values.
• Silent Installation. Use this type of installation if you want to automate your installation process when installing more than one instance of Calendar Server. This feature is especially useful for installing several servers at your site.

• Directory server accounts. Unless noted otherwise, these accounts were created if you installed Directory Server.
• Windows NT System Account. You can create this account manually or let the installation program create it for you.
• Unix system Accounts. If they do not exist, you will need to create these accounts on your Unix system before you install Calendar Server 2.1.

Calendar Server Administrator.

This is the username and associated password that can make configuration changes to the Calendar Server. This user has administration privileges over the Calendar Server, but not over the Directory Server itself. The default is calmaster.

Directory Administrator.

Also known as "Unrestricted User". If you use LDAP (the default mechanism) for user authentication, this is the username and associated password that can make changes to the Directory Server schema. This user has overall administrator privileges on the Directory Server and all servers that make use of the Directory Server, such as the Administration Server and Calendar Server, and has full administration access to all entries in the Directory Server. You enter the Directory Administrator's distinguished name (DN) when you create a Directory Server instance. The default and recommended DN is:

cn=Directory Manager,ou=Topology Manager,ou=your domain.com

Calendar Server User and Group.

(Unix only) These accounts are the user and group the make up the identity that the Calendar Server runs as. The calendar data files, such as the calendar data store, are owned by this user and group. This user and group should be highly secure and should be members of the Netscape group. For security reasons, these accounts should have no special privileges on the system. In the course of operation, servers will assign some directory permissions to this user and the Netscape group for certain server-specific operations. The Calendar Server installation program suggests the default user icsuser and the default group icsgroup and will create these accounts automatically if they do not exist.

• Host and domain names on Unix. The installation program assumes that your host and domain names are defined correctly in your Unix system files. Make sure that both the hostname and domainname commands return the correct information before installing Calendar Server. If your system does not support the domainname command, check the domain name in the /etc/resolv.conf file.
• Directories. The Messaging, Directory, and Administration servers are installed into directories referred to as server-roots. These directories provide a known file location structure (file directory path) that enables the servers to identify one another.

Calendar Server 2.1 must be installed in its own unique server-root.

1. Locate the Calendar Server 2.1 archive (tar or zip) file for your platform:

• On Unix, there are separate archive files for each supported operating system. The archive filename identifies the supported operating system.
• On Windows NT, the installation archive file is a self-extracting zip file. For example: ics20.zip

You can find the archive file on the distribution CD or download it from the iPlanet Calendar Server online site.

2. Create a directory (such as /tmp/calinstall) on the machine that will host the Calendar Server and copy the archive file to that directory.
3. Go to the directory where you copied the archive file and then extract the contents.

On Unix, type

tar -xvf archive.tar

where archive identifies the name of the platform archive file you chose to transfer.

On Windows NT:

Double-click the self-extracting ics20.exe file included as part of your installation package.

Status messages display as the archive is unpacked.

• On Unix, go to the directory location that contains the extracted installation files and type: ./setup.
• On Windows NT, run the setup.exe program located in the directory where you extracted the installation files.

• 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
• If your users are stored in a manner other than LDAP directory format, such as an OS specific or proprietary user authentication method, you can create a pug-in using the CSAPI to authenticate users and give them access to data hosted on the Calendar Server.