Previous     Contents     Index     DocHome     Next     
iPlanet Messaging Server 5.1 Installation Guide for Windows NT



Chapter 2   Installation Instructions


This chapter describes how to run the setup program, directory setup program, and silent installation. In addition, common installation scenarios and post-installation configuration steps are outlined. It is assumed that you have reviewed the previous sections in Chapter 1, "Preparing for Installation."



Installation Readiness

At this point, you are almost ready to run the setup program and begin Messaging Server installation. You should be able to answer "yes" to the following questions before you continue:

  1. Have you reviewed the System Requirements and verified that they have been met?

  2. Have you reviewed the Product Hierarchy and Interaction to determine which components you will be installing and where you will be installing them?

  3. Have you determined the Types of Installations you would like to perform, and have you gathered all of the necessary information?

  4. Have you decided if you will use an existing Directory Server or install the one that comes with the Messaging Server? You should review Configuring an Existing Directory Server for more information on using an existing Directory Server.

  5. Are you ready to your record installation and configuration values in the installation checklist in Table 1-2?



Transferring Messaging Server Installation Files

To transfer and extract the product archive files, use the following steps.


From the Web

To transfer and extract the compressed installation program files from the iPlanet Web site, locate the Messaging Server archive file. Download and unzip the zipped archive of Messaging Server from:

http://www.iplanet.com/downloads.

  1. Unzip the m51DIU.zip archive.

  2. Create a directory (such as c:\tmp\msg51) on the machine that will host Messaging Server and copy the archive files to that directory.


From the CD

  1. Locate the Messaging Server archive:

    From the product CD:

    Insert the CD into the CD-ROM drive on your installation machine and locate the archive \ntx86. Next, locate the appropriate subdirectory you want to install:

    • ES - iPlanet Web Server

    • iDA - iPlanet Delegated Administrator for Messaging

    • iMS - iPlanet Messaging Server
      Note If you do not have an existing Directory Server installation, skip the next step. It is recommended that you install a new configuration directory server with the Windows NT version of Messaging Server if you are migrating your users and groups from Netscape Messaging System. Refer to the iPlanet Messaging Server 5.0 Migration Guide for more information.


  2. Locate the ims_dssetup archive (on CD: \ntx86\iMS\msg) and copy it to the archive where you installed your existing Directory Server. In addition, you should copy the supporting config (located in dssetup.zip) directory to your existing Directory Server machine.
    Note If you have two existing directory servers (one for users and groups and one for configuration data), you will need to run the ims_dssetup.pl on both directory servers.




Running the ims_dssetup Script

This section provides instructions on how to run the ims_dssetup.pl script to configure an existing Directory Server for Messaging Server installation. If you do not have an existing Directory Server, you do not need to read this section. The ims_dssetup.pl script is located in the msg directory where you downloaded the archive file from the Web; on the CD-ROM, it is also located in the msg directory:

  1. Execute the ims_dssetup script with the following command:

    perl5 ims_dssetup.pl
    Note The ims_dssetup.pl utility is a Perl script; Messaging Server provides a Perl (version 5.005) executable program in the c:\server-root\install directory of the existing Directory Server installation. It is recommended that you use this version of Perl script.


  2. Enter y to continue,

    Welcome to the iMS Directory Server preparation tool.

    This tool will help you setup a Netscape Directory Server and make it ready to use for installing iPlanet Messaging Server.

    Do you want to continue [y]:

  3. Specify the Directory Server root where the existing directory server resides.

    Please enter the full path to the directory where Netscape Directory Server was installed.

    Directory server root [c:\iplanet\server5] :

  4. Select a Directory Server instance that you plan to use with the Messaging Server installation.

    Please select a directory server instance from the following list:

    [1] slapd-budgie

    Which instance do you want [1]:

  5. Specify the base suffix for the DC tree or press Return to accept the default value. In the DC Tree, the convention is to set the root to o=internet.

    Please enter the base suffix for DC Tree [o=internet]:

  6. Specify the base suffix under which the Users and Groups data should be set up. Press Return to accept the default value.

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

  7. Answer yes or press Return to update the schema files.

    Do you want to update the schema files [yes]:

  8. Answer yes or press Return to configure the new indexes.

    Do you want to configure new indexes [yes]:

  9. Specify the schema directory; this is the config subdirectory of the directory where the ims_dssetup.pl script is located:

    Please enter the schema directory [c:\iplanet\server5\msg\config]:

