Complete Contents
Introduction
Chapter 1 Preparing for Installation
Chapter 2 Installing Netscape Messaging Server 4.1
Chapter 3 Ugrading an Existing Installation
Appendix A Installing a 3.x Directory Server
Index
Messaging 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:


Installation Process Overview
Messaging Server 4.1 uses a common installation program for performing the installation process that provides a consistent installation interface and procedure across the entire Netscape Server product set. It is the same installation program used by the other Netscape 4.x servers.

In addition, Messaging Server 4.1 provides tools for completing and upgrading your installation, for stopping and starting various server processes, migrating existing users to an upgraded server, and so forth. Instructions for using these installation tools are provided in the relevant sections of this document.

Installing Messaging Server 4.1 involves four basic steps:

  1. Gathering Your Installation Information
  2. Transferring the Messaging Server Installation Files
  3. Configuring an Existing Directory Server (This step is required only if you are upgrading or migrating an existing Directory Server installation to use with your new Messaging Serverm 4.1 installation.)
  4. Installing Messaging Server 4.1

Before You Begin the Installation
Before you begin installing Netscape Messaging Server 4.1, you should verify that the systems on which you plan to install the software meet the minimum product requirements. In addition, you should understand what the various Messaging Server components are. 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 the Messaging Server, including:

A Netscape Directory Server is required to run Messaging Server 4.1.
The Messaging Server 4.1 installation program includes Directory Server 4.0. If you do not already have a Directory Server installed, you should install Directory Server 4.0 during the Messaging Server installation process.

If you already have an existing Directory Server 3.x or 4.x installation, you must first run the dssetup utility to prepare the directory before you install Messaging Server 4.1. For more information see Configuring an Existing Directory Server.

For information about Directory Server 3.x installations, see Appendix A, "Installing a 3.x Directory Server."


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

Hardware Requirements
The basic minimum hardware requirements for a Messaging Server installation are as follows:

Note. If you are operating an existing Messaging Server 3.x in "single-copy" mode, you may need temporary disk space equal to at least double the size of the message store. If installation fails and the log reports a lack of space problem, add additional temporary disk space.

Software Requirements
Messaging Server 4.1 supports the following operating systems at the appropriate version and patch levels:


Installation Privileges
It is recommended that you install Messaging Server logged in as root (Unix) or administrator (Windows NT). Superuser privileges (root or administrator) are required for Messaging Server 4.1 installations if you plan to use the default port numbers (which are less than 1024).


Installation Components
The product contains the following separate software components:

Netscape Console.

Netscape Administration Server.

Netscape Directory Server 4.0.

Netscape Messaging Server 4.1.

Netscape Messaging Multiplexor.

JMailstone and Mailstone utilities.

Note. The order in which you install and configure the various components depends on whether you are performing a new installation or an upgrade.


Using the Installation Interface
There are two installation interfaces, one for Unix platforms and one for Windows NT. On Unix, the installation program uses a text-based prompt driven interface. On Windows NT, the installation program uses a standard Windows based interface. Except for a few OS specific requirements, both interfaces follow the same general procedure and ask you to supply the same information.

Keyboard Shortcuts
In Unix, use the following keyboard shortcuts: to maneuver through the installation interface:

On Windows NT, use the following keyboard shortcuts:

Selecting Multiple Items
When the installation program offers multiple options, enter a comma-separated list of numbers to select more than one, but not all of them. For example:, if you want three out of four possible options, enter: 1,2,3 and press Enter.

Types of Installation
The Messaging Server 4.1 installation program lets you install in four basic ways:


Accounts, Groups, and Administrators
The accounts, groups, and administrators referred to in this guide are grouped into the following categories:

Directory Server Accounts
The accounts described in this section are those used with Netscape Directory Server. For more information, refer to the Netscape Directory Server documentation.

Administration Server Administrator.

Configuration Server Administrator.

Directory Manager.

Netscape Administrator User.

Server Administrator.

Suitespot Administrator.

Unrestricted User.

User Directory Administrator.

Postmaster account.

Webmail End User Admin.

Windows NT System Account
On Windows NT, you can run the Netscape servers logged in as any valid user. Usually, however, you will want to run the servers under the system account (logged in as administrator) to ensure that you have all account privileges required to manage the servers. If you log in as a user other than administrator, you may not have the privileges you need to manage the servers.

