Sun Java System Messaging Server 6 2005Q4 Administration Guide

Setting Up the Messaging Multiplexor

During the initial runtime configuration of Messaging Server, you determined if you wanted to configure the MMP on a machine. You could either set it up on the same machine as your Messaging Server or set it up on a separate machine.

Note –

MMP does not cache DNS results. A high quality caching DNS server on the local network is a requirement for a production deployment of Messaging Server.

The following sections describe how to set up the MMP:

More information about the MMP can be found in the following:

Chapter 5, Messaging Multiplexor Configuration, in Sun Java System Messaging Server 6 2005Q4 Administration Reference

Before You Configure MMP

Before configuring the MMP:

Choose the machine on which you will configure the MMP. It is best to use a dedicated machine set aside for the MMP.

Note –
It is recommended that the MMP not be enabled on a machine that is also running either the POP or IMAP servers.

If you install MMP on the same machine as Messaging Server, you must make sure that the POP and IMAP servers are set to non-standard ports. That way, the MMP and Messaging Server ports will not conflict with one another.
On the machine that the MMP is to be configured, create a UNIX system user to be used by the MMP. This new user must belong to a UNIX system group. See Creating UNIX System Users and Groups
Set up the Directory Server and its host machine for use with Messaging Server, if they are not already set up. See To Prepare Directory Server for Messaging Server Configuration
If the MMP is upgraded before the backend servers, customers should set the Capability option in ImapProxyAService.cfg to match the response to the capability command from the older backend. This would be:

IMAP4 IMAP4rev1 ACL QUOTA LITERAL+ NAMESPACE UIDPLUS CHILDREN LANGUAGE XSENDER X-NETSCAPE XSERVERINFO

Note that line break is for editorial clarity, and that the configuration value must be on one line.

Multiplexor Configuration

To configure the MMP, you must use the Messaging Server configure program, which gives you the option of enabling the Messaging Multiplexor. For detailed information about the configure program see Creating the Initial Messaging Server Runtime Configuration

To Configure the MMP

Steps

Put Sun Java System Messaging Server on the machine where you are installing and configuring the MMP.

Configure the MMP by creating the Messaging Server Initial Runtime Configuration. See Creating the Initial Messaging Server Runtime Configuration

Note the following exception: when installing Messaging Server, check only the Messaging Multiplexor option.

Multiplexor Files

The Messaging Multiplexor files are stored in the msg_svr_base/config configuration file directory. You must manually edit the configuration parameters in the Messaging Multiplexor configuration files listed in Table 7–1. For a complete description of all MMP configuration parameters, see the Multiplexor Configuration Parameters in Sun Java System Messaging Server 6 2005Q4 Administration Reference.

Table 7–1 Messaging Multiplexor Configuration Files


File	Description
`PopProxyAService.cfg`	Configuration file specifying configuration variables used for POP services.
`PopProxyAService-def.cfg`	POP services configuration template. File comes into existence only after initial MMP start with `start-msg mmp`
`ImapProxyAService.cfg`	Configuration file specifying configuration variables used for IMAP services.
`ImapProxyAService-def.cfg`	IMAP services configuration template. File comes into existence only after initial MMP start with `start-msg mmp`
`AService.cfg`	Configuration file specifying which services to start and a few options shared by both POP and IMAP services.
`AService-def.cfg`	Configuration template specifying which services to start and a few options shared by both POP and IMAP services. File comes into existence only after initial MMP start with `start-msg mmp`
`SmtpProxyAService.cfg`	Optional configuration file specifying configuration variables used for SMTP Proxy services. Required if you enable POP before SMTP; useful for maximizing support for SSL hardware even if POP before SMTP is not enabled. For more information on POP before SMTP, see Enabling POP Before SMTP
`SmtpProxyAService-def.cfg`	Configuration template specifying configuration variables used for SMTP Proxy services. File comes into existence only after initial MMP start with `start-msg mmp`

As an example, the LogDir and LogLevel parameters can be found in all configuration files. In ImapProxyAService.cfg, they are used to specify logging parameters for IMAP-related events; similarly, these parameters in PopProxyAService.cfg are used to configure logging parameters for POP-related events. In SmtpProxyAService.cfg, they are used to specify logging for SMTP Proxy-related events.

In AService.cfg, however, LogDir and LogLevel are used for logging MMP-wide failures, such as the failure to start a POP, IMAP, or SMTP service.

Note –

When the MMP is configured or upgraded, the configuration template files will be overwritten.

Starting the Multiplexor

To start, stop, or refresh an instance of the Messaging Multiplexor, use the one of the following commands in Table 7–2 located in the msg_svr_base/sbin directory:

Table 7–2 MMP Commands


Option	Description
`start-msg mmp`	Starts the MMP (even if one is already running).
`stop-msg mmp`	Stops the most recently started MMP.
`refresh mmp`	Causes an MMP that is already running to refresh its configuration without disrupting any active connections.

Modifying an Existing MMP

To modify an existing instance of the MMP, edit the ImapProxyAService.cfg and/or PopProxyAService.cfg configuration files as necessary. These configuration files are located in the msg_svr_base/config subdirectory.