Chapter 11 Pre-Installation Considerations and Procedures

This chapter describes considerations you need to think about, and procedures you need to perform, before installing Messaging Server. See the Sun Java Enterprise System 2004Q2 Installation Guide for instructions on running the Java Enterprise System installer.

Installation Considerations

This section describes installation considerations that help you prepare to install Messaging Server.

Resource Contention. To avoid resource contention between the servers, considering installing Directory Server on a different host 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).

Upgrading Servers. If you do not install other component products (Web Server, Directory Server, Identity Server, and Administration Server) on the Messaging Server host, you do not have to upgrade those components and Messaging Server should continue to operate without problem. If other component products are installed on the same machine, then they must be upgraded along with Messaging Server.

Port Number Conflicts. If certain products are installed on the same machine, you will encounter port number conflicts. The following table shows potential port number conflicts.

Table 11-1 Potential Port Number Conflicts
Conflicting Port Number	Component	Component
143	IMAP Server	MMP IMAP Proxy
110	POP3 Server	MMP POP3 Proxy
993	IMAP over SSL	MMP IMAP Proxy with SSL
80	Identity Server (Web Server port)	Messenger Express

If possible, install products with conflicting port numbers on separate hosts. If you are unable to do so, then you will need to change the port number of one of the conflicting products. To change port numbers, use the configutil utility (see the Sun Java System Messaging Server Administration Reference for instructions).

The following example uses the service.http.port configutil parameter to change the Messenger Express HTTP port number to 8080.

configutil -o service.http.port -v 8080

Installation Worksheets

When installing Messaging Server, use the following installation worksheets to record and assist you with the installation process. You can reuse these installation worksheets for multiple installations of Messaging Server, uninstallation, or for Messaging Server upgrades.

Directory Server Installation Worksheet


Tip	Record all the port numbers you specify during the installation, along with the specific component using that port number.

You either installed Directory Server through the Java Enterprise System installer, or have a previous Directory Server installation. Record your Directory Server installation and configuration parameters in the following table. You will need these parameters when you install and configure Administration Server and Messaging Server, as well as your initial Messaging Server runtime configuration. For additional help, see the Sun Java System Messaging Server Administration Guide.

Table 11-2 Directory Server Installation Parameters
Parameter	Description	Example	Used in
Directory Installation Root	A directory on the Directory Server host dedicated to holding the server program, configuration, maintenance, and information files.	/var/opt/mps/serverroot	comm_dssetup.pl Perl script
Host	The fully qualified domain name. The fully qualified domain name consists of two parts: the host name and the domain name.	svr1.west.sesta.com	Administration Server Configuration
LDAP Directory Port Number	The default for an LDAP directory server is 389.	389	Administration Server Configuration and Messaging Server Configuration
Administrator ID and Password	Administrator in charge or responsible for configuration information. Password for the Administrator	Admin PaSsWoRd	Administration Server Configuration
User and Group Tree Suffix	The distinguished name of the LDAP entry at the top of the directory tree, below which user and group data is stored.	o=usergroup	comm_dssetup.pl Perl script
Directory Manager DN and Password	The privileged directory administrator, comparable to superuser in UNIX. Typically, this administrator is responsible for user and group data. Password for the Directory Manager.	cn=Directory Manager pAsSwOrD	comm_dssetup.pl Perl script and Messaging Server Configuration
Administration Domain	A region of administrative control.	System Lab	Administration Server Configuration

Administration Server Initial Runtime Configuration Worksheet

When you run the Administration Server initial runtime configuration program through the Java Enterprise System installer, record your installation parameters in the following table. You will need some of these parameters for the Messaging Server initial runtime configuration. You might also refer to your Directory Server Installation Worksheet to answer certain questions.

Table 11-3 Administration Server Initial Runtime Configuration Program Parameters
Parameter	Description	Example
Fully Qualified Domain Name	Fully qualified domain name for the host machine.	svr1.west.sesta.com
Server Root Definition	Installation Root of the Administration Server dedicated to holding the server program, configuration, maintenance, and information files.	/var/opt/mps/serverroot
UNIX System User	Certain privileges designated to system users to ensure they have appropriate permissions for the processes they are running. Always use root.	root
UNIX System Group	The group to which certain UNIX System users belong. Always use other.	other
Configuration Directory Server	Host and Port specified on Directory Server Installation Worksheet.	Host svr1.west.sesta.com Port 390
Configuration Directory Server Administrator and Password	Administrator ID specified on Directory Server Installation Worksheet. Password of Administrator ID	Admin PaSsWoRd
Administration Domain	A region of administrative control. If you have installed Messaging Server and Directory Server on the same machine, then you should choose the same Administration Domain on Directory Server Installation Worksheet.	System Lab2
Administrative Server Port	A unique port number dedicated to the Administration Server.	5555

Choosing Which Messaging Server Components to Configure

When you install Messaging Server software, the Java Enterprise System installer installs all the Messaging Server packages. You then configure the appropriate Messaging Server component (MTA, Message Store, Messenger Express, MMP) on a Messaging host through the Messaging Server configuration program.

The following table shows which components you need to configure for each type of Messaging host.

Table 11-4 Which Messaging Server Components to Configure?
Type of Messaging Host Being Configured	Needs These Components Selected in the Configurator Program
MTA Relay	Message Transfer Agent
Message Store (back end)	Message Transfer Agent, Message Store, Messenger Express Note: You need to configure the store for an MEM proxy after configuration is done.
Messenger Express (front end only, no store or SMTP function)	Messenger Express, Messaging Multiplexor Note: If you are only configuring Messenger Express, you must also select the Message Store and the MTA, or at least be able to point to an existing MTA.
Message Multiplexor (front end only, no store or SMTP function)	Messaging Multiplexor


Note	Configuring the LMTP delivery mechanism requires configuration on both the relay machines and on the back end stores. See the Sun Java System Messaging Server Administration Guide for instructions on configuring LMTP.

Disabling the sendmail Daemon

Prior to installing Messaging Server, you should disable the sendmail daemon if it is running. The Dispatcher, under which the Messaging Server SMTP server runs, needs to bind to port 25. If the sendmail daemon is running (on port 25), the Dispatcher will not be able to bind to port 25.

To Disable the sendmail Daemon

Change to the /etc/init.d directory.

cd /etc/init.d

Stop the sendmail daemon if it is running.

./sendmail stop

Modify /etc/default/sendmail by adding MODE="".

If the sendmail file does not exist, create the file and then add MODE="".

If a user accidentally runs sendmail start, or if a patch restarts sendmail, then adding this modification prevents sendmail from starting up in daemon mode.

Previous Contents Index Next
Sun Java System Messaging Server 6 2004Q2 Deployment Planning Guide