Unix System Accounts
The accounts described in this section apply only to Messaging Server installations on Unix platforms.

Administration Server User.

Messaging Server User.

Netscape User and Group.

Server User.

SuiteSpot User and Group.

System user.


Installation Guidelines
This section contains information you need and suggested guidelines you should follow as you prepare for your Messaging Server 4.1 installation:


Gathering Your Installation Information
Before beginning the installation process, it is helpful to gather the installation and configuration information you will need. The information you need will differ according to the type of installation you select. Chapter 2, Installing Messaging Server 4.1 provides three checklists for the types of installations:

Note. You will need additional preparatory information if you are upgrading to Messaging Server 4.1 from a previous version. For more information, see Chapter 3, "Upgrading an Existing Installation."


Transferring the Messaging Server Installation Files
To transfer and extract the product archive files which contain the installation program files in compressed format:

  1. Locate the Messaging Server 4.1 archive (tar or zip) file for your platform:
  2. You can find the archive file on the distribution CD or download it from the Netscape Messaging Server online site.

  3. Create a directory (such as /tmp/msg4install) on the machine that will host the Messaging Server and copy the archive file to that directory.
  4. Go to the directory where you copied the archive file and then extract the contents.
  5. On Unix, type

    tar -xvf archive.tar

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

    On Windows NT:

    Unzip the zip file (for example, m41eiu.zip ) or double-click the self- extracting .exe file if it is included as part of your installation package.

    Status messages display as the archive is unpacked.

    Note: If you do not have an existing server Directory Server installation, skip the following steps.

  6. Copy the dssetup archive file (dssetup.tar.gz on Unix or dssetup.zip on Windows NT) to a directory on the machine where you installed your existing Directory Server.
  7. On the Directory Server machine, go to the directory where you copied the dssetup archive file. For example:
  8. On Unix, type:

    root# cd /usr/netscape/temp/

    On Windows NT, type:

    cd c:\netscape\temp

  9. Unpack the dssetup file. For example:
  10. On Unix, type:

    gunzip -c dssetup.tar.gz | tar xvf -

    On Windows NT, unzip the dssetup.zip file.

    Status messages display as the archive is unpacked.


Choosing a Configuration Directory Server
All 4.x Netscape servers use an instance of the 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 Netscape servers. For more information, refer to the Netscape Directory Server documentation.

When setting up your directory severs, 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 Netscape Servers. In this way, 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.

If you are installing Netscape Directory Server 4.0 or later, you can choose it to be your Configuration Server. If you have an existing directory server installed (either version 3.x or 4.0), it is recommended that you prepare it by running dssetup. For more information, see Using dssetup (or msg4ldif) to Configure a 3.x Directory Server.

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 4.0 or later and choose it to be your Configuration Server directory, you can specify an Administration Domain. If you later want to add administration domains to an existing Configuration Server, you can use dssetup.

For example, you could host all servers for Airways US Corp. under the administration domain airius.com, and host all servers for Trainways US Inc. under the administration domain trainus.com. You can have as many administration domains as you wish. Each administration domain can have its own set of Global Preferences, such as resource editor extensions. Additionally, each administration domain can define its own default Users and Groups directory URL.

Configuration Administrator
The Configuration Administrator is a user account that has full access over all Administration domains of a configuration directory. By default, when you first install Directory Server 4.0 and choose it be a Configuration Server directory or when you prepare an existing LDAP server to be a Configuration Server, a Configuration Administrators group is created that has full access to all the Administration Domains.

Additionally, a Configuration Administrator account is created whenever you first install Netscape Directory Server 4.0 or later and choose it to be your Configuration Server. If you want to add configuration administrators to an existing Configuration Server, you can use dssetup to add any new administrators you have added to the Configuration Administrators group.

If you run the dssetup utility to prepare an existing Directory Server for designation as your Configuration Server, you specify a Configuration Administrator account.

Users and Groups Server
For optimal performance, when setting up Messaging Server, it is recommended that you specify one directory server as the configuration directory and another directory server for Users and Groups.

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

If you want to specify something other than the what the installation program suggests, you can run dssetup on the Configuration Server directory and specify a new Users and Groups Server. You must then also run dssetup on the directory you specified as your Users and Groups Server.

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.


