Previous     Contents     Index     Next     
iPlanet Messaging Server 5.2 Installation Guide for UNIX



Chapter 1   Preparing for Installation


This chapter contains the following sections to help you prepare for a UNIX installation of iPlanet Messaging Server 5.2:



Installation Overview

iPlanet Messaging ServerTM 5.2 uses a common installation program for performing the installation process. The program provides a consistent installation interface and procedure across the entire iPlanet Server product set.

In addition, Messaging Server provides tools for completing and upgrading your installation, for stopping and starting various server processes, for migrating existing users to an upgraded server, and so on.

Before you install Messaging Server, you should verify that the systems on which you plan to install the software meet the minimum product requirements. In addition, you should have a general understanding of Messaging Server components and the directory schema used by them. If you have not already done so, you should read Chapter 1 of the iPlanet Messaging Server Provisioning Guide before proceeding with installation. It is also a good idea to plan how you want to configure the software components before you begin the installation process.

The Messaging Server installation program contains everything you need to install this release of Messaging Server, including:

  • iPlanet Messaging Server 5.2

  • iPlanet Web Server Enterprise Edition 6.0 SP 2 (Service Pack 2)

  • Netscape Administration Server 4.2

  • Netscape Directory Server 4.16

  • Netscape Console

  • iPlanet Delegated Administrator for Messaging 1.2

  • iPlanet Messaging Server Directory setup (ims_dssetup) if you have an existing Directory Server.
    Note Although this installation guide provides instructions for installing Messaging Server with Netscape Directory Server 4.16, iPlanet strongly recommends that for new deployments, Messaging Server should be installed with iPlanet Directory Server 5.1. For instructions on installing iPlanet Directory Server 5.1 with Messaging Server, first refer to Appendix A, "Installing iPlanet Directory Server 5.1."

    For existing Messaging Server deployments, you can install Messaging Server with Netscape Directory Server 4.16. If you use Class of Service or counter plug-ins, you should also install Messaging Server with Netscape Directory Server 4.16. Since you already have an existing 4.1x Directory Server installation, you must first run the ims_dssetup utility to prepare the directory before you install Messaging Server. For more information, see Configuring an Existing Directory Server.

    If you are installing both iPlanet Messaging Server and Directory Server on the same machine and at the same time (for example, in the case of an evaluation installation), you can install Netscape Directory Server 4.16 during the Messaging Server installation process. See Installation Scenarios for more information.

    Because an HA agent does not exist for iPlanet Directory Server, you cannot configure high availability with iPlanet Directory Server 5.1. Instead, you should use other solutions, such as directory replication. For more information on alternate availability solutions, see the iPlanet Directory Server Deployment Guide.

    Note that the currently planned end of service life for Netscape Directory Server 4.16 is scheduled for January 24, 2003.




System Requirements

This section outlines the minimum hardware and software requirements and installation privileges needed to install Messaging Server. You should make certain that these requirements are met before performing the installation. Refer to the iPlanet Messaging Server 5.2 Release Notes for any updates to hardware or software requirements.


Hardware Requirements

The minimum hardware requirements for Messaging Server are:

  • Approximately 500 MB of disk space for a standard installation. For production systems, you should plan at least 1 GB to support the product binaries.

  • 128 MB of RAM. For production systems, you should have a minimum of 256 MB of RAM; be sure to allocate this accordingly, depending on the size of your site and number of users.

  • Adequate space for your user mailboxes (message store), database, log files, and message queue directory. These can grow in size dramatically depending on the size of your site, so be sure to allocate space accordingly.


Software Requirements

Messaging Server is supported on Solaris 2.6, Solaris 8, and HP-UX 11.0. This guide will focus on these UNIX platforms. Please refer to iPlanet Messaging Server Installation Guide for Windows NT to install Messaging Server on Windows NT. The following patches are required with for each UNIX platform:

  • Solaris 2.6 for Sparc requires patch 105591-09 (Shared library patch for C++), patch 106613-01 (character set conversion), and other recommended patches.

    • If you install Messaging Server in the ja_JP.PCK locale, the imadmin command line utility will not work properly without the 106361-10 patch.

  • Solaris 8 for Sparc requires patch 108827-08 and 109461-02 (or later versions) in addition to the recommended patches listed in the link below.

