Administering Your Messenger Express Multiplexor

This section describes the basic administration capabilities of the Messenger Express Multiplexor.

To Configure and Administer SSL

To configure and administer SSL (otherwise known as Secure Sockets Layer) for your Messenger Express Multiplexor, refer to To Enable SSL and Selecting Ciphers

To Set Up Multiple Proxy Servers

To set up multiple Messenger Express Multiplexors that are addressed by a single name, you can use a session-aware load balancing device. With this device, all requests can be routed from any given client to a unique server.

To Manage Different Versions of Messaging Server and Messenger Express Multiplexor

If you use different versions of Messaging Server for the Messenger Express Multiplexor and the back-end mail hosts, you need to update the Messenger Express static files to ensure compatibility between the servers.

The static files which make up the Messenger Express interface are served directly from the Messenger Express Multiplexor, not the user’s mail host. The Multiplexor finds these files in the msg_svr_base/config/html directory.

To update these files in order to ensure compatibility between servers, replace the entire contents (which consist of these static files that make up the Messenger Express interface) of the directory msg_svr_base/config/html in the newer version of Messaging Server with the entire contents of the same directory in the older version of Messaging Server.

For example, if the back-end messaging servers use Messaging Server 6 2003Q4 and you have installed Messaging Server 6 2005Q4 as the Messenger Express Multiplexor, you need to replace the entire contents of the directory msg_svr_base/config/html of the Messenger Express Multiplexor with the contents of the same directory from the Messaging Server 6 2003Q4 back-end server. When you eventually upgrade Messaging Server 6 2003Q4 to Messaging Server 6 2005Q4, you can update these static files in directory msg_svr_base/config/html for the Messenger Express Multiplexor server as well.

To Configure the Port of the Back-end Messaging Server with the Messenger Express Multiplexor

If you want to configure the port of the back-end HTTP Messaging Server with the Messenger Express Multiplexor, use the following configutil command on your Multiplexor machine:

local.service.http.proxy.port.hostname

where hostname is the host of the back-end HTTP Messaging Server.

For example, if the host name of the back-end messaging server is sesta.com and the port number is 8888, the command would be in the following format:

configutil -o local.service.http.proxy.port.store.sesta.com -v 8888

local.service.HTTP.proxy.port applies to all back-end message stores except those which have their own port (same as local.service.proxy.admin).

To Configure Single Sign-on

Single sign-on must be configured on the Messenger Express Multiplexor machine in the same way as the Messaging (HTTP) server, with the following additional configurations:

configutil -o local.service.http.proxy.admin -v store_administrator

where store_administrator is the back-end store administrator specified during your back-end Messaging Server installation.

configutil -o local.service.http.proxy.adminpass -v store_admin_password

where store_admin_password is the back-end store administrator password specified during your back-end Messaging Server installation.

If you are using multiple back-end Messaging Servers that use different store administrators and passwords, you can configure them individually by appending the fully qualified host name to each configuration variable in Messenger Express Multiplexor:

configutil -o local.service.http.proxy.admin.hostname -v store_administrator

configutil -o local.service.http.proxy.adminpass.hostname -v store_admin_password

where hostname is the host of the back-end HTTP Messaging Server, store_administrator and store_admin_password are the back-end store administrator and password specified during your back-end Messaging Server installation.

To log the user into the back-end servers, Messenger Express Multiplexor uses the proxyauth login command. To enable proxyauth, use the following configutil parameter on the back-end message store:

configutil -o service.http.allowadminproxy -v 1

If Single sign-on is enabled through the Messenger Express Multiplexor, it does not need to be configured on the back-end HTTP Messaging Servers.