Configuring an Existing Directory Server
Messaging Server 4.1 is compatible with both Netscape Directory 3.x and 4.x versions. Netscape Messaging Server and Directory Server, however, need not be installed and run on the same platform. In other words, while Messaging Server 4.1 requires either Solaris 2.6, HP/UX 11.00, AIX 4.3.1 or 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 either HP/UX or Windows NT.

If you plan to use an existing Directory Server with Messaging Server 4.1, you must use the dssetup (formerly called nsds3setup) to configure it as described in the following sections.

Configuring a 4.x Directory Server
To configure a 4.0 Directory Server, you need only update the schema files. To do so, run dssetup. When you run the dssetup utility, it will ask you to specify a server-root and server-instance (server ID), administration domain, configuration serverID, and so forth.

Configuring a 3.x Directory Server
If you do not have Directory Server 3.x installed, Netscape recommends that you install Directory Server 4.0. Otherwise you can install Directory Server 3.x as described in Appendix A, "Installing a 3.x Directory Server."

If you already have Directory Server 3.x installed, read the following points and then proceed to Configuring a 3.x Directory Server:

What You Need to Know First
You will need to have the following information to configure a 3.x Directory Server for Messaging Server 4.1:

Using dssetup (or msg4ldif) to Configure a 3.x Directory Server
You can use the dssetup utility to configure a 3.x Directory Server for Messaging Server 4.1 if the Directory Server is running on either Solaris 2.5.1 or 2.6, or HP/UX 11.00. This utility performs basic configuration procedures, generates the necessary configuration files, and refreshes the Directory Server.