A list of recommended patches for Solaris 2.6 and Solaris 8 can be found at the following URL:

http://access1.sun.com/patch.public/.

Additionally, ensure that in your Solaris setup, it is clearly specified how to route to hosts that are not on the local subnet:

    • The /etc/defaultrouter should contain the IP address of the gateway system. This address must be on a local subnet.

    • The /etc/resolv.conf exists and contains the proper entries for reachable DNS servers and domain suffixes.

    • In /etc/nsswitch.conf, the hosts: line has the dns keyword added.

  • HP-UX 11.0 with the following required operating system bundles and patches:

    • XSWGR1100 (HP-UX 11.0 General Release Patches, September 2000)

    • XSWHWCR1100 (HP-UX 11.0 Hardware Enablement and Critical Patches, September 2001)

    • QPK1100 (HP-UX 11.00 Quality Pack, September 2001)

    • PHCO_21902 (df(1M) cumulative patch)

    • PHCO_22314 (libc cumulative patch)

    • PHCO_23499 (LVM commands cumulative patch)

    A list of recommended patches for HP-UX 11.00 can be found at the following URL:

    http://us-support.external.hp.com/index.html/

To use the iPlanet Delegated Administrator command-line utilities, it is required that you also install the iPlanet Delegated Administrator for Messaging from the product CD or the iPlanet Web site. See the iPlanet Messaging Server Delegated Administrator for Messaging Installation and Administration Guide.

For Messenger Express access, Messaging Server requires a JavaScript-enabled browser. For optimal performance, iPlanet recommends using the following browsers:

  • Netscape CommunicatorTM 4.7 or later

  • Internet Explorer 5.5 SP2 (Service Pack 2)



Graphical Overview of the Messaging Suite

Figure 1-1 illustrates the relationships between the various products and components within the Messaging Suite.

Figure 1-1    Messaging Suite Products and Components



Installation Components


The Messaging Server suite contains the following separate software components:


Netscape Server Core

During the installation, you will have the option of installing the Netscape Server Core, which contains the products described in the following subsections:


Netscape Product Core Components (Netscape Console 4.2)

Netscape Console provides the common user interface for all Netscape and iPlanet server products. From it you can perform common server administration functions, such as stopping and starting non-SMTP servers, installing new server instances, and managing user and group information. Netscape Console can be installed stand alone on any machine on your network and can be used to manage remote servers.


Netscape Core Java Classes

The Java classes run and support the Netscape and iPlanet server product core components.


Java Runtime Environment (JRE)

The tools and binaries needed to run and support the Netscape and iPlanet server product core components.


Directory Suite

The products in the Directory Suite are described in the following subsections (For a description on iPlanet Directory Server 5.1, refer to Appendix A, "Installing iPlanet Directory Server 5.1."):


Netscape Directory Server

The Directory Server is iPlanet's LDAP-compliant server that manages directory database services and responds to requests from LDAP clients such as Messaging Server. It runs as the ns-slapd process on your machine


Netscape Directory Server Console

This is the portion of the Netscape Console designed specifically for use with the Directory Server. The Directory Server Console enables you to perform most Directory Server administrative tasks, such as starting and stopping the server, managing access control, viewing and configuring server logs, backing up and restoring directory databases, and so forth.


Administration Services

The products in the Administration Services installation component are described in the following subsections:


Netscape Administration Server

The Administration Server receives communications from the Netscape Console and passes those communications to the appropriate iPlanet server. Your site will have at least one Administration Server for each server-root in which you have installed an iPlanet server.


Administration Server Console

This is the portion of the Netscape Console designed specifically for use with the Administration Server. You can perform most Administration Server tasks through the Administration Server Console (for example, starting and stopping servers).


iPlanet Messaging Applications

