This page was last updated on January 30, 1999.
This document describes the steps required for installing Messaging Server 4.0 on a UNIX platform. For information about known problems with this release, please see the release notes.
This document covers the following topics:
Step 1: Gathering Your Installation
Information
Express Installation
Checklist
Typical Installation
Checklist
Custom Installation Checklist
Step 2: Transferring the Messaging Server Installation Files
Step 3: Installing a Directory Server
Step 4: Configuring a 3.x Directory Server for Messaging Server 4.0
Step 5: Installing the Messaging
Server
Express Installation
Typical Installation
Custom Installation
Fast Multiple Installations
Upgrading an Existing Installation
Replacing an Existing Messaging
Server
Upgrading from a 3.x Server to a 4.0
Server
Upgrading an Older 4.0 Server to a Newer
4.0 Server
Migrating Mailboxes and Message Queue With the upgrade
Utility
Migrating Users in a Multi-Partition
Environment
Migrating Specific Users
Specifying Non-Default Directories
Repeating Message Migration
Upgrade Completed the Process With
Errors
Upgrade Failed or Was Halted Before
Completion
A Netscape Directory Server is required to run Messaging Server 4.0. If you do not have a Directory Server, you can install one as described in Installing the Directory Server.
Once you have a Directory Server, the Messaging Server archive files contain everything you need to install this release of the Messaging Server, including:
This release of Netscape Messaging Server 4.0 supports the following platforms:
The requirements are as follows:
Hardware Requirements:
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, additional temporary disk space is needed.
Software Requirements:
Solaris 2.6 with recommended patches
See: http://sunsolve.sun.com/sunsolve/pubpatches/patches.html
Accounts, Groups, and Administrators
The following accounts, groups, and administrators are referred to in these installation procedures:
This is the user ID or distinguished name of the administrator who has
administration privileges for the Netscape Registry and Netscape Console. This
must be a unique user ID.
(Netscape also recommends that for some servers, such as Messaging Server, you use server-specific user IDs rather than the default Netscape user ID. For example, Netscape recommends that Messaging Server be run under the user ID mailsrv rather than nsuser. If you follow this recommendation, then mailsrv becomes the Messaging Server User that is described below.)
You can use the following navigation controls to maneuver through the installation interface:
The following section contains pertinent information you should consider when determining your installation configuration.
This release of Messaging Server 4.0 provides a Common Install program for performing the installation process. Common Install provides a consistent installation interface and procedure across the entire Netscape server product set and is the same installation program used by the other Netscape 4.0 servers.
Also provided in this release of Messaging Server 4.0 are 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.
There are five basic steps involved for installing Messaging Server 4.0:
The following sections provide detailed information about these steps.
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 level you select. You can choose one of three installation levels:
This installation level is more complex than the Express level. Some
options are automatically configured with default values, but some require
that you choose and enter the value you wish to use. This level is recommended
for intermediate users or for any installation that does not require custom
configuration.
This is the most complex level. You must choose and enter all option
values. This installation level is recommended for expert users only.
The sections below provide checklists of the information you need to complete the various installation levels. There are three checklists corresponding to the installation levels. The three checklists are as follows:
You will need the following information to complete the installation procedure for any of the installation levels:
Determine the installation level you want to use: Express, Typical, or Custom.
Determine the name and path of the directory in which you want the server(s)
to be installed. For example, /usr/netscape/server4. Be sure that
this is a different directory than the Directory Server 3.x server-root, if
installed on the same machine.
This directory will contain your message data store and should be on a storage device large enough to handle the load. For example, a high-capacity hard drive with adequate free space, or a RAID array.
Choose one or more of the following:
A fully qualified host name has the following syntax:
Where airius.com is the domain name.
This is the UNIX user account and group under which the Administration Server
and Messaging Server will run. See Messaging Server
User for additional information. (This prompt is not displayed if this
account and group already exist.)
Netscape Servers use an LDAP-based Directory Server for resource
administration. This server is called the Netscape Registry Server. You can
access it with the same LDAP URL you entered for the Netscape Registry when
installing the Directory Server.
The URL must have the following syntax:
NOTE: You must grant write access to this entry before you can install the Administration and Messaging Servers. (If you run nsds3setup as described in Configuring a 3.x Directory Server for Messaging Server 4.0 this is done for you.)
This is the user ID or distinguished name of the administrator who has access
privileges for the Netscape Registry and Console. See Netscape Administrator for additional information.
This is the entry in the Netscape Registry where management information for
your servers is to be stored. Registry information is entered when preparing a
Directory Server 3.x for Messaging Server installation or when installing
Directory Server 4.x. You must grant write access to this entry before you can
install the Administration and Messaging Servers.
This is the user account to which error and informational messages are to be
sent. See Postmaster account for additional
information. (This prompt is not displayed if this account already exists.)
This address should use the following syntax:
In addition to the information in the Express Checklist, you need the following information to complete the Typical Installation procedure:
NOTE: Netscape recommends that you install both Core Package subcomponents.
If you have elected to install the Administration Suite, you can specify one
or both of the following subcomponents:
NOTE: Netscape recommends that you install both Administration Suite subcomponents.
If you have elected to install the Messaging Suite, you can specify one or
more of the following subcomponents:
NOTE: Typically, you will install just the Messaging Server subcomponent.
The Administration Server must listen on a reserved port not used by any of
your other Netscape servers. Select a port number with a value between 1024
and 65535.
NOTE: The default value provided by the installation program is randomly selected from the available ports on your system. To select a different port, you must enter that number explicitly during the appropriate phase of the installation process. Netscape recommends that you select a number that is easy to remember, and that you write down your selection for future reference.
This is the user ID that has administration privileges for the Administration
Server. See Administration Server User for
additional information.
NOTE: The Administration Server no longer controls most of the Messaging and Directory Server configuration. That functionality is now in the startconsole application.
In addition to the information in the Basic/Express Checklist and Typical Checklist, you will need the following information to complete the Custom Installation procedure:
The default for both is admin.
This is the domain name associated with the Messaging Server. This entry
ensures that messages sent to this domain are routed properly. The domain name
must be a fully qualified domain name (FQDN). For example:
This is the name of the machine on which the Server resides and will execute
commands. Each Messaging Server host name must be unique.
This is the user that Messaging Server 4.x will run as. The default is
mailsrv. See Messaging Server User for
additional information.
This is the name by which this instance of the Messaging Server will be
identified. Each instance of the Messaging Server must have a unique
identifier. For example, msgsvr4-a. Server identifiers must be
entered as a single, unqualified element without use of a period (.)
character. For example, both msgsvr4.arius.com and
msgsvr4.primary are not allowed, but msgsvr4-primary is
allowed.
Note that entering your own identifier here does not cause the defaults shown in subsequent prompts, such as queue and store directory, to change. Therefore, if you enter a non-default identifier here, you must also enter the appropriate non-default values at those prompts that make use of the server identifier.
This is the network port on which the Messaging Server listens for SMTP
connections. By default, this is port 25.
This is the network port on which the Messaging Server listens for POP3
connections. By default, this is port 110.
This is the network port on which the Messaging Server listens for IMAP4
connections. The default is port 143.
This is the path to the temporary holding area (message queue) for receiving
incoming messages before they are stored in the targeted mail folder/mailbox.
You must specify the absolute pathname for this directory.
This is the path to the message storage area to which messages will be written
and from which they will be retrieved. You must specify the absolute pathname
for this directory.
This is the user account to which error and informational messages are to
be sent. By default the postmaster account is created as
cn=postmaster under the user/groups suffix. See Postmaster account for additional information.
Step 2: Transferring the Messaging Server Installation Files
Where archive identifies the platform archive file you chose to transfer. Note the dash at end of the command.
Status messages are displayed as the archive is unpacked.
For example,
Status messages are displayed as the files are transferred. Several subdirectories are created.
The filename of this archive is in the form:
For example, to copy the archive file for the Solaris operating system to a /tmp/ds3archive directory on the machine hosting the Directory Server:
For example:
Status messages are displayed as the files are unpacked.
Step 3: Installing a Directory Server
You must have Netscape Directory Server 3.x installed before you can install the Messaging Server. Netscape recommends that you upgrade to Directory Server 3.12 if you have not already done so. For more information, see the release notes. Netscape Directory Server 3.12 is available from the download site at http://home.netscape.com/download/.
The following is a basic outline of the Directory Server installation process. For detailed instructions on how to perform more complex installations, refer to the Directory Server Readme and installation documentation.
Note: Part of the Directory Server installation process is specifying the SuiteSpot user and group. The default user and group is nobody because they are assumed to exist on all Unix systems. However, Netscape recommends creating a special user and group for this purpose rather than accepting the default. To specify a non-default user and group, you need to create the user and group before beginning the installation process.
Directory Server installation archives can be copied from a distribution CD or downloaded from the Netscape Products web site (http:/home.netscape.com/download).
There is a separate archive file for each supported operating system. The archive files have names that follow the pattern: archive.tar.gz, where archive identifies the operating system.
These instructions assume that you have transferred the Directory Server archive to an installation directory named /tmp/ds3archive.
Note the dash at end of the command.
Begin the installation process by running the Directory Server setup program from the operating system command line, as follows:
Be sure to write down the values that you enter. You will use these values again in the Messaging Server installation process.
Default values are shown enclosed in square brackets. You can accept the default value by pressing Enter, or you can type in an alternative value.
This is the server-root directory into which Directory Server will be installed. If you are installing Directory Server 3.x on the same machine as the Administration and Messaging 4.0 Servers (which is not recommended), you must install the Directory Server in a server-root that is different from the server-root used for the Messaging and Administration servers. The directory you specify here is the value referred to as the server-root throughout the rest of these installation instructions.
This is the fully qualified host name of the Directory Server machine. For example, dirsrv1.airius.com.
This is the default user ID under which servers are to be run. Netscape recommends that instead of accepting the proposed default that you create a special user and group for running Netscape servers. The SuiteSpot user must already exist before you enter that user ID here. See SuiteSpot User and Group for additional information.
This is the default group which will own files shared by various servers. The SuiteSpot group must already exist before you enter it here. See SuiteSpot User and Group for additional information.
At this point, files are extracted.
This is the port the Administration server is to access. It must be unique port that is not used by any other application. You can choose any port between the numbers 1024 and 65535.
This is the user ID under which the Administration Server is to run. Netscape recommends that you accept root. These instructions assume that you are using root. See Administration Server User for additional information. Note that the Administration Server User does not have the same functionality in Directory Server 4.0x as in Directory Server 3.x. You may wish to review the Administration Server User definition to determine whether to run the Administration Server User as root.
This prompt asks if you have Directory Server version 2.x instance that you wish to upgrade to this 3.x version. If you do not have a 2.x Directory Server, accept the default and proceed. If you do have a 2.x server, enter the path to the 2.x installation.
Password:
Password (again):
This user is to have administration privileges on the Administration Server. For 3.x servers this is the Suitespot Administrator, for 4.x it is the Configuration Administrator. The default for both is admin, but you are free to select any user ID you wish. This user ID has to already exist. See Suitespot Administrator or Configuration Administrator for additional information.
At this point the installation process starts up the Directory Server. Status messages are displayed.
The URL for administering the Directory Server through a web browser is reported.
The installation procedure then loads the browser and the appropriate URL. (If you will be using a web browser from a Windows or Macintosh computer, or a remote system, enter NONE here and then manually launch the browser and go to the URL reported above.)
This is the hostname of the machine on which the Directory Server is running. For example, dirsrv1.airius.com.
This is the port that the server instance is to use. The port you select cannot be used by any other application on this machine. The default is 389.
This is a unique name that identifies the server instance. By default this is the machine name without the domain name (dirsrv1), but it can be any name you choose. If you have more than one instance on the same machine, each must have a different identifier.
This is the user ID for the account under which the Directory Server is to run. You can leave this blank, in which case it will run as root.
Password:
Password (again):
This is the administrator for all 3.x servers. This prompt is only used to configure this Directory Server instance for SuiteSpot 3.x. When installing Messaging Server 4.0, Netscape recommends leaving this prompt blank.
This is the root of an LDAP tree under which your directory information is stored. The default is o=Airius.com, but you should change this to the suffix you use for your directory root.
Password:
Password (again):
This is the Directory Manager. The default is cn=Directory Manager. See Directory Manager for additional information.
You can also use this web page for additional Directory Server tasks as needed.
At this point, no additional Directory Server configuration steps are required before proceeding to Step 3.
Note however, that if you are using a Directory Server 3.x you must prepare that Directory Server for the Administration and Messaging Server 4.0 installation after you have transferred the Messaging Server files. The nsds3setup utility is provided for this purpose. See Step 4: Configuring a 3.x Directory Server for Messaging Server 4.0 for details.
For additional instructions on Directory Server installation and further configuration refer to the following document(s):
Step 4: Configuring a 3.x Directory Server for Messaging Server
4.0
Messaging Server 4.0 requires a Netscape Directory Server. Messaging Server can use any Netscape Directory Server regardless of the operating system platform or version the Directory Server is running on. In other words, while Messaging Server requires either Solaris 2.6, or HP/UX 11.00, the Directory Server platform does not matter.
If your Directory Server is version 3.x, you must configure it for Messaging Server 4.0.
You will need to know the following information to configure a 3.x Directory Server for Messaging Server 4.0:
This is the user ID or distinguished name of the administrator who has
administration privileges for the Netscape Registry and Netscape Console. This
must be a unique user ID.
This is the password for the user account specified as the Netscape
Administrator.
You can use the nsds3setup utility to configure a 3.x Directory Server for Messaging Server 4.0 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.0, run nsds3setup from a command line prompt as follows:
(This step is optional, but recommended.)
You must have superuser privileges in order to run the nsds3setup command.
This is the directory on the Directory Server in which you unpacked the msgldif archive file as described in steps 5 through 8 of the "Transferring the Messaging Server Installation Files" section. In these instructions, the example we are using is /tmp/ds3archive.
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" followed by Enter. Be sure to write down the values that you specify.
Enter yes (or simply y to continue.
This is the directory where the Directory Server is installed. If you
installed a new Directory Server as described in Step 2, 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
the rest of these installation instructions.
This prompt appears only if nsds3setup has already been run once on
this server. If you answer yes, the previous schema files are overwritten with
new files.
Configuration information for Netscape servers is stored on a Directory Server
under an Administration domain, in the base suffix o=NetscapeRoot. If
this is the first time you have run nsds3setup on this Directory
Server, or if you want to set up additional Configuration Administrators or
Administration domains, answer yes for this Directory Server 3.x instance to
be prepared for server configuration tasks.
Answer yes, to prepare this Directory Server 3.x instances for managing users
and groups. This Users/Groups base DN will be created if it does not already
exist, and the Users/Groups Administrator account will be set up.
Please enter the Directory Administrator's Password
This is asked if you chose to prepare this server for either server
configuration of users and groups administration (or both). This is the
Directory Manager. If you installed a new Directory Server as described in
Step 2, this is the user ID you entered in response to the Unrestricted
User prompt during the ns-setup procedure. The default is
cn=Directory Manager. See Directory Manager
for additional information.
Please enter the Configuration Administrator's Password
Enter the Configuration Administrator's Password again to verify
This is only asked 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. Enter the domain that you
want used for this purpose on this Directory Server. For example,
airius.com. Note that 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.
Please enter the base suffix under which the Users/Groups data should
be setup [o=Airius.com]
This is only asked if you answered "yes" to both the "..use
this directory for managing Users/Groups " and "..configure
this directory for Server Config" prompts. 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 Password:
This prompt is only displayed 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/Groups base DN. See Users Directory
Administrator for additional information.
If the settings are correct, enter yes to continue. If the settings
are not correct, enter no and the process will exit. Restart
nsds3setup and enter the correct values.
After choosing to continue, status messages are displayed as the Directory Server is configured for Messaging Server 4.0.
Manually Configuring a Directory Server 3.x
To manually configure a Directory Server 3.x for installation of Messaging Server 4.0, follow these steps:
(This step is optional, but recommended.)
You must have superuser privileges in order to run the nsds3setup command.
This is the directory on the Directory Server in which you unpacked the msgldif archive file as described in steps 5 through 8 of the "Transferring the Messaging Server Installation Files" section.
All server configuration is managed under the suffix o=NetscapeRoot on the Directory Server used for server configuration. Enter the domain that you want used for this purpose on this Directory Server. Note that 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.
For example, if this Directory Server's server-root is
/usr/netscape/suitespot and the instance is slapd-dirsrv1:
For example:
Where server-root is the Directory Server's server-root and instance is the name of the server instance. For example, /usr/netscape/suitespot/slapd-dirsrv1.
See your Directory Server documentation for details if needed.
See your Directory Server documentation for details if needed.
See your Directory Server documentation for details if needed.
Step 5: Installing the Messaging Server
Once a Directory Server 3.x instance is up and running and the Messaging Server archive files have been unpacked, you are ready to begin installing the Messaging Server.
Note: If you have already installed Messaging Server 4.0 once, and saved the cache file, you can use that cache file to speed up of the installation process of subsequent Messaging Server installations. See Fast Multiple Installations for details.
In the installation directory in which you unpacked the Messaging Server files (/tmp/msg4install), is the setupinstallation program.
Note: The installation steps below describe a typical installation pattern. To some extent, the choices you make determine the subsequent prompts that are displayed. Therefore, the prompts that you see during your installation may not be exactly the same as those shown below.
To install Messaging Server 4.0, follow these steps:
As part of the installation process, you will be asked if you agree to the terms listed in this file.
You must have superuser privileges (that is, be logged in as root) to run the installation program.
Run the setup program from the operating system command line.
The installation program Welcome Message is displayed.
Press Enter to continue. The license agreement is displayed.
Read the license agreement and enter y to accept it and continue.
Note that you have to actually enter y because the default is
no.
Select the software that you want to install. The default is Messaging Server
and associated Console. Or you can enter 2 to just install the
Netscape Console without Messaging Server. (These instructions assume that you
select to install both Messaging Server and the Console.)
Select the installation level of detail that you wish to use. The same
software is installed for each level. The difference between the levels is the
number of configuration options you are asked to specify rather than have
default values automatically entered for you. The three levels are:
After selecting the installation level, you are prompted to enter your installation and configuration information, according to the level you selected. For more detailed descriptions of what to enter for each prompt, refer to the appropriate installation checklist(s) earlier in this document.
This is the directory where the Messaging and Administration Server software
is to be installed. Do not specify the same server-root that is used by
Directory Server 3.x. (You can create multiple server roots by installing into
multiple directories on the same machine.)
Choose which components you want to install. The prompts you see will vary
according to the choices you make.
The choices are:
Netscape Messaging Server Mailstone Tool which is a Messaging Server performance monitoring utility.
This is the fully qualified host name of the machine where the Messaging
Server is to be installed. For example, msgserver.airius.com.
System Group [nobody]:
This is the same as the Netscape user and group. Netscape recommends that
rather than using the nobody default, you create a new user ID and
group for running Messaging Server. For example, mailsrv for the user
and nsgroup for the group. See Messaging Server
User for additional information.
The group should be same as the one used for the Directory Server so that Messaging Server has access to the server root's configuration and security data. For security reasons, Netscape recommends that this user ID not be given any privileges elsewhere on the system. See Netscape User and Group for additional information.
This is the URL of the Directory Server that this instance of Messaging Server is
to use. This must be entered in the form:
ldap://hostname:port.
This is the domain of your organization, for example airius.com. You
must have already granted write access to this domain. (If you ran
nsds3setup write access to this domain was granted for you.) Netscape
recommends that you accept the proposed default value.
Password:
This is the Configuration Administrator ID that you entered when you ran
nsds3setup. See Configuration Administrator
for additional information.
Password:
This is the Users and Groups administrator. This user must have write access
to the users and groups directory suffix on the Directory Server. See Users Directory Administrator for additional information.
This is the port that the Administration Server is to use. It must be a unique
port that no other application uses.
This is the user ID under which the Administration Server is to run. This
should be different than the ID used to run Messaging and other servers.
Netscape recommends that you run the Administration Server as root so that you
will be able to use the Console to start and stop servers. See Administration Server User for additional information.
Note that the Administration Server User
does not have the same functionality in Messaging Server 4.0x as in Messaging Server 3.x.
You may wish to review the Administration Server User definition to determine
whether to run the Administration Server User as root.
This prompt is only displayed if you already have one or more 3.x or 4.0
Messaging Servers installed on this machine in other server-roots. If you
answer yes:
Note: If your 3.x server uses non-default directories to store mailboxes and message queues, do not migrate them at this time. Instead, wait until installation is complete, and then run the upgrade utility from the command line as explained in Migrating Messages With the upgrade Utility.
A server instance must be created before Messaging Server can be used.
This is the Messaging Server User and Messaging Server will run under this
user ID. This should be a different user ID than the IDs entered for Netscape
User (nobody) and the Administration Server (root). This
user ID must already exist. In order to prevent possible security problems,
Netscape recommends that this user be a member of the Netscape Group that you
specified earlier. See Messaging Server User for
additional information.
(This prompt is not displayed if a postmaster account has already been
created.) See Postmaster account for additional
information.
(This prompt is not displayed if a valid postmaster account already exists.)
This is the user ID that serves as the postmaster account. If the account you
specify is stored on the directory server used by this Messaging Server, you
need only enter the user ID. For example, mailmaster. If the account
resides on a different Directory Server or in a different domain, then you
must enter a fully-qualified email address. For example,
mailman@airius.com. The user IDs listed for the postmaster account do
not yet have to exist. See Postmaster account for
additional information.
(When performing a Typical installation, this prompt is only displayed if the
default port (25) is already in use.)
This is the port number for the SMTP daemon. The port number specified here must be a unique port that no other application is using. If the port is in use, you can either enter a different port, or accept the proposed default in which case you must kill whatever process is currently using that port before starting up Messaging Server.
If you choose (or accept) a port that is already in use, the installation procedure will warn you and ask if you wish to continue. You can use Control-B to go back and select a different port. If you continue, you will not be able to start up this Messaging Server instance until the application using the port you specified has been shut down.
(When performing a Typical installation, this prompt is only displayed if the
default port (143) is already in use.)
This is the port number for the IMAP daemon. The port number specified here must be a unique port that no other application is using. If the port is in use, you can either enter a different port, or accept the proposed default in which case you must kill whatever process is currently using that port before starting up Messaging Server.
(When performing a Typical installation, this prompt is only displayed if the
default port (110) is already in use.)
This is the port number for the POP3 daemon. The port number specified here must be a unique port that no other application is using. If the port is in use, you can either enter a different port, or accept the proposed default in which case you must kill whatever process is currently using that port before starting up Messaging Server.
(This prompt is only displayed if sendmail is using a port designated
for Messaging Server.) If sendmail is running and you enter
yes to stop it, then sendmail will be halted and Messaging
Server 4.0 will be installed and started up. If you enter no,
Messaging Server 4.0 will be installed and but it will not be started up. You
will later have to manually halt sendmail and then start Messaging
Server.
A summary of the choices you have made is now displayed for your review. You
can use Control-B to return to previous screens to make corrections.
When the list is correct, press Enter to continue.
Installation status messages are displayed as the servers are installed and configured.
Enter yes (or simply y) to continue.
Status messages are displayed as Messaging Server 4.0 is started.
This refers to the install.inf cache file that was created by the
setup program. If you keep this file, you can use it as an installation
template for other Messaging Server instances as described in Fast Multiple Installations. But since this file
contains user IDs and password that you may want to keep secure, the default
is to delete it.
For an Express Installation, you must answer the following prompts (default answers are given in brackets):
For a Typical Installation, you must answer the prompts listed for an Express Installation plus the following additional prompts (default answers are given in brackets):
For a Custom Installation, you must answer the prompts listed for both an Express and Custom Installation plus the following additional prompts:
If you already installed a Messaging Server 4.0, and you chose to save the cache file, you can use that file to quickly install additional Messaging Server instances. All of your responses to the installation prompts are recorded in the cache file. When you use a cache file in a new installation you are not asked any questions. Instead, all of that cache file responses are automatically applied as the new installation parameters.
The cache file from an installation is saved under the name install.inf in the server-root/setup directory. For example, if you installed the server into /usr/netscape/server1 the cache file for that installation is: /usr/netscape/server1/setup/install.inf
To use the cache file for a fast installation of another Messaging Server 4.0, follow these steps:
You can rename the file if you wish.
You will probably want to change some of the parameters and specifications in the cache file. For example, the hostname for this installation may be different than the hostname recorded in the cache file. Remember that the parameters listed in the cache file will be automatically applied to this installation.
The filename is the full path identifying the cache file you wish to use. For example,
Note that when you use a cache file in this way, no new cache file is created from this installation.
If you already have a 3.x or previous 4.0 version of the Messaging Server
installed on your system, you can elect either to perform a totally new
installation, or to upgrade the existing one. These procedures support
upgrading from Messaging Server 3.01 or later, they do not support upgrading
from versions earlier than 3.01.
The choice of whether to upgrade an existing server or perform a new
installation is handled entirely by the installation procedure; you do not
need to run any additional upgrade programs. (Note, however, that during the
installation process you are given the option of immediately migrating
existing mailboxes and message queues to the newly installed server or waiting
until later. If you choose to not migrate immediately, you must later run the
upgrade utility to move mailboxes and messages
to the new server.)
NOTE: This release of the product does not support dynamic upgrades
(upgrading while the Server is running). The Messaging Server cannot be
running during the upgrade procedure. If the Server is running, the
installation program will detect this and terminate the Messaging Server
processes.
When executed, the installation program first detects whether there is an
existing Messaging Server on your system. If it detects an existing server,
you are then presented with the option to upgrade or to perform a completely
new installation. Depending on your selection, you are then presented with
additional options. The possible upgrade/installation paths are as follows:
NOTE: In this case, do not specify the same server-root as the existing
installation as this will cause a conflict with the upgraded installation.
See Replacing an Existing Messaging Server for
additional details.
The following subsections describe the processes involved for the various
upgrade paths.
If you decline the upgrade request, then the standard installation procedure
is executed as described in the earlier sections of this document. Note the
following important points:
If you try to specify the same ports as you did for the existing installation,
the install program detects that these ports are in use. The program then
prompts you to select a different value for each port.
Upgrading an Existing Installation
The installation program will perform a complete re-installation and
replacement of the selected components. Existing configuration data will be
ignored. The mailboxes and message queue/store of the original installation
will not be migrated to the new installation.
Replacing an Existing Messaging Server
Upgrading from a 3.x Server to a 4.0 Server
If you elect to upgrade, and your existing Messaging Server is a 3.x version, the Common Install program detects this. It then gathers the existing configuration parameter settings, and presents these as the default values during the installation process when possible. You can specify non-default values where applicable.
During the installation procedure, the install program will prompt you as to whether you want to migrate the mailboxes and message queue to the upgraded installation. If you decline, then the upgrade process is completed and the upgraded 4.0 Server is started. If you elect to migrate, you should note the following important points:
Once the migration has successfully completed, the Common Install program
completes the upgrade installation and restarts all services.
Upgrading an Older 4.0 Server to a Newer 4.0 Server
Note that mailboxes and message queue do not require migration for a 4.0-to-4.0 system upgrade.
If you elect to upgrade, and your existing Messaging Server is an older 4.0 version, the installation program detects this. It presents existing file, directory, and configuration values as defaults during the installation process and will fill in missing values with standard default suggestions. You are free to specify non-default values where desired.
Migrating Mailboxes and Message Queue with the upgrade Utility
This section describes how to migrate mailboxes and the message queue to a new Messaging Server 4.0 with the upgrade utility.
During the Messaging Server installation process you are given the option of immediately migrating existing mailboxes and the message queue to the newly installed server or waiting until later. If you chose not to migrate at that point, you must now run the upgrade utility to move your user mailboxes and the message queue to the new server. (The upgrade utility performs functions similar to the migrate utility provided with Messaging Server 3.x.)
The number of mailboxes and messages to be migrated determine how long this process takes. The more mailboxes and messages you need to transfer, the longer the process takes. Your machine and network parameters and load are also factors influencing how long a migration will take.
Before running upgrade, note the following points:
See Specifying Non-Default Directories for information on how to use different directories.
To migrate mailboxes and messages to a new 4.0 Messaging Server, follow these steps:
The -m option is a multi-thread process. The default is 5 threads. You can use the -t nn option to specify a different number of threads. For example, to specify 10 threads, you would run:
If you wish, you can also use the -r option to delete messages from the 3.x server after transfer.
Alternatively, instead of using -m, you can use the -u uidlist option to migrate users from one disk partition at a time or only migrate messages for a specific list of user IDs. See Migrating Users in a Multi-Partition Environment and Migrating Specific Users below for details.
Migrating Users in a Multi-Partition Environment
The -m option transfers messages for all 3.x users to the new 4.0 server regardless of the disk partition they are stored in. Instead of using -m, you may be able to improve message transfer efficiency by using the -u uidlist option to transfer all messages from a single disk partition at one time.
When you ran upgrade -s it created a separate users file for each partition. For example, a file named __up.primary.txt that lists the users on the primary partition. If you have a secondary partition, upgrade -s also created a __up.secondary.txt file for the users on that partition. The __up.primary.txt file (or files) are stored in the 3.x default mailbox directory.
To migrate users one partition at a time, use upgrade -u uidlist where uidlist is the name of the partition file created by upgrade -s. For example, to migrate just the users stored in the primary partition, you would enter:
The upgrade -u uidlist command reads the user IDs to be migrated from a text file. As described below, you can create your own text file listing the users whose messages are to be migrated.
You cannot use the -r option on the same command line with the - u option. If you wish messages for the users in the uidlist file to be deleted from the 3.x server after migration, you must first run upgrade -s -r before running upgrade -u. For example, to migrate the users listed in a file named alphalist and then remove from the 3.x server the messages for those users:
The uidlist file can be named whatever you want. The first three lines of the file below are mandatory as follows:
Following these three lines add the list of user IDs to be transferred, one ID per line. For example, a uidlist text file should look like this:
Specifying Non-Default Directories
If you want to use a non-default directory to store messages, you need to run the configutil utility to change the partition name created by upgrade before running upgrade -m (or upgrade -u).
For example, assume you have two 3.x message store directories:
But suppose you want to use the directories /mailstore/sales and /mailstore/research. To set up your mail system with these non- default directories, you must use configutil to change the directory structure before running upgrade -m (or upgrade -u). For example:
Make sure that the /mailstore/sales and /mailstore/research directories have been created with the same permissions as those of server-root/msg-instance/store.
Note that if you later rerun upgrade -s again, the partition information that upgrade relies on will be reset back to the original default. Thus, every time you run upgrade -s you must remember to use configutil to change the partition paths.
Errors that occur during the migration process are recorded in the log. There
are two error recovery procedures depending on whether or not upgrade
completed the process with errors or halted before completion.
If the errors did not cause upgrade to halt abnormally, you can
correct whatever caused the problem and then resume message migration by
performing the following steps :
If upgrade failed without completing the process or was halted
abnormally, follow these steps which will remove all migrated mailbox and
perform the entire upgrade process from scratch:
This cleans up database locking and makes sure that there are no database
problems.
This section describes how to remove Messaging Server instances from a
machine.
In the directory in which you installed the Messaging Server files, you will
find the uninstall program. To run uninstall, do the
following:
You must have superuser privileges (that is, be logged in as root) to
run the uninstall program successfully.
To halt the server instance, run the msg-stop utility. This utility
is stored in the server-root/server-instance directory.
Change to the directory in which you installed the Administration and
Messaging Servers:
Run the uninstall program from the operating system command
line.
The uninstall program then prompts you for the following information:
NOTE: Uninstall might have been unable to remove some of your
installation files. Please check for any remaining files and remove them
manually.
When a machine hosts multiple instances of Messaging Server, perform the
following steps to remove all of the instances:
You must have superuser privileges (that is, be logged in as root) to
run the uninstall program successfully.
To halt a server instance, run the msg-stop utility. This utility is
stored in the server-root/server-instance directory.
This must be done separately for each instance on the machine.
Change to the directory in which you installed the Administration and
Messaging Servers:
This is done with the ldapmodify utility as explained in your
Directory Server documentation.
Copyright 1998 Netscape Communications Corporation. All
rights reserved.
The Software contains encryption software from RSA Data Security, Inc. Copyright © 1994, 1995
RSA Data Security, Inc. All rights reserved. Portions of the Software copyright © 1995 PEER Networks, Inc. All rights
reserved. Portions of the Software copyright 1991-1997 Compuware Corporation. Powered by Java technology from Sun
Microsystems, Inc. Copyright © 1992-1997 Sun Microsystems, Inc. All rights reserved. Java is a trademark or registered
trademark of Sun Microsystems, Inc in the United States and other countries.
Repeating Message Migration
Upgrade Completed the Process With Errors
Upgrade Failed or Was Halted Before Completion
root# /etc/NscpMsg start store
root# /etc/NscpMsg stop store
(This filename begins with two underscore characters.)
Uninstalling Messaging Server Components
Running the Uninstall Utility
The un-installation should now be completed.
root# cd server-root/server-instance
root# ./msg-stop
root# cd server-root
root# ./uninstall
Uninstalling Multiple Instances
root# cd server-root/server-instance
root# ./msg-stop
root# cd server-root
root# rmdir msg-*