| Sun ONE Messaging Server 6.0 Installation Guide for Solaris Operating Systems |
Chapter 1
Planning Your InstallationThis chapter presents an overview for planning your Sun ONE Messaging Server 6.0 installation and configuration. The following topics are covered:
Installation OverviewTo install Sun™ ONE Messaging Server 6.0, you will use the Sun Java™ Enterprise System installer. The installer provides a consistent installation interface, common components, and common procedures across the entire Java Enterprise System product set. In addition to Messaging Server, you can also install Sun™ ONE Web Server, Sun™ ONE Directory Server, Sun™ ONE Portal Server, Sun™ ONE Calendar Server, and so on. For more information on the Java Enterprise System installer, review the Java Enterprise System Installation Guide.
In addition to the Java Enterprise System installer, the Messaging Server product and documentation provides procedures and tools for completing and upgrading your installation, for configuring your servers, and so on. For more information on these additional installation and configuration steps, read this guide prior to using the Java Enterprise System installer.
Before you install Messaging Server through the Java Enterprise System installer, you should verify that the systems on which you plan to install the software meet the minimum product requirements. In addition, you should have a general understanding of Messaging Server components and the directory schema used by them. It is also a good idea to plan how you want to configure the software components before you begin the installation process.
System RequirementsThis section describes the following system requirements and recommendations for Messaging Server:
Hardware
The minimum hardware requirements for Messaging Server are:
- Approximately 500 MB of disk space for a standard installation. For production systems, you should plan at least 1 GB to support the product binaries, data, and configuration files.
- 128 MB of RAM. For production systems, you should have a minimum of 256 MB of RAM; be sure to allocate this accordingly, depending on the size of your site and number of users.
- Adequate space for your user mailboxes (message store), database, configuration directory, log files. and message queue directory. These can grow in size dramatically depending on the size of your site, so be sure to allocate space accordingly.
Software
Messaging Server is supported on Sparc and x86 for Solaris 8, and Solaris 9 operating systems.
Read the Sun ONE Messaging Server 6.0 Release Notes for required Solaris operating system patches.
A high quality caching DNS server on the local network is a requirement for a production deployment of Messaging Server.
Additionally, ensure in your Solaris setup that DNS is properly configured and that it is clearly specified how to route to hosts that are not on the local subnet:
- The /etc/defaultrouter should contain the IP address of the gateway system. This address must be on a local subnet.
- The /etc/resolv.conf exists and contains the proper entries for reachable DNS servers and domain suffixes.
- In /etc/nsswitch.conf, the hosts: line has the files, dns and nis keywords added. The keyword files must precede dns and nis.
- Make sure that the FQDN is the first host name in the /etc/hosts file.
For Messenger Express access, a JavaScript-enabled browser is required. For optimal performance, Sun ONE recommends using the following browser and platform combinations listed in Table 1-1:
File System
Messaging Server supports the following file systems:
- NFS (Network File System). Though NFS is not supported on machines with message stores, you can use this file system on MTA relay machines, particularly if LMTP is enabled, or for autoreply histories and message defragmentation. (See the Sun ONE Messaging Server Administrator’s Guide for more information on autoreply). In addition, NFS can be supported on BSD-style mailboxes (/var/mail/).
- LUFS (Logging UFS).
- VxFS (Veritas File System). Veritas File System provides good system performance if configured properly. If you use VxVM, the Veritas Volume Manager, you need to carefully watch that the volumes and the log file for the volumes are set to be regularly striped.
- Sun Cluster Global File System.
Physical Memory
Make sure you have an adequate amount of physical memory on each machine in your deployment. Additional physical memory improves performance and enables the server to operate at peak volume. With sufficient memory, Messaging Server can operate efficiently without excessive swapping.
At minimum, be sure to have 1G of memory per CPU.
Disk Capacity
When planning server system disk space, you need to be sure to include space for operating environment software, Messaging Server software, and databases. Be sure to use a robust external disk array, since Messaging Server is typically disk bound.
In addition, user disk space needs to be allocated. This space is usually determined by your site’s policy.
CPU Resources
Enable enough CPU for your Message Stores, MTAs, and on systems that are just running multiplexing services (MMP and Messenger Express Multiplexor). In addition, enable enough CPU for any RAID systems that you plan to use.
Understanding Your Messaging Server Provisioning OptionsThis section outlines your provisioning options with Messaging Server 6.0. Because of the complexity in provisioning Messaging Server 6.0, spend time understanding your options before installing the product.
The following topics are described:
Messaging Schema Choices
This section describes two schema options that are available and supported with Messaging Server 6.0. This section outlines the following topics:
- Sun ONE LDAP Schema, v.2 (Native Mode)
Deciding Which Schema to Use
Choosing the schema that’s right for your installation depends on your provisioning needs:
If you need to use a graphical user interface or if you need your end users to be able to make modifications to their profiles through a graphical user interface, you should use Sun ONE LDAP Schema, v.1. Note that this option is not available for new installations of Messaging Server. It is only available for existing Messaging Server 5.x installations where Messaging Server 6.0 is now being installed.
If you are planning on using a command-line interface, you can use Sun ONE LDAP Schema, v.1 (for existing Messaging Server installations) or Sun ONE LDAP Schema, v.2 (for new or for existing Messaging Server installations).
You can also use your own graphical or command-line interfaces with either schema should you decide not to use the provisioning interfaces that accompany Messaging Server.
Sun ONE LDAP Schema, v.1
Sun ONE LDAP Schema, v.1 is a provisioning schema that consists of both an Organization Tree and a DC Tree. This set of schema was supported in previous Messaging Server 5.x versions (which at the time was simply called “schema”).
When Messaging Server searches for user or group entries, it looks at the user ‘s or group’s domain node in the DC Tree and extracts the value of the inetDomainBaseDN attribute. This attribute holds a DN reference to the organization subtree containing the actual user or group entry.
Only users who have installed previous versions of Messaging Server should use Sun ONE LDAP Schema, v.1.
Note that migrating to Sun ONE LDAP Schema, v.2 will be imperative if you plan to install Messaging Server with other Sun ONE products in future releases.
Supported Provisioning Tools: Sun ONE Delegated Administrator for Messaging Graphical User and Command-line Interfaces and LDAP Provisioning Tools for Sun ONE LDAP, Schema v.1. For more information, see Messaging Server Provisioning Tools.
Sun ONE LDAP Schema, v.2 (Native Mode)
Sun ONE LDAP Schema, v.2 is a newly defined set of provisioning definitions that describe the types of information that can be stored as entries using the Directory LDAP.
The native mode uses search templates to search the LDAP directory server; once the domain is found by using the domain search template, the user or group search templates are used to find a specific user or group.
You should use this mode if you are installing Messaging Server for the first time and you don’t have other applications on your machine that are dependent on a two tree provisioning model. You should also use this mode if you want to install other products in the Java Enterprise System product suite.
Note that Sun ONE LDAP Schema, v.2 Native Mode is the recommended provisioning model for all Sun ONE products in the Java Enterprise System product suite.
Supported Provisioning Tools: Sun ONE Communication Server Command-line Interface and LDAP Provisioning Tools for Sun ONE LDAP Schema, v.2. For more information, see Messaging Server Provisioning Tools.
Messaging Server Provisioning Tools
Through supported Messaging Server provisioning tools, administrators can query, modify, add, or delete user, group, and domain entry information in their LDAP directory. This section examines these Messaging Server provisioning tools.
In addition to the questions asked in Deciding Which Schema to Use, you should use Table 1-2 to evaluate your schema and provisioning tool options.
Note
Prior to installing and configuring Messaging Server, you will need to decide upon a schema model and tool or tools for provisioning your Messaging Server entries.
The following sections provide high-level information about the supported provisioning tools:
Sun ONE Delegated Administrator for Messaging
Sun ONE Delegated Administrator for Messaging provides both a command-line and a graphical user interface to provision users and groups. Delegated Administrator uses Sun ONE LDAP Schema, v.1, which is the Messaging Server 5.x version of provisioning definitions, that describe the types of information that can be stored as entries in the LDAP Directory Server.
To install Delegated Administrator, you need to download it from the Sun Software page. Contact your Sun ONE representative for information on the download location information.
Note
Delegated Administrator can only be installed after Messaging Server and Web Server are installed and configured. For more information on installing Delegated Administrator, see the Sun ONE Delegated Administrator documentation.
Delegated Administrator is only available for those customers with existing Messaging Server 5.x installations and who are currently installing Messaging Server 6.0. It is not available to those customers new to the Messaging Server product.
Delegated Administrator must be used with Sun ONE Web Server 6.0 (which is only bundled with the previous Messaging Server 5.2 product). You cannot use Web Server 6.1 (bundled with the Java Enterprise System installer) with Delegated Administrator.
Be sure to read the product limitations in Table 1-2 as well as in the Sun ONE Messaging Server 6.0 Release Notes.
Summary of Installation Steps: To install and configure Sun ONE Delegated Administrator for Messaging with Messaging Server 6.0:
- Be sure that either Sun ONE Directory Server 5.1 or 5.2 is installed and configured.
For more information, read the Sun ONE Directory Server Installation Guide.
- Install and configure Messaging Server 6.0 with help from this guide.
Messaging Server will detect that you are using Sun ONE LDAP Schema, v.1 since Sun ONE Identity Server will not be installed.
- Install Sun ONE Web Server 6.0 from your previous Messaging Server 5.2 bundle.
Review the Sun ONE Web Server documentation and the Sun ONE Delegated Administrator documentation.
- Install Sun ONE Delegated Administrator for Messaging 1.2 Patch 2. Contact your Sun support representative to obtain the latest version.
Refer to the Sun ONE Delegated Administrator documentation.
LDAP Provisioning Tools
You can also provision users and groups through the Directory LDAP. Unlike Sun ONE provisioning graphical and command-line interfaces, you can directly provision users and groups by adding, removing, and modifying the LDIF records through the LDAP without having to use a user interface.
Summary of Installation Steps:
- If you plan to use Sun ONE LDAP Schema, v.2, install and configure Identity Server. If you plan to use Sun ONE LDAP Schema, v.1, you can skip to Step 2.
If you install Identity Server, Messaging Server will identify Sun ONE LDAP Schema, v.2 as your schema model. Even though you cannot use the Identity Server GUI to provision your Messaging Server user, group, and domain entries, you need to install Identity Server in order to add the new ACIs and search templates to your organization tree. For more information on installing Identity Server, refer to the Sun ONE Identity Server 6.1 Installation Guide and the Sun ONE Messaging Server 6.0 Provisioning Guide.
If you don’t install Identity Server, Messaging Server will assume you are using Sun ONE LDAP Schema, v.1.
- If Directory Server is not already installed, be sure to install and configure it.
For more information, refer to the Sun ONE Directory Server Installation Guide.
- Configure Identity Server to recognize data in your Directory Server.
Before Identity Server can recognize the data in your LDAP directory, you must add special object classes to entries for all organizations, groups and users that will be managed by Identity Server. If you have not done this already, do it before you start provisioning new accounts. Sample scripts are bundled in the Identity Server product to help you automatically add these object classes to your directory. For more information on these post-installation steps, see the Sun ONE Identity Server 6.1 Installation and Migration Guide.
- Install and configure Messaging Server 6.0 with help from this guide.
Messaging Server will detect which Sun ONE LDAP Schema you are using, depending on whether or not Identity Server is installed.
- Install and configure Sun ONE Web Server 6.1 to enable mail filtering in Messenger Express. For more information on enabling mail filtering, see Configuring Messenger Express Mail Filters. To install Web Server, refer to the Sun ONE Web Server 6.1 Installation Guide.
Though mail filtering is not a provisioning tool, its functionality existed in the previous GUI version of Delegated Administrator for Messaging.
- Refer to the Sun ONE Messaging Server documentation to perform LDAP provisioning.
For Sun ONE LDAP Schema, v.2 LDAP provisioning, use the Sun ONE Messaging Server 6.0 Provisioning Guide with the Sun ONE Messaging Server 6.0 Schema Reference Manual.
For Sun ONE LDAP Schema, v.1 LDAP provisioning, use the Messaging Server 5.2 Provisioning Guide and Sun ONE Messaging Server 6.0 Schema Reference Manual (The 6.0 Schema Reference manual contains object classes and attributes for both Sun ONE LDAP Schema, v.1 and v.2).
Sun ONE Communication Server Command-line Utilities
The Sun ONE Identity Server uses Sun ONE LDAP Schema, v.2, the newly defined set of provisioning definitions that describe the types of information that can be stored as entries using the Directory LDAP.
Since the Sun ONE server products in the Java Enterprise System product suite use Sun ONE LDAP Schema, v.2, it is recommended that you use the Sun ONE Communication Server command-line utilities, particularly if you are using more than one Java Enterprise System product or if you are performing a brand new installation of Messaging Server.
Summary of Installation Steps:
- Install and configure Identity Server.
Even though you cannot use the Identity Server GUI to provision your Messaging Server user, group, and domain entries, you need to install Identity Server in order to add the new ACIs and search templates to your organization tree. For more information, refer to the Sun ONE Identity Server Installation Guide and the Sun ONE Messaging Server 6.0 Provisioning Guide.
- If Directory Server is not already installed, be sure to install and configure it.
For more information, refer to the Sun ONE Directory Server Installation Guide.
- Configure Identity Server to recognize data in your Directory Server.
Before Identity Server can recognize the data in your LDAP directory, you must add special object classes to entries for all organizations, groups and users that will be managed by Identity Server. If you have not done this already, do it before you start provisioning new accounts. Sample scripts are bundled in the Identity Server product to help you automatically add these object classes to your directory. For more information on these post-installation steps, see the Sun ONE Identity Server 6.1 Installation and Migration Guide.
- Install and configure Messaging Server 6.0 with help from this guide.
Messaging Server will detect that you are using Sun ONE LDAP Schema, v.2 because Sun ONE Identity Server is installed.
- Install and configure Sun ONE Web Server 6.1 to enable mail filtering in Messenger Express. For more information on enabling mail filtering, see Configuring Messenger Express Mail Filters. To install Web Server, refer to the Sun ONE Web Server 6.1 Installation Guide.
Though mail filtering is not a provisioning tool, it is functionality that existed in the previous GUI version of Delegated Administrator for Messaging.
- Install and configure the User Management Utility for Sun ONE Messaging and Calendar Servers.
Read the Sun ONE User Management Utility for Sun ONE Messaging and Calendar Servers Configuration and Reference Manual.
Comparing Your Provisioning Tool Options
Table 1-2 shows the various supported schema, provisioning tools, provisioning limitations, and recommended documentation for additional information.
Pre-Installation ProceduresThis section describes recommended procedures you should do prior to installing Messaging Server:
Disabling the sendmail daemon
Prior to installing Messaging Server, you should disable the sendmail daemon if it is running. To disable, follow these steps:
Installation Considerations
This section describes installation considerations to help you prepare for Messaging Server installation.
- Resource Contention. To avoid resource contention between the servers, it is recommended that you install the Directory Server on a different machine than where you install Messaging Server.
- Installation Privileges. You must install Messaging Server logged in as superuser.
- Messaging Server Base Directory. The Messaging Server is installed into a directory referred to as msg_svr_base (for example, /opt/SUNWmsgsr). This directory provides a known file location structure (file directory path).
Installation Worksheets
While installing Messaging Server, use the installation worksheets in Appendix A, "Installation Worksheets" to record and assist you with the installation process. Note that you can reuse these installation worksheets for multiple installations of Messaging Server, uninstallation, or for Messaging Server upgrades.
Tip
It is recommended that you record all of the port numbers you specify during the installation, along with the specific component using that port number.
