| Sun ONE Messaging Server 6.0 Installation Guide for Solaris Operating Systems |
Chapter 2
Installing Messaging ServerThis chapter will describe how to install Sun ONE Messaging Server. It will describe each of the installation screens. Topics covered include:
To upgrade from Sun ONE Messaging Server 5.2 to Sun ONE Messaging Server 6.0, see Chapter 4, "Upgrading to Sun ONE Messaging Server."
Overview of the Installation ProcessThis chapter describes each of the following steps in the installation process.
- Create UNIX System Users and Groups, with appropriate permissions.
The following optional procedures are also described in this chapter:
Note
If you are upgrading from a previous version of Messaging Server 5.x, read Chapter 4, "Upgrading to Sun ONE Messaging Server" prior to performing any upgrades or installations.
Create UNIX System Users and GroupsSystem users run specific server processes. Certain privileges need to be designated for these users to ensure they have appropriate permissions for the processes they are running.
It is recommended that you set up a system user account and group for all Sun ONE servers. You should then set permissions appropriately for the directories and files owned by that user. To do so, follow these steps:
- Log in as superuser.
- Create a group to which your system users will belong. In the following example, the mailsrv group is created:
- Create the system user and associate it with the group you just created. In addition, set the password for that user. In the following example, the user mail is created and associated with the mailsrv group:
For more information on the useradd and usermod commands, refer to your UNIX man pages.
- You might also need to check the /etc/groups file to be sure that the user has been added to the system group that you created.
Note
Should you decide not to set up UNIX system users and groups prior to installing Messaging Server, you will be able to specify them when you the Create the Initial Messaging Server Runtime Configuration.
Run the Java Enterprise System InstallerThe Java Enterprise System installation program installs a series of products, shared components, and libraries that cohabit and interoperate with one another. To successfully install and configure Sun ONE Messaging Server, you need to install the following products through the Java Enterprise System installer:
- Sun ONE Web Server (optional)
You only need to install Web Server if you are enabling Mail Filtering through Messenger Express — See Configuring Messenger Express Mail Filters.
- Sun ONE Identity Server (optional)
You only need to install Identity Server if you are enabling Sun ONE LDAP Schema v.2 ¦— See Messaging Schema Choices.
If you install Identity Server, you do not need to install Directory Server, Administration Server, or Web Server separately. Your Identity Server installation will prompt you to install Directory Server, Administration Server and Web Server.
The Java Enterprise System installation program installs the necessary Solaris packages for these products which you will later configure to suit your needs. In other words, the Java Enterprise System installer simply installs (but does not configure) the component product bits that you specify on your machines.
Sun ONE Web Server
If you want to enable mail filtering through the HTTP Messenger Express client, you need to install and configure Web Server 6.1 through the Java Enterprise System installer. For instructions, see the Sun ONE Web Server 6.1 Installation Guide. For information on Messenger Express mail filtering, see Configuring Messenger Express Mail Filters and the Messenger Express Online Help.
If you are an existing Messaging Server customer and you want to use Delegated Administrator for Messaging, you need to use Sun ONE Web Server 6.0 SP2 (Service Pack 2), which is only available with the Messaging Server 5.2 product. If you enable mail filters through Delegated Administrator, you cannot enable them through the Messaging Server 6.0 Messenger Express client (and vice versa).
Sun ONE Directory Server
Prior to installing Messaging Server, Sun ONE Directory Server should already be installed and configured. For instructions on installing Directory Server, see the Sun ONE Directory Server Installation Guide.
Note
If you are using the Solaris 9 operating system, you can use the directory server that is bundled in operating system.
Sun ONE Messaging Server can be configured with the following versions of Sun ONE Directory Server:
You will be able to install Directory Server 5.2 through the Java Enterprise System installer, however, if Directory Server 5.1 SPx is already installed and configured, you may continue to use it with Messaging Server.
Use Appendix A, "Installation Worksheets" to record your Directory installation and configuration parameters. You will need these parameters when you install the Administration and Messaging servers.
Sun ONE Identity Server
If you are using Sun ONE LDAP Schema, v.2 to provision your users and groups, you need to install Sun ONE Identity Server before installing Messaging Server.
To do so, be sure to install Identity Server 6.1 through the Java Enterprise System installer. Previous versions of Identity Server are incompatible with Messaging Server.
Note that Identity Server will also automatically install the User Management Utility, the command-line interface for provisioning users and groups with Sun ONE LDAP Schema, v.2. For more information on the User Management Utility, read the Sun ONE Communications Server 6.0 Provisioning Tools Configuration and Reference Manual.
If you are an existing customer who wishes to stay with Sun ONE LDAP Schema, v.1 (which is the version of schema included with Messaging Server 5.2), you do not need to install Identity Server.
Additional information on available Messaging Server provisioning tools and schema models is discussed in Understanding Your Messaging Server Provisioning Options in Chapter 1, "Planning Your Installation."
Sun ONE Administration Server
The Administration Server manages operation requests from the Sun ONE Console to all servers installed on a single machine. For example, you can use the Console to start and stop services. The Console sends the request to the appropriate Administration Server. The Administration Server then invokes the programs that actually start or stop Messaging services.
On any machine where you install a Messaging Server, you must also install an Administration Server. There is a single administration server per machine. You use this administration server to manage all the servers installed on that machine.
To install the Administration Server, use the Java Enterprise System installer. Previous versions of Administration Server are incompatible with Messaging Server.
Once the Administration Server is installed, use the Java Enterprise System installer to run the Administration Server initial runtime configuration program. Unlike Messaging Server’s configuration program, the Administration Server runtime configuration is built into the Java Enterprise System installer.
Use Appendix A, "Installation Worksheets" to record your Administration Server configuration parameters. You will need these parameters when you install the Messaging server.
Sun ONE Messaging Server
To install Messaging Server through the Java Enterprise System installer, you should use this guide alongside the Java Enterprise System Installation Guide in order to properly set up, configure, and perform post-installation tasks.
Table 2-1 lists the specific Messaging Server packages that you will install with the Java Enterprise System installer; some of these packages are shared amongst other products:
Uninstalling Messaging Server
To uninstall Messaging Server or to uninstall any other products that were installed through the Java Enterprise System installer, use the Java Enterprise System uninstaller program. For more information, refer to the Java Enterprise System Installation Guide.
Prepare Directory Server for Messaging Server ConfigurationThis section provides instructions on how to run the Directory Server Setup script (comm_dssetup.pl) that configures your LDAP Directory Server to work with your Messaging Server, Calendar Server, or User Management (see Sun ONE Communication Server Command-line Utilities) Utility configurations. The comm_dssetup.pl script prepares the Directory Server by setting up new schema, index, and configuration data in your Directory Server.
When the comm_dssetup.pl script runs, it automatically detects if you have installed and configured Identity Server and consequently, it will set up Sun ONE LDAP Schema, v.1 or v.2 for your system. For more information on supported schema and provisioning tools, review Understanding Your Messaging Server Provisioning Options.
The following topics are explained:
comm_dssetup.pl Requirements
Before you run the comm_dssetup.pl script, be sure to read the following requirements:
- Prior to running the comm_dssetup.pl script, your directory server must be installed and configured.
- Run the comm_dssetup.pl script as superuser.
- Run comm_dssetup.pl prior to running the Messaging Server, Calendar Server, or User Management Utility Initial Runtime Configuration programs.
- The comm_dssetup.pl script must be run on your directory server machine.
- Be sure that your directory server is running prior to running comm_dssetup.pl.
- Whenever you install a new version of Messaging Server, you will need to run the new version of comm_dssetup.pl on your Directory Server machine. New schema and new indexes may be added to each Messaging Server distribution.
- If the configuration data and user and group data are split into separate directory instances, you will need to run the comm_dssetup script on both instances.
- Use the version of Perl that ships with Directory Server to avoid versioning problems: /var/mps/serverroot/bin/slapd/admin/bin/perl.
- If you are running comm_dssetup.pl on a remote directory server:
- Copy the dssetup.zip file from the msg_svr_base/install directory to the remote directory server. You may want to copy it to a directory like /tmp or /var/tmp.
- Unzip the dssetup.zip file (which contains the comm_dssetup.pl and required schema).
- Run the comm_dssetup.pl script on the remote directory server.
- If you are running a replicated directory server, you need to make sure you run the comm_dssetup.pl script against the master and replica directories. For more information on installing Messaging server against a Directory server, see Install Messaging Server against a Directory Server Replica.
Running the comm_dssetup.pl Script
The comm_dssetup.pl script is located in your msg60/.install/Tools/dssetup directory.
You can either run comm_dssetup.pl in:
Use Appendix A, "Installation Worksheets" to record your answers.
Silent Mode
To enable the silent mode, specify all the arguments at one time:
Syntax
Options
The options for this command are:
Option
Description
-i yes|no
Answers the following question: “Do you want to configure new indexes?” Specify yes to configure new indexes. Specify no if you don’t want to configure new indexes.
-c Directory_Server_Root
Directory Server Root path name.For example: /var/mps/serverroot
-d Directory_instance
Directory Server instance subdirectory. For example: slapd-budgie
-r DC_tree
DC tree suffix. For example: o=internet
-u User_Group_suffix
User/Group suffix e.g. o=usergroup
-s yes|no
Answers the following question: “Do you want to update the schema?” Specify yes to update the schema files (Note: you must have configuration directory with schema files). Specify no if you don’t want to update the schema files.
-D DirectoryManagerDN
Directory Manager DN. For example, "cn=Directory Manager"
-w password
Directory Manager password
-b yes|no
Answers the following question: “Will this directory server be used for users and groups?” Specify yes if the directory server will be used for configuration and user/groups. Specify no if this directory will be only used for configuration data.
-t 1|1.5|2
Determines the schema version that you want to use for your Messaging Server:
-m yes|no
Answers the following question: “Do you want to modify the directory server?” Specify yes to modify the directory. Specify no if you don’t want to modify the directory.
-S path-to-schema-files
Specifies the directory path to schema files. For example: ./schema.
Example
# comm_dssetup.pl -i yes -c /var/mps/serverroot -d slapd-budgie
-r o=internet -u o=usergroup -s yes -D "cn=Directory Manager" -w password -b yes -t 1 -m yes
Once you set all the options for the comm_dssetup.pl script, you will see the following summary screen before the script is actually run:
Here is a summary of the settings that you chose:
Server Root : /var/mps/serverroot/
Server Instance : slapd-budgie
Users/Groups Directory : Yes
Update Schema : yes
Schema Type : 1
DC Root : o=internet
User/Group Root : o=usergroup
Add New Indexes : yes
Schema Directory : ./schema
Directory Manager DN : "cn=Directory Manager"
Each option is further described in the Interactive Mode section.
Interactive Mode
The following questions will be asked if you specify comm_dssetup.pl without any arguments:
- Introduction
Press enter to continue. Enter No to exit.
- Installation Root of Directory Server
Indicate the location of the installation root of the Directory Server on the Directory Server machine.
- Directory Server Instance
If multiple instances of Directory Server reside on the machine, choose the one that will be configured with Messaging Server.
- Directory Manager Distinguished Name (DN)
The Directory Manager DN (cn=Directory Manager) is the administrator who is responsible for the user and group data in the Organization Tree. Be sure that the Directory Manager DN you specify in this script is the same DN that you set up in your Directory Server installation as well as your Messaging Server installation.
If you enter Yes, you will answer questions on selecting a DC Tree base suffix and a User and Group base suffix for your Organization Tree.
If you enter No, it is assumed that this directory instance is only used to store configuration data; you will skip to the question about updating schema files. After you finish running this script against the configuration directory instance, you need to run this script against the directory instance that stores user and group data before moving on in the installation process.
The User and Group base suffix is the top entry in the Organization Tree which holds the namespace for user and group entries. Be sure that the User and Group base suffix you select is the same as what you specified during your Directory Server installation and in your Messaging Server installation.
Note
If you installed Identity Server, be sure the suffix specified in Identity Server installation is the same as what you specify for this question. If you do not use the same suffix, Messaging Server will not recognize your Identity Server installation.
For more information on the Organization Tree, see the Sun ONE Messaging Server Provisioning Guide.
- Schema Type
Choose Option 1 if you are planning to use Sun ONE LDAP Schema, v.1.
Choose Option 1.5 if you plan to use Sun ONE LDAP Schema, v.2, Compatibility Mode. For more information, see the Sun ONE Messaging Server 6.0 Provisioning Guide.
Choose Option 2 if you plan to use Sun ONE LDAP Schema, v.2, Native Mode.
If Identity Server is not installed and configured prior to choosing a Sun ONE LDAP Schema, v.2 option, comm_dssetup.pl will terminate. You will be asked to rerun the program once Identity Server is installed.
For more information on your schema options, see Messaging Schema Choices.
- Domain Component (DC) Tree Base Suffix
Note
In Step 7, if you choose Option 1 or 1.5, you will be asked to provide your DC Tree Base Suffix. If you choose Option 2 - Sun ONE LDAP Schema, v.2 - Native Mode, you will not be asked this question.
The DC Tree mirrors the local DNS structure and is used by the system as an index to the Organization Tree that contain the user and group data entries. The DC Tree base suffix is the name of the top entry on the DC tree. You can either choose the default o=internet or another name.
For more information on the DC Tree or the Organization Tree, see the Sun ONE Messaging Server Provisioning Guide.
If you answer Yes, new elements will be added to your schema. It is recommended that you update the Directory with the new schema files each time you install newer versions of Messaging Server.
If you answer Yes to Step 5 (User and Group Directory Server), you will be asked if you want to configure new indexes, which are used to create caches to improve efficiency of directory searches. It is recommended that you answer Yes to this question.
- Summary of Settings
Here is a summary of the settings that you chose:
Server Root : /var/mps/serverroot/
Server Instance : slapd-varrius
Users/Groups Directory : Yes
Update Schema : yes
Schema Type : 1
DC Root : o=internet
User/Group Root : o=usergroup
Add New Indexes : yes
Directory Manager DN : cn=Directory Manager
Now ready to generate a shell script and ldif file to modify the Directory.
No changes to the Directory Server will be made this time.
Do you want to continue [y]:
A summary of your settings will be displayed before your directory configuration is updated.
Note
In Step 7, if you choose Option 2: Sun ONE LDAP Schema, v.2 - Native Mode, the DC Root in the Summary of Settings will be the same value that you entered for the User/Group Root.
If you want to change any of your settings, enter No and re-run the script.
If you enter Yes to continue, the comm_dssetup.pl script will create an LDIF file and a shell script that will be used to update the indexes and schema in your directory server:
/var/tmp/dssetup_YYYYMMDDHHMMSS.sh
/var/tmp/dssetup_YYYYMMDDHHMMSS.ldifwhere YYYYMMDDHHMMSS indicates the time and date stamps when the files were created.
Create the Initial Messaging Server Runtime ConfigurationThe initial runtime configuration program provides a configuration to get your Messaging Server up and running. The program is only meant to be run once. Subsequent running of this program may result in your configuration being overwritten. To modify your initial runtime configuration, use the configuration utilities described in both the Sun ONE Messaging Server 6.0 Administrator’s Guide and the Sun ONE Messaging Server 6.0 Reference Manual.
The following steps walk you through configuring the Messaging Server initial runtime configuration:
Invoke the Messaging Server initial runtime configuration with the following command:
You might use the xhost(1) command if you are configuring Messaging Server on a remote system.
Table 2-2 describes optional flags you can set with the configure program:
Table 2-2 Optional Flags for the Messaging Server configure Program
Flag
Description
-nodisplay
Invokes a command-line configuration program.
-noconsole
Invokes a GUI user interface program.
-state [statefile]
Uses a silent installation file. Must be used with -nodisplay and -noconsole flags. See Perform Silent Installation.
Once you run the configure command, the configuration program will start:
- Welcome
The first panel in the configure program is a copyright page. Select Next to continue or Cancel to exit.
- Software License Agreement
Read the software license agreement.
Select Yes to accept the license. Or, select No to exit the program.
- Select directory to store configuration and data files
Select the directory where you want to store the Messaging Server configuration and data files. For example, /var/opt/SUNWmsgsr. This directory symbolically links with the configuration directories specified in msg_svr_base. For more information on these symbolic links, see Post-Installation File Directory Layout in Chapter 5, "Performing Post-Installation Procedures."
Make sure you have large enough disk space set aside for these files.
- You will see a small window indicating that components are being loaded.
This may take a few minutes.
- Select Components to Configure
Select the Messaging components that you want to configure.
- Message Transfer Agent: Handles routing, delivering user mail, and handling SMTP authentication. The MTA provides support for hosted domains, domain aliases, and server-side filters.
- Message Store: 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). If you are only configuring a Message Store, you must also select the MTA.
- Messenger Express: Handles the HTTP protocol retrieval of messages from the Message Store. If you are only configuring Messenger Express, you must also select the Message Store and the MTA.
- Messaging Multiplexor: Acts as a proxy to multiple messaging server machines within an organization. Users connect to the Multiplexor server, which redirects each connection to the appropriate mail server. This component is not enabled by default. If you do check the MMP as well as the Message Store, they will be enabled on the same system; a warning message will appear for you to change your change port numbers after configuration (For instructions on doing so, see Port Numbers).
To configure the MMP, see the Sun ONE Messaging Server 6.0 Administrator’s Guide and the Sun ONE Messaging Server 6.0 Reference Manual.
Check any components you want to configure, and uncheck those components you do not wish to configure.
- Enter the system user name and the group that will own the installed files.
For information on setting up system users and groups, see Create UNIX System Users and Groups.
- Configuration Directory Server Panel
Enter your Configuration Directory LDAP URL, Administrator and Password.
Gather the Configuration Server LDAP URL from your Directory Server installation. See Directory Server Installation in Appendix A, "Installation Worksheets."
The Directory Manager has overall administrator privileges on the Directory Server and all Sun ONE servers that make use of the Directory Server (for example, the Messaging Server) and has full administration access to all entries in the Directory Server. The default and recommended Distinguished Name (DN) is cn=Directory Manager.
If you are installing against a replicated Directory Server instance, you must you specify the credentials of the replica, not the master directory.
- User/Group Directory Server Panel
Enter your Users and Groups Directory LDAP URL, Administrator and Password.
Gather the User/Group Server LDAP URL information from the host and post number information from your Directory Server installation. See Directory Server Installation in Appendix A, "Installation Worksheets."
The Directory Manager has overall administrator privileges on the Directory Server and all Sun ONE servers that make use of the Directory Server (for example, the Messaging Server) and has full administration access to all entries in the Directory Server. The default and recommended Distinguished Name (DN) is cn=Directory Manager.
If you are installing against a replicated Directory Server instance, you must specify the credentials of the replica, not the master directory.
- Postmaster Email Address
Enter a Postmaster Email Address.
Select an address that your Administrator will actively monitor. For example, pma@siroe.com for a postmaster on the siroe domain. Note that this address cannot begin with “Postmaster.”
Note that the user of the email address is not automatically created. Therefore, you will need create it by using a provisioning tool.
- Password for administrator accounts
Enter a universal password that will be used for service administrator, server, user/group administrator, end user administrator privileges as well as PAB administrator and SSL passwords.
After the initial runtime configuration, you might change this password for individual administrator accounts. For more information, see Modifying Your Configuration in Chapter 5, "Performing Post-Installation Procedures."
- Default Email Domain
Enter a Default Email Domain.
This email domain is the default that is used if no other domain is specified. For example, if siroe.com is the default email domain, then messages that are generated by an internal user will be attempted to be sent to the designated recipient in the siroe.com domain if no other domain is specified.
If you are using the User Management Utility, the command-line interface for provisioning users and groups with Sun ONE LDAP Schema, v.2, you will want to specify the same default domain during its configuration. For more information, see the Sun ONE Communications Server 6.0 Provisioning Tools Configuration and Reference Manual.
- Organization DN
Enter an Organization DN.
In the organization tree, you need an organization DN under which your organization will reside.
For example, if your organization DN is o=Engineering, all the users in that organization will be placed under the LDAP DN o=Engineering, o=usergroup (where o=usergroup is your user/group Directory suffix which was specified in Prepare Directory Server for Messaging Server Configuration).
If you choose the same your user/group Directory suffix as your Organization DN, you may have migration problems if you decide to create a hosted domain. If you want to set up a hosted domain during initial runtime configuration, then specify a DN one level below the User/Group suffix.
- Ready to Configure
The configuration program will check for enough disk space on your machine and then outline the components it is ready to configure.
To configure the Messaging components, select Configure Now. To change any of your configuration variables, select Back. Or to exit from the configuration program, select Cancel.
- Starting Task Sequence, Sequence Completed, and Installation Summary Panels
You can read the installation status by selecting Details on the final Installation Summary page. To exit the program, select Close.
A log file is created in /msg_svr_base/install/configure_YYYYMMDDHHMMSS.log, where YYYYMMDDHHMMSS identifies the 4-digit year, month, date, hour, minute, and second of the configuration.
An initial runtime configuration is now set up for your Messaging Server. To change any configuration parameter, refer to both Modifying Your Configuration in Chapter 5, "Performing Post-Installation Procedures" and the Sun ONE Messaging Server Administrator’s Guide for instructions on doing so.
To start Messaging Server, use the following command:
Perform Silent InstallationThe Messaging Server initial runtime configuration program automatically creates a silent installation state file (called saveState) that can be used to quickly configure additional Messaging Server instances in your deployment where the Messaging Server Solaris packages have been installed. All of your responses to the configuration prompts are recorded in that file.
By running the silent installation, you instruct the configure program to read the silent installation state file. The configure program uses the responses in this file rather than ask the same installation questions again for subsequent initial runtime configurations of Messaging Server. When you use the state file in a new installation, you are not asked any questions. Instead, all of the state file responses are automatically applied as the new installation parameters.
The silent installation saveState state file is stored in the /msg_svr_base/install/configure_YYYYMMDDHHMMSS directory, where YYYYMMDDHHMMSS identifies the 4-digit year, month, date, hour, minute, and second of the saveState file.
To use the silent installation state file to configure another Messaging Server instance on another machine in the deployment, follow these steps:
- Copy the silent installation state file to the installation directory on the machine where you are performing the new installation.
- Review and edit the silent installation state file as necessary.
You will probably want to change some of the parameters and specifications in the state file. For example, the default email domain for the new installation may be different than the default email domain recorded in the state file. Remember that the parameters listed in the state file will be automatically applied to this installation.
- Run the following command to configure other machines with the silent installation file:
msg_svr_base/sbin/configure -nodisplay -noconsole -state \
fullpath/saveStatewhere fullpath is the full directory path of where the saveState file is located. (See Step 1 of this section).
Install Messaging Server against a Directory Server ReplicaThere might be limitations that prevent you from installing Messaging Server against a Directory Server replica:
To install Messaging Server against a Directory Server replica, follow these steps:
- Run the comm_dssetup.pl program against all Directory Servers including the the Directory Server replicas as noted in comm_dssetup.pl Requirements.
- Run the Messaging configure program (located in msg_svr_base/sbin/configure) using the replicated Directory Server credentials as described in Step 7 and Step 8 in Create the Initial Messaging Server Runtime Configuration.
Because of invalid privileges, the configure program will fail in trying to configure the Directory Server Administrators. It will, however, produce the *.ldif files that are needed to allow proper privileges to the Directory Server replicas.
- Move the *.ldif files to the Directory Server master.
- Run the ldapmodify command on the *.ldif files.
See the Sun ONE Directory Server documentation for more information on ldapmodify or in the /msg_svr_base/install/configure_YYYYMMDDHHMMSS.log.
- Re-run the configure program.
Your Directory Server replica (and master) are now configured to work with your Messaging Server.