The products and components in the Messaging Applications installation component are described in the following subsections. The following components make up Messaging applications:


iPlanet Message Store and Message Access (MSMA)

Messaging Server provides the foundation for unified messaging services through its universal Message Store. Access to the message store is available through multiple protocols (HTTP, POP, IMAP). The Message Access component is responsible for handling the retrieval of messages from the Message Store.


iPlanet Message Transfer Agent (MTA)

The MTA handles tasks such as routing and delivering user mail and handling SMTP authentication. The MTA provides support for features such as hosted domains, domain aliases, and server-side filters.


iPlanet Messaging Multiplexor (MMP)

The MMP is a proxy server that acts as a single point of connection to multiple instances of Messaging Server. With the MMP, large-scale mail-service providers can distribute POP and IMAP user mailboxes (as well as SMTP Proxy) across many machines to increase messaging capacity. All users connect to the single Multiplexor server, which redirects each connection to the appropriate mail server.

For information on MMP installation, see Chapter 5, "Installing the Messaging Multiplexor."


High Availability for iPlanet Messaging Server (HA)

High Availability enables server management functions such as expansion of message store capacity and backup and recovery of user folders. Messaging Server is designed to integrate with the Veritas Cluster Server 1.1 or later, Sun Cluster 2.2, Sun Cluster 3.0 U1 and Sun Cluster 3.0 U2 high availability clustering software.

For information about the various high availability models, configuration information, and installation instructions, see Chapter 4, "High Availability."


iPlanet Delegated Administrator for Messaging Command Line Utilities (iDA)

These command line utilities (CLIs) provide the capability to perform provisioning on domains, users, and groups. They also grant privileges to the Domain Administrators.



Product Hierarchy and Interaction


This section outlines dependencies within the installation components and sub-components, shows you how to determine port numbers, and describes the interaction between installation products.


Installation Component and Sub-Component Dependencies

Each Messaging Server component has multiple sub-components. There are dependencies that allow or prevent you from installing various components together. Table 1-1 shows the components and sub-component dependencies.

Table 1-1    Messaging Server Component and Sub-component Dependencies 

Sub-Components

Corresponding Component Group

Dependent on:

Netscape Server Products Core Components  

Netscape Server Products Core Components  

n/a  

Netscape Core Java Classes  

Netscape Server Products Core Components  

n/a  

Java Runtime Environment  

Netscape Server Products Core Components  

n/a  

Directory Server  

Directory Suite  

Netscape Server Products Core Components

Netscape Administration Server  

Directory Server Console  

Directory Suite  

n/a  

Netscape Administration Server  

Administration Services  

Netscape Server Products Core Components  

Administration Server Console  

Administration Services  

Netscape Server Products Core Components  

iPlanet Message Store and Message Access  

iPlanet Messaging Suite  

Administration Services Component  

iPlanet Internet Message Transport Agent  

iPlanet Messaging Suite  

Administration Services Component  

iPlanet Messaging Multiplexor  

iPlanet Messaging Suite  

iPlanet Messaging Libraries  

High Availability for iPlanet Messaging Server  

iPlanet Messaging Suite  

n/a     

iPlanet Delegated Administrator Command Line Utilities  

iPlanet Messaging Suite  

n/a  


Port Numbers

Throughout the installation program, you will choose port numbers for various services. These port numbers can be any number from 1 to 65535. Be sure to specify different port numbers to avoid any conflicts in your Messaging installation. By the end of your installation, the following port numbers will be designated:

  • Standard Directory Server LDAP port for managing and provisioning users and services (Default: 389).

  • Administration Server HTTP port for listening to the Netscape Console requests (Choose a port number that is easy to remember. For example: 55555).

  • Messenger Express (Webmail) HTTP port (Default: 80).

  • Delegated Administrator for Messaging HTTP port (Default: 8080) This port should correspond to the iPlanet Web Server User HTTP port. See the iPlanet Delegated Administrator for Messaging and Collaboration Installation and Administration Guide for more information.