At this point, you will see a summary of your options. It will look similar to the following:

Here is a summary of the settings that you chose:

Server Root            : c:\iplanet\server5
Server Instance            : slapd-budgie
Update Schema             : yes
DC Root             : o=internet
User/Group Root             : o=siroe.com
Add New Indexes             : yes
Schema Directory             : c:\iplanet\server5\msg\config

Answer yes or press Return to continue, or answer no to start over. Do you want to continue [y]: At this point, the configuration of the specified Directory Server begins.



Running the setup Program


The installation directory where the iPlanet Messaging Server files (such as c:\temp\msg5install) reside, contains the setup.exe program.

You can run the setup command as follows:

setup [options]

The optional parameters for the setup command are listed in Table 2-1:

Table 2-1    Optional parameters for the setup command

Parameter

Description

-s  

Silent installation mode. This parameter must be used in conjunction with the -f file parameter.  

-f file  

Specify file as the silent installation script. This parameter must be used in conjunction with -s parameter.  

-k  

Keep the installation cache.  

To run setup, follow these steps:

  1. Login as Administrator.

    You must have superuser privileges (logged in as Administrator) to run the installation program.

  2. Run the setup command from the binary directories, using optional parameters (listed above) if necessary.



Silent Installation

The installation program allows you to create a silent installation cache file that can be used to quickly install additional Messaging Server instances in your enterprise. When you use the -k option during your first installation, you create the silent installation cache file. All of your responses to the installation prompts are recorded in that file.

By running the silent installation, you instruct the setup program to read the silent installation cache file. The setup program uses the responses in this file rather than ask the same installation questions again for subsequent Messaging Server installations. When you use the cache file in a new installation, you are not asked any questions. Instead, all of the cache file responses are automatically applied as the new installation parameters.

The silent installation cache file is saved in the c:\server-root\setup directory. For example, if you installed the server into c:\iplanet\server5, the cache file for that installation is:

c:\iplanet\server5\setup\install.inf

To use the cache file for a fast installation of another Messaging Server instance, follow these steps:

  1. Copy the silent installation cache file to the installation directory that you are using for the new installation.

  2. Review and edit the silent installation cache file as necessary.

    You will probably want to change some of the parameters and specifications in the cache file. For example, the host name for this installation may be different than the host name recorded in the cache file. Remember that the parameters listed in the cache file will be automatically applied to this installation.

  3. Run setup with the -s -f filename options where filename represents the full path and name of the silent installation cache file (Additional setup options are listed in Running the setup Program.). For example:

    setup -s -f c:\home\foo\install.inf
    Note When you use a cache file, no new cache file is created from a silent installation.

    If you have many similar server configurations to set up, you can place the configuration file and the server installation package on each machine. You execute the setup program on each machine; it then extracts all information it needs from the configuration file as it performs the installation.




Installation Scenarios

This section describes three common installation scenarios:
Note The instructions in these scenarios are geared for a Custom Installation. If you are performing an Express or Typical Installation, you will not see all of the questions listed here.


