Sun and OracleChannel SunHow to BuyLog InEnglish

Sun Java Communications Suite 5 Installation Guide
  Search only this book
Search Help
View this book in:
Contained Within
Find More Documentation
Featured Support Resources
 Download this book in PDF (1689 KB)

Appendix A Messaging Server Pre-Installation Considerations and Procedures

This appendix describes considerations you need to think about, and procedures you need to perform, before installing Messaging Server.

This appendix contains the following sections:

Messaging Server Installation Considerations

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:

    1. Install and configure the Messaging Server 6.3 back end using the Communications Suite 5 installer.

    2. Run the Java Enterprise System 2005Q4 installer to install the Messaging Server 6 2005Q4 front end and choose the Configure Later option when prompted.

    3. Open MsgServer-base/lib/config-templates/DevsetupDefaults.properties in a text editor.

    4. 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.

Table A–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 

Access Manager (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 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

Messaging Server Installation Worksheets

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

Tip –

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

Directory Server Installation Worksheet

Record your Directory Server installation and configuration parameters. You will need these parameters when you install and configure your initial Messaging Server runtime configuration. For additional help, see the Sun Java System Messaging Server 6.3 Administration Guide.

Table A–2 Directory Server Installation Parameters

Parameter 

Description 

Example 

Used in 

Your Answer 

Directory Server instance(s) (server-root) or an Explicit Instance Directory 

An instance or directory on the Directory Server host dedicated to holding the server program, configuration, maintenance, and information files. 

Solaris 

Instance: /opt/SUNWdsee/ds6

Server Root: /var/opt/SUNWdsse/dsins1

Linux/HP-UX 

Instance: /opt/sun/ds6 

Server Root: /var/opt/sun/dsins1

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

Messaging Server Configuration 

 

LDAP Directory Port Number 

The default for an LDAP directory server is 389.

389

Messaging 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 root 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

 

Choosing Which Messaging Server Components to Configure

When you install Messaging Server software, the installer installs all the Messaging Server packages. You then configure the appropriate Messaging Server component (MTA, Message Store, Webmail Server, 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 A–3 Choosing Which Messaging Server Components to Configure

Type of Messaging Host Being Configured 

Needs These Components Selected in the Configurator Program 

MTA 

Message Transfer Agent 

Message Store (back end) 

Message Transfer Agent, Message Store 

Webmail Server (front end only, no store or SMTP function) 

Webmail Server 

Note: If you are only configuring Communications 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 

Webmail Server (for Communications Express) 

Webmail Server 

Webmail Server and Message Store 

Webmail Server, Message Transfer Agent, Message Store 

Note –

Configuring the LMTP delivery mechanism requires configuration on both the MTAs and on the back-end stores. See Chapter 16, LMTP Delivery, in Sun Java System Messaging Server 6.3 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.

ProcedureTo Disable the sendmail Daemon

  1. Change to the /etc/init.d directory.


    cd /etc/init.d

  2. Stop the sendmail daemon if it is running.


    ./sendmail stop

  3. 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.

    Note –

    In some cases (especially on Solaris 10), even after you run the /etc/init.d/sendmail stop command, sendmail is autorestarted. In this case, use the following command to stop the sendmail process:

    svcadmin disable network/smtp:sendmail