Chapter 1 Preparing for Installation This chapter contains the following sections to help you prepare for installation of iPlanet Calendar Server 2.1:
This chapter contains the following sections to help you prepare for installation of iPlanet Calendar Server 2.1:
Gathering Your Installation Information.
Installing and Configuring an LDAP Server.
Installing iPlanet Calendar Server. See Installing Calendar Server on Unix or Installing 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 +).
Solaris 2.6 / Solaris 2.7: with recommended patches. See:
http://sunsolve.sun.com/pubpatch
HPUX 11.0: (PA-RISC1.1 or better) with recommended patches (PHKL_18543 (mmap() patch), PHNE_16017 (cumulative ARPA Transport patch). For more information about these recommended patches, see:
http://hp.com
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.
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.
Web Port (default is 80) is the port number used by the Calendar Server to provide web (HTTP) access to users.
Admin Port (default is randomly selected at installation time) is the port number used by Calendar Server to provide web (HTTP) access to administer the server, such as commands to stop the server or list all logged-in users.
Calendar Server Administrator email address. This address uses the syntax: userid@hostname.domainname. For example, calmaster@airius.com
SMTP server host name. This is the fully qualified host name of the SMTP server that the Calendar Server will use to send email messages. For example:
calhome.airius.com
where calhome is the machine's host name and airius.com is the domain name on which the SMTP server is running.
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=airius.com, all LDAP search operations executed by Calendar Server will examine only the ou=people subtree in the o=airius.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:
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 exits by using the directory server ldapsearch utility, for example:
./ldapsearch -b o=NetscapeRoot uid=admin
Administrator Password: The password for the user account of the Administrator Bind DN described above.
On Unix, the default is:
/var/opt/SUNWicsrv/csdb
On Windows NT, the default is:
c:\Program Files\iPlanet\CalendarServer\var\csdb
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.
Install iPlanet Calendar Server 2.1.
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.
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.
Stop the Calendar Server if it is running.
Stop and restart the Directory Server.
Start the Calendar Server.
On Unix systems, the installation program uses the command /usr/bin/domainname to identify the associated domain name of your system. To verify that this setting is correct, at the command prompt, type:
domainname
The above command should return the domain name of your system correctly. If this is not the case, set the domain name by typing:
domainname <your system domain name>
To customize the bundled Calendar Express to use your company logo, your company name, etc., use the Perl script provided in the uicust directory. You must have Perl5.004 or later to use this script.
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 believe that this is a badly configured machine. If you install iPlanet Calendar Server on such a machine, entries in the server.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 server.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.
Previous