For some questions, you are instructed to provide a specific answer; for the others, you will need to provide your own answer. Detailed information about each question can be found in Chapter 3 "Installation Questions."
Tip It is important that you record your answer for each question in the Table 1-2; you may need them for another product installation (for example, iPlanet Delegated Administrator for Messaging requires answers to several of the questions specified during the Messaging Server installation. See "Required Information for the iPlanet Delegated Administrator for Messaging Installation" for more information.



Scenario One: Install Messaging and Directory Servers on the Same Machine

Follow the installation instruction provided below if you are installing Messaging and Directory Servers on the same machine:

  1. Go to the directory where you downloaded the installation files and click on the setup.exe program.

  2. Run the setup program to begin installation. See Running the setup Program for more information.

  3. Provide answers for the following questions as described in Chapter 3, "Installation Questions."


Scenario Two: Install Messaging Server with Existing Configuration and Users and Groups Directory Servers

Follow the installation instructions provided below if you are installing Messaging Server with an existing Configuration and Users and Groups Directory Servers.

  1. Go to the directory where you downloaded the installation files and click on the setup.exe program.

  2. Run the setup program to begin the installation. See Running the setup Program for more information.

  3. Provide answers for the following questions as described in Chapter 3, "Installation Questions."


Scenario Three: Install Messaging Server with Existing Users and Groups Directory Server and New Configuration Directory Server

Follow the installation instructions provided below if you are installing the Messaging Server with an existing Users and Groups Directory Server only:

  1. Go to the directory where you downloaded the installation files and click on the setup.exe program.

  2. Run the setup program to begin the installation. See Running the setup Program for more information.

  3. Provide answers for the following questions as described in Chapter 3, "Installation Questions."



Post-Installation Configuration

At this point, you will have finished installing Messaging Server onto your system. You may need to perform additional post-installation configuration, particularly if you install multiple instances of Messaging Server.


Messaging Servers Sharing Common User and Group Directory

If you install multiple instances of the messaging server that use a common Users and Groups Directory Server, Installer fails to add the msg-admin-xxx account to Messaging End User Administrator group.

All instances of Messaging Server create an LDAP account in the User and Group directory. These instances use the account credentials to access User and Group data from the LDAP directory.

This account, created during installation, is permitted read access to necessary directory data, that is granted via access control items (ACI) in the directory. The ACI grants access to members of the Messaging End User Administrator group. This group is located in the 'ou=Groups' branch of the default domain's organization subtree. The DN of the Messaging End User Administrator Group is 'cn=Messaging End User Administrators Group, ou=Groups, o=siroe.com, o=ISP', where:

  • The default domain is siroe.com

  • The base suffix of the user and group LDAP directory is 'o=ISP'

  • The default organization's subtree (one that 'dc=siroe, dc=com, o=internet' has a DN reference to) is 'o=siroe.com, o=ISP'

ACIs in the directory permit access to the directory data to members of the group referenced above, but only the first Messaging Server servers account is added as a member of this group. Installer creates the account for other servers and stores their credentials in the following pair of attributes: local.ugldapbasedn and local.ugldabindcred. However, Installer fails to add this account as a member of the Messaging End User Administrator Group thereby preventing Messaging Server from accessing the necessary data from the users and groups directory server.

To properly configure the LDAP directory, you must add the DN of the Messaging Server account as a member of the Messaging End User Administrator Group by following these steps:

  1. Determine the DN of the Messaging End User Administrator Group (For example: 'dn: cn=Messaging End User Administrators Group, o=siroe.com, o=ISP').

  2. Determine the DN of the Messaging Server account. This is stored in the attribute local.ugldapbinddn of the Messaging Server configuration. Use the command '$INSTANCEROOT/getconf local.ugldapbinddn' to retrieve the DN (For example: uid=msg-admin-2, ou=People, o=siroe.com, o=ISP).

  3. Add the DN as a value of the 'uniquemember' attribute of the Messaging End User Administrator Group. The LDIF example shown below will add the account DN to the group used in this example:

    dn: cn=Messaging End User Administrators Group, ou=Groups,    o=siroe.com,o=ISP
    changetype: modify
    add: uniquemember
    uniquemember: uid=msg-admin-2, ou=People, o=siroe.com, o=ISP

  4. Use the LDIF file as an argument to ldapmodify the Messaging End User Administrator Group to grant the required access privileges to the Messaging Server.


Adding Service Administrators Group to Second Messaging Server

If a Service Administrators group already exists, adding a second Messaging Server fails to add its own service administrator into the group. As a workaround, manually add the second service administrator user to the service administrator group.


Previous     Contents     Index     DocHome     Next     
Copyright © 2001 Sun Microsystems, Inc. Some preexisting portions Copyright © 2001 Netscape Communications Corp. All rights reserved.

Last Updated May 06, 2001