| Previous Contents Index Next |
| iPlanet Calendar Server Installation Guide |
Chapter 1 Preparing for Installation
This chapter contains the following sections to help you prepare for installation of iPlanet Calendar Server 5.0:
Installation Overview
Gathering Your Installation Information
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:
Gathering Your Installation Information.
On Unix:Installing and Configuring an LDAP Server.
Installing iPlanet Calendar Server. See Installing iPlanet Calendar Server on Unix or Installing iPlanet Calendar Server on Windows NT.
The installation program uses an X-Windows graphical user interface. It is recommended that you install iCS using a local terminal window.
If you cannot use X-Windows remotely or if your machine does not have X-Windows installed, you must use the command line installation. The command line installation follows the same process as the graphical installation. The difference between the graphical and command line interfaces is in how you invoke the installation setup script.
If you must run the installation program from a remote terminal, be sure to set your DISPLAY environment variable properly on the remote machine and be sure to allow X-Windows connections from the machine to appear on your terminal (for example, using the utility xhost +).
System Requirements
Before you install iPlanet Calendar Server, you must ensure you have met the minimum hardware and operating system requirements. For the latest information on the supported platforms and software and hardware requirements, see the iPlanet Calendar Server 5.0 release notes listed at:http://docs.iplanet.com/docs/manuals/calendar.html
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 iPlanet Calendar Server 5.0 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 service port is the TCP port number that you want iPlanet Calendar Server to use to provide web (HTTP) access to users (default is 80). It is highly recommended that you choose the Web port number suggested by the installation program because 80 is the default port number used by all Web browsers. If you specify a port number other than 80, calendar users will need to explicitly include this port number in the URL they enter to access their calendars on this Calendar Server. If port 80 is already in use, it is recommended that you free port 80 on the other service before you install iPlanet Calendar Server.
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 Identity (Windows NT only)
This is the identity iPlanet Calendar Server will run as. The installation program assumes this identity is the user (and password) that is currently logged in to the system and it cannot be changed while you run the installation program. This user must have full administration rights to this system. Therefore, before you start the installation program, be sure to log in as the user that you want iPlanet Calendar Server to run as and ensure that this user has full administration rights to the system on which you are installing iPlanet Calendar Server.
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 must also exist in the directory server used to store user preferences if they are stored on another directory server. 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 server or listing all the logged-in users.
Email and Email Alarms Address
Identify the following:
Calendar Server Administrator email address. This address uses the syntax: userid@hostname.domainname. For example, calmaster@siroe.com.
SMTP server host name. This is the fully qualified host name of the SMTP server that the iPlanet Calendar Server will use to send email messages. For example:
- calhome.siroe.com
- where calhome is the machine's host name and siroe.com is the DNS domain name on which the SMTP server is running.
LDAP Server Information
Identify the following LDAP server information for user authentication and preferences:
Host: The host name of the machine where the LDAP server is installed. The default is the host name of the machine on which you are running the installation program.
Port: The service port for the LDAP server. The default is 389.
Base DN: The Base DN (distinguished name) is the entry in your LDAP directory used as the starting point from which searches will occur. For example, if you specify a base DN of ou=people, o=siroe.com, all LDAP search operations executed by iPlanet Calendar Server will examine only the ou=people subtree in the o=siroe.com directory tree.
Administrator Bind DN: The DN of the account that has privileges to manage the attributes of any calendar user in the LDAP directory that stores user preferences. The default is:
Administrator Password: The password for the user account of the Administrator Bind DN described above.
- uid=admin,ou=Administrators,ou=TopologyManagement,o=NetscapeRoot
- The default bind DN will work with any 4.x version of the Netscape/iPlanet LDAP directory. On a Netscape/iPlanet Directory Server 4.x server, you can verify that this DN exists by using the directory server ldapsearch utility, for example:
- ./ldapsearch -b o=NetscapeRoot uid=admin
Directory Manager (also known as "Unrestricted User") of the Directory Server that stores user and group information. This is the username and password of the person who can make changes in the Netscape 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 has full administration access to all entries in the Directory Server. The Directory Manager's distinguished name (DN) was supplied when the directory server was installed. The default DN is cn=Directory Manager. This information is needed because iPlanet Calendar Server 5.0 requires specific updates to the LDAP schema.
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 the desired values for the following system resource allocations to run iPlanet Calendar Server:
Calendar Database Directory
Specify the directory to place the server database.
On Solaris, the default is:
On Unix systems other than Solaris, the default is:
/var/opt/iPlanet/CalendarServer5/csdb
On Windows NT, the default is:
c:\Program Files\iPlanet\CalendarServer5\var\csdb
- Note that on Windows NT, this directory must be located on an NTFS formatted drive and not on a FAT file system.
Installing and Configuring an LDAP Server
iPlanet Calendar Server 5.0 stores and manages calendars, calendar properties, access control information, events, todos, and alarms. It does not, however, manage storage for user information. iPlanet Calendar Server requires a directory service perform operations such as user authentication and storage and retrieval of user preferences. The default installation supports users defined and maintained in an LDAP directory, such as iPlanet Netscape Directory Server, and the installation package includes iPlanet Netscape Directory Server 4.12.If your users are already stored in an LDAP directory, the simplest solution for deploying iPlanet Calendar Server is to upgrade your directory server to Netscape Directory Server 4.12 (or later) which supports the schema extensions that enable users to access iPlanet Calendar Server data. Otherwise, you can modify your directory schema manually to allow your users to access to iPlanet Calendar Server data.
For information on how to install and configure iPlanet Netscape Directory Server, go to:
http://docs.iplanet.com/docs/manuals/directory.html
Updating the LDAP Schema
The LDAP schema extensions used by iPlanet Calendar Server 5.0 are defined in the following files:
um50-common-schema.conf which defines the LDAP attributes and object classes shared by iPlanet products.
If you are using Netscape Directory Server 4.12 or later, the installation program will attempt to automatically update your directory schema to work with iPlanet Calendar Server 5.0. You can also manually update the directory schema as follows:ics50-schema.conf which defines the LDAP attributes and object classes used by iPlanet Calendar Server 5.0.
Install iPlanet Calendar Server 5.0 and save the LDAP schema files locally when given this option during the installation process.
Copy the LDAP schema files (um50-common-schema.conf and ics50-schema.conf) from the location in which you saved them to the machine on which your Directory Server is running into the directory server-root/slapd-hostname/config directory (for example, /usr/Netscape/Server4/slapd-hostname/config).
Stop the iPlanet Calendar Server if it is running.
- Note: You can download the most up to date iPlanet Calendar Server 5.0 schema files at:
- http://www.iplanet.com/products/infrastructure/messaging/ics/index.html
Stop the Directory Server if it is running.
Edit the ns-schema.conf file (in the same directory in which you copied the um50-common-schema.conf and ics50-schema.conf files) and, at end of the file, if they are not already present, add the lines to include these files. For example:
Start the Directory Server.
- On Unix:
include /netscape/server4/slapd-myhost/config/um50-common-schema.conf
include /netscape/server4/slapd-myhost/config/ics50-schema.conf
- On Windows NT:
include "C:/Netscape/Server4/slapd-myhost/config/um50-common-schema.conf"
include "C:/Netscape/Server4/slapd-myhost/config/ics50-schema.conf"
- Note: Be sure to add the lines in the order shown above so that um50-common-schema.conf is included before ics50-schema.conf.
Important Considerations
Note the following considerations before installing iPlanet Calendar Server:
On Unix systems, the installation program uses the command /usr/bin/domainname to identify the associated DNS domain name of your system. To verify that this setting is correct, at the command prompt, type:
Some Unix Systems have been encountered where the value returned by hostname could not be used in the IP addresses associated with that system. For example, the machine name is x.example.com, but TCP/IP applications must use y.example.com to connect to it. It is believed that this is a badly configured machine. If you install iPlanet Calendar Server on such a machine, entries in the ics.conf file may have incorrect values. Ideally, the machine should be reconfigured. If you cannot change the configuration of the machine, you will have to edit the ics.conf file explicitly using a text editor to correct the host name values. Additionally, there are several properties with property names containing the strings "host" and "hostname" that have null values. A null value signals the server to use the value returned by gethostname(3C). You will have to manually add the host name recognized by the TCP/IP subsystem as a value for these properties.
- domainname
- The above command should return the DNS domain name of your system correctly. If this is not the case, set the domain name by typing:
- domainname <your system domain name>
- If the installation program cannot determine the DNS domain name as described above, it will attempt to read this value in the etc\resolv.conf file, if available.
Previous Contents Index Next
Copyright © 2000 Sun Microsystems, Inc. Some preexisting portions Copyright © 2000 Netscape Communications Corp. All rights reserved.
Last Updated November 02, 2000