To configure a Directory Server 3.x for installation of Messaging Server 4.1, run dssetup from a command line prompt as follows:

  1. Shut down the Directory Server that you will be configuring.
  2. Backup (or export) your data. (This step is optional, but recommended.)
  3. Log in as root or setuid to root (Unix) or as administrators (Windows NT) on the machine hosting your Directory Server.
  4. Note: You must have superuser (or full administrative) privileges to run the dssetup command.

  5. Go to the directory where you where you unpacked the dssetup archive file as described in Transferring the Messaging Server Installation Files starting on page 21.
  6. Run the dssetup command. For example:
  7. ./dssetup

    Note: The dssetup program is not supported on some platforms (such as HP 10.10 and HP 10.20). In such cases, run instead the script version of dssetup called msg4ldif that is included as part of the installation package.

  8. Enter the required information at the prompts.
  9. Enter the information as prompted by the utility. Default values are shown enclosed in square brackets. You can accept a default value by pressing Enter, or you can type in an alternative value and then press Enter. To change a "Yes" or "No" prompt, simply type in "y" or "n" and then press Enter. Be sure to write down the values that you specify.

    Do you wish to continue [yes]

    Enter yes (or simply y to continue).

    Directory server root [/usr/netscape/suitespot]

    This is the directory where the Directory Server is installed. If you installed a new Directory Server 3.x as described in Installing a 3.x Directory Server, enter the same directory name you entered in response to the Server root prompt. This directory is the value referred to as the server-root throughout this document.

    Messaging Server schema in the directory server appears to be up to date. Do you wish to update the schema anyway [y]?

    This prompt appears only if dssetup has already been run once on this server. If you answer yes, the previous schema files are overwritten with new files.

    Do you wish to configure this directory for Server Config [y]?

    Configuration information for Netscape servers is stored on a Directory Server under an Administration domain, in the base suffix o=NetscapeRoot. Answer "yes" only if you are running dssetup on the Directory Server instance which stores the data in o=NetscapeRoot. If this is the first time you have run dssetup on this Directory Server, or if you want to set up additional Configuration Administrators or administration domains, answer yes for this Directory Server instance to be prepared for server configuration tasks.

    Do you wish to use this directory for managing Users/ Groups [y]?

    Answer yes to prepare this Directory Server instance for managing users and groups. This Users and Groups base DN will be created if it does not already exist, and the Users and Groups Administrator account will be set up with the following configurations:

    Please enter the Directory Administrator's DN [cn=Directory Manager]

    Please enter the Directory Administrator's Password

    This question is asked if you chose to prepare this server as the Configuration Server or the Users and Groups administration server (or both). This account is the Directory Manager. If you installed a new Directory Server, this is the user ID or DN you entered in response to the Unrestricted User prompt during the installation procedure. The default is cn=Directory Manager. See Directory Manager for additional information.

    Please enter the Configuration Administrator's uid [admin]

    Please enter the Configuration Administrator's Password
    Enter the Configuration Administrator's Password again to verify

    The default is admin. See Configuration Server Administrator for additional information.

    Please enter the Administration Domain under which Server Configuration will be stored [default]

    This question is asked only if you answered "yes" to the "...configure this directory for Server Config" prompt. All server configuration is managed under the suffix o=NetscapeRoot on the Directory Server used for server configuration (the Configuration Server). Enter the domain that you want used for this purpose on this Directory Server. For example, airius.com.

    Note: You can create multiple administration domains under which your server can be installed. For example, you can host servers under administration domains airius.com and acme.com.

    Users and Groups

    The following prompts display for User and Groups information:

    Users/Groups directory URL [ldap://default/o=suffix]

    This question is asked only if you answered "no" to the "...use this directory for managing Users and Groups" prompt, and "yes" to the "...configure this directory for Server Config" prompt. Enter the LDAP URL to the Users/ Groups directory server that you wish to use. For example:

    ldap://users/airius.com:389/o=airius.com

    Please enter the base suffix under which the Users/ Groups data should be setup [o=airius.com]

    This question is asked only if you answered "yes" to the "...use this directory for managing Users/Groups" prompt. Enter the base suffix that you wish to use. The base suffix will be created if it does not already exist. Anonymous search will be enabled on this base suffix.

    Please enter the Users/Groups Administrator's uid [admin]

    Please enter the Users/Groups Administrator's Password:

    This question is asked only if you answered "yes" to the "...use this directory for managing Users/Groups" prompt. This user must have write access to the users and groups directory suffix on the Directory Server. If this user ID does not exist, it will be created under the Users and Groups base DN. See User Directory Administrator for additional information. The default is admin.

  10. A summary of your settings is then displayed and you are asked if you wish to continue. If the settings are correct, enter yes to continue. If the settings are not correct, enter no and the process will exit. Restart dssetup and enter the correct values.
  11. After choosing to continue, status messages are displayed as the Directory Server starts and is configured for Messaging Server 4.1.

Manually Configuring a Directory Server
To manually configure a Directory Server for installation of Messaging Server 4.1 use the following steps:

  1. Shut down the Directory Server that you will be configuring.
  2. Backup (or export) your data. (This step is optional, but recommended.)
  3. On Unix, log in as root (or setuid to root) or on Windows NT log in as administrator on the Directory Server machine. You must have superuser privileges to run the dssetup command.
  4. Go to the Directory Server installation directory.
  5. This is the directory in which you unpacked the dssetup archive file as described in Transferring the Messaging Server Installation Files.

  6. If you are configuring a 4.0 Directory Server that you installed as your Configuration Server directory, you can skip this step and proceed to the next step. Otherwise, Edit the ldif/ds3setup.ldif file by making the following substitutions:
  7. Copy all files in the config subdirectory to the Directory Server's server-root/slapd-instance/config directory.
  8. For example, if your Directory Server is installed in the server-root is usr/netscape/server4 and the Directory Server instance is slapd- dirsrv4, you would enter:

    cp /config/* /usr/netscape/server4/slapd-dirsrv4/config

  9. Go to the server-root/instance/config directory. For example:
  10. cd /usr/netscape/server4/slapd-dirsrv4/config

  11. Edit the ns-schema.conf file by adding the following lines to the end of the file in the following order:
  12. include server-root/instance/config/ns-common-schema.conf

    include server-root/instance/config/ns-admin-schema.conf

    include server-root/instance/config/ns-legacy-schema.conf

    include server-root/instance/config/ns-mlm-schema.conf

    include server-root/instance/config/ns-value-schema.conf

    include server-root/instance/config/ns-msg-schema.conf

    Where server-root is the Directory Server's server-root directory and instance is the name of the server instance. For example:

    /usr/netscape/server4/slapd-dirsrv4

  13. Add the suffix o=NetscapeRoot to your Directory Server as follows:
  14. Start up the Directory Server.
  15. If you are configuring a 4.0 Directory Server that you installed as your Configuration Server directory, you can skip this step and proceed to the next step. Otherwise, add the entries from the installation directory's /ldif/ds3setup.ldif file that you edited in step 5 as follows:
  16. Create your Users and Groups directory server administrator:
  17. See your Directory Server documentation for details.

  18. Add the following access rules.
  19. To do so:

 

© Copyright 1999 Netscape Communications Corp., a subsidiary of America Online, Inc. All rights reserved.