This section describes installation considerations that help you prepare to install Messaging Server.
Resource Contention. To avoid resource contention between 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 root.
Messaging Server Base Directory. The Messaging Server is installed into a directory referred to as msgsvr-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, Access Manager, and Administration Server) on the Messaging Server host, you do not have to upgrade those components and Messaging Server should continue to operate.
Using a Messaging Server 6 2005Q4 Front End with a Messaging Server 6.3 Back End. If you choose to use a Messaging Server 6.3 back end with a Messaging Server 6 2005Q4 front end, you need to configure the front end to run without an Admin Server as follows:
Install and configure the Messaging Server 6.3 back end using the Communications Suite 5 installer.
Run the Java Enterprise System 2005Q4 installer to install the Messaging Server 6 2005Q4 front end and choose the Configure Later option when prompted.
Open MsgServer-base/lib/config-templates/DevsetupDefaults.properties in a text editor.
Change the following line:
ADMINSERVER_SERVERROOT_CONF = /etc/mps/admin/v.5.2/shared/config/serverroot.conf |
to:
ADMINSERVER_SERVERROOT_CONF = NO_ADMIN_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.
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 |
Access Manager (Web Server port) |
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 6.3 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 |