The following default port numbers may be specified during the installation process; if you select Custom Installation (or if these any of these ports are in use), these port numbers can be changed:

  • POP3 (default 110)

  • IMAP4 (default: 143)

  • SMTP (default: 25)

The Administration Server must run as root if the Directory Server is going to use standard port numbers (only root authenticated user accounts can access ports lower than 1024.).
Tip It is recommended that you record all of the port numbers you specify during the installation, along with the specific component using that port number. See Table 1-2.



When and Where to Install each Product

Although the Directory Server is included, you may choose to use an existing Directory Server and not install the one that is included with the Messaging Server. If you do so, you must run ims_dssetup (See Running the ims_dssetup Utility.) against that existing Directory Server prior to installing the Messaging Server. See Configuring an Existing Directory Server for more information.

The iPlanet Web Server must be installed on the same machine as the Delegated Administrator, but the Messaging Server can be installed on a separate machine. Since the existence of the Web Server is required for the Delegated Administrator, you must install the Web Server before you install the Delegated Administrator.

The Delegated Administrator should be installed immediately after the Messaging Server; if you start to provision the Messaging Server before installing the Delegated Administrator, you may encounter some complications in the Delegated Administrator installation.

Tip It is recommended that you install the Messaging Server first, then the Web Server, then the Delegated Administrator.



Required Information for the iPlanet Delegated Administrator for Messaging Installation

The Delegated Administrator requires the following information from the Messaging Server installation; make sure you accurately record this information in Table 1-2, before or during the Messaging Server installation. Relevant iPlanet Delegated Administrator information to note during Messaging installation includes:



Configuring an Existing Directory Server

This section provides information for configuring an existing Directory Server in preparation for a Messaging Server installation. If you do not have an existing Directory Server, or you want to install the Directory Server that comes with the Messaging Server, you do not need to read this section.
Note To install iPlanet Directory Server 5.1 with Messaging Server, refer to Appendix A, "Installing iPlanet Directory Server 5.1."


Messaging Server is compatible with Netscape Directory Server 4.1x. Messaging Server and Directory Server need not be installed and run on the same platform. While Messaging Server requires Solaris 2.6, 8, HP-UX 11.00, or Windows NT 4.0, the Directory Server can run on any platform on which it is supported. For example, a Directory Server running on Solaris can provide LDAP services to a messaging server running on HP-UX or Windows NT.

Note If you plan to use an existing Directory Server with Messaging Server, you must use the ims_dssetup program to configure it as described in Running the ims_dssetup Utility.



Choosing a Configuration Directory Server

All iPlanet servers use a Directory Server to store configuration information. This information is stored in the o=NetscapeRoot directory tree. Your configuration directory is the Directory Server that contains the o=NetscapeRoot tree used by your servers. For more information, refer to your Directory Server documentation.

When setting up your Directory Servers, you will want to centralize the administrative configuration settings on a single LDAP server and use it to host the configurations of any number of iPlanet Servers. When you open Netscape Console for any server, you will see all the other servers that are using the same LDAP server as the Configuration Server directory.


Administration Domains

On any configuration LDAP server, you can group your servers under different administration domains for increased manageability. When you first install a Directory server and choose it to be your Configuration Directory Server, you can specify an Administration Domain. If you later want to add administration domains to an existing Configuration Directory Server, you can use the Administration Console.

The administration domain allows you to logically group iPlanet servers together so that you can more easily distribute server administrative tasks. A common scenario is for two divisions in a company to each want control of their individual iPlanet servers. However, you may still want some centralized control of all the servers in your enterprise. Administration domains allow you to meet these conflicting goals.

Administration domains have the following qualities:

  • All servers share the same configuration directory, regardless of the domain that they belong to.

  • Servers in two different domains may use two different user directories for authentication and user management.

  • The configuration directory administrator has complete access to all installed Netscape servers, regardless of the domain that they belong to.

  • Each administration domain can be configured with an administration domain owner. This owner has complete access to all the servers in the domain but does not have access to the servers in any other administration domain.

  • The administration domain owner can grant individual users administrative access on a server by server basis within the domain.


Choosing a Users and Groups Directory Server

When setting up Messaging Server, it is recommended that you specify one Directory Server as the Configuration Directory Server and another Directory Server for Users and Groups for increased manageability.

When you install the Messaging Server, there are two ways to specify your Users and Groups Directory Server:

  • Use an existing Users and Groups Directory Server with your Messaging Server installation.

  • Install a new version of the Users and Groups Directory Server with your Messaging Server installation.
    Note After completing the installation, you can use Netscape Console to change the Users and Groups Directory that your Messaging Server uses, regardless of what was specified during the installation.




Types of Installations

The Messaging Server installation program lets you install in four basic ways:

  • Express Installation. This type of installation performs a "quick" installation. Because most options at this level are automatically configured with default values, it is recommended for novice users. Use Express Installation if you want to evaluate Messaging Server.

  • Typical Installation. This type of installation is more complex than the Express level. Some options are automatically configured with default values, but some options require that you choose or enter the value you want to use. Typical installation is recommended for intermediate users or for any installation that does not require custom configuration. Use this type of installation if you are performing a normal installation of Messaging Server.

  • 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. Use this type of installation if you want to perform advanced activities during installation such as specifying SMTP and IMAP 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 Messaging Server. This feature is especially useful for installing several servers in your enterprise. Instructions on how to run this type of installation are described in Silent Installation.



Suggested Guidelines

This section contains suggested guidelines you should follow as you prepare for your Messaging Server installation.

  • Installation Privileges. You must install Messaging Server logged in as root.

  • Host and Domain Names. The iPlanet installation utilities assume that your host and domain names are defined correctly in your UNIX system files. Make sure that the hostname command returns the correct information before installing iPlanet servers. If your system does not support the domainname command, check the domain name in the /etc/resolv.conf file.

  • Server-root Directories. The Messaging Server, Directory Server, 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.

  • Create nobody for HP-UX installations. Prior to an HP-UX installation, you will need to create a user called nobody who has no privileges, does not reside in any group, is not root, and does not have a home directory. The user, nobody, should not be a user in your Messaging or Directory Server.

  • Resource Contention. To avoid resource contention between the servers, it is recommended that you install the Directory Server on a different machine than where you install Messaging Server. This is not necessary for single system installations, like an evaluation installation.

  • Hardened Solaris Machines. To install Messaging Server on a hardened Solaris machine, create a dummy file called libx11.so.4 in a directory (such as /tmp). Add that directory to the LD_LIBRARY_PATH variable prior to installation.

  • High Availability installation. High availability for the Messaging Server is not installed by default; be sure to select High Availability Components from the Custom Installation menu if you install Sun Cluster 2.2 or Veritas Cluster Server 1.1 or later. For specific instructions, see Chapter 4, "High Availability."
    Note If you install Sun Cluster 3.0 U1 or U2, you should select Custom Installation as your installation type, however you should not select High Availability components option during Messaging Server installation. See Chapter 4, "High Availability."


    Because an HA agent does not exist for iPlanet Directory Server, you cannot configure high availability with iPlanet Directory Server 5.1. Instead, you should use other solutions, such as directory replication. For more information on alternate availability solutions, see the iPlanet Directory Server Deployment Guide.

  • MMP installation. The MMP is not installed by default; be sure to select it from the menu if you want it installed. You may use either the Typical or Custom installation to install the MMP. See Chapter 5, "Installing the Messaging Multiplexor."



Installation Steps

The basic steps that should be followed for installing Messaging Server and its suite of products are listed below:

  1. Review System Requirements and verify that they have been met.

  2. Record the information you'll need to complete the installation based on the type of installation you want to perform (for example, IDs, passwords, and so forth) as described in Table 1-2.

  3. Determine whether you want to use an existing Directory Server or install the Directory Server that is included with the Messaging Server.

    1. If you choose to use an existing Directory Server, you must run the ims_dssetup script on this existing Directory Server before you install Messaging Server. For more information, see Running the ims_dssetup Utility.

    2. If you do not have an existing Directory Server, you must install the Directory Server provided with the Messaging Server installation. Messaging Server installation creates only one instance of the Directory Server.
      Note If you install the Directory Server that comes with the Messaging Server, you do not need to run the ims_dssetup.pl program that is described in Running the ims_dssetup Utility; this utility is only used for a pre-existing Directory Server to prepare it for the Messaging Server installation.


  4. Make sure that the installation files are available, either from the product CD or downloaded from the iPlanet Web site. See Transferring Messaging Server Installation Files for more information.

  5. Run the setup program to perform the installation. See Chapter 2, "Installation Instructions" for more information on how to run the setup program.

  6. Verify that the installation was successful.



iPlanet Messaging Server Installation Checklist

Use Table 1-2 to record installation and configuration values during the installation process. This information will be particularly helpful when installing other Messaging products and for subsequent installations of Messaging Server.

Table 1-2    iPlanet Messaging Server Installation Checklist 

Parameter

Specified During

Value

Location of Product CD Image

 

The path of the install-binaries from the installation CD or from the iPlanet Web site.  

Example: /usr/temp/msg51opt



install-binaries:_____________________________  

Directory Manager DN  

Messaging Server Installation: Directory Manager Settings  

Directory Manager DN Example (default): cn=Directory Manager
Password: iPlAnEt1

Directory Manager DN: _______________________

Password: _________________________________  

Directory Server Identifier, Port, and Suffix  

Messaging Server Installation: Directory Server Settings  

Server Identifier Example: budgie
Server Port Example: 389 (default)
User Suffix Example: o=siroe.com

Server Identifier ___________________________
Port __________________________
Suffix____________________  

Directory Host and Domain Name  

Messaging Server Installation: Directory Server Settings  

Host and Domain Name Example: budgie.siroe.com


Host Name Identifier _______________________  

Administration Server Port for Messaging and Directory Servers  

Messaging Server Installation: Administrator Server Port Selection

Also specified in the Web Server installation  

Administration Port Example: 5000


Administration Port Number: ____________________  

Messaging Server Ports
SMTP
Webmail (Messenger Express)
POP3
IMAP4  

Messaging Server Installation: Messaging Server Ports  

Ports Example (defaults):
POP3: 110                              POP3: ____________
IMAP4: 143                           IMAP4: ____________
SMTP: 25                               SMTP: ____________
Webmail: 80                           Webmail: ___________  

Messaging Server Fully Qualified Host Name  

Messaging Server Installation: Messaging Server Host and Domain Name  

Fully qualified example: budgie.siroe.com
Host example: budgie
Domain example: siroe.com

Messaging Server Fully Qualified Host Name:

_________________________________________  

Messaging Server Service Administrator  

Messaging Server Installation: Service Administration  

User example (default): ServiceAdmin
Password example: iPlAnEt1

Messaging Server Services User: ________________

Password: _________________________________  

Postmaster User Account  

Messaging Server Installation: Postmaster Address  

Postmaster Address example: pma@siroe.com

Postmaster Address: _________________________  

Delegated Administrator for Messaging running on Web Server Port  

Messaging Server Installation: Messaging Server Delegated Administration Host and Port (Web Server installation)  

Delegated Administration Host and Port example:
Host Name: budgie.siroe.com
Port: 8080 (default)

Delegated Administration Host Name: ___________

Port Number: ________________________________  

Web Server Port  

Delegated Administrator for Messaging Product Installation (Web Server installation)  

Administration Server Port for Web Server Example: 8000

Administration Server Port for Web Server:
Port Number:________________________________  

Web Server Configuration Directory  

Delegated Administrator for Messaging Product Installation  

Example: /usr/netscape/server4/https-budgie/ \
config

Directory:______________________________________  


Previous     Contents     Index     Next     
Copyright © 2002 Sun Microsystems, Inc. All rights reserved.

Last Updated February 26, 2002