Chat now with support
Chat with Support

Coexistence Manager for GroupWise 1.7 - User Guide

About the CMG documentation suite Introduction CMG Directory Connector
Directory Connector overview Installation and configuration DC Management Console Connector Creation Wizard Connector Advanced Settings Running and stopping the Directory Connector service
CMG Mail Connector CMG Free/Busy Connector The Log Viewer Appendix A: Known limitations Appendix B: Troubleshooting Appendix C:Configuring CMG logging

Redundant CMG Mail Connectors

Multiple instances of the Mail Connector can be deployed for load balancing and to provide redundant mail paths. As illustrated below, any CMG server can receive messages from any mail server defined in the configuration file, and likewise can relay messages to any of the defined destination servers.

In multiple-CMG schemes, the CMG servers can be load-balanced by MX-record priority designations used by the source mail system or a more formal load-balancing mechanism.

Message distribution among multiple servers

CMG's Mail Connector interprets and honors MX priority settings to intelligently distribute messages in prioritized round-robin fashion. Priority designations run in reverse-numerical order, where the highest priority is 0, and higher priority numbers represent less preferred servers.

When MX resolution is enabled for CMG’s outbound servers, the Mail Connector attempts a connection at the highest priority level, and if unsuccessful attempts a connection with another server (if any) at the same priority level, or at the next lower priority level only if no server at the higher priority level is available. Within each group of servers at the same priority level, the Mail Connector randomly selects a server in the group for its first connection attempt, and then if unsuccessful proceeds to the other servers in random round-robin fashion.

If MX resolution is not enabled for the CMG servers, messages are distributed in random round-robin fashion among all configured servers.

CMG and hosted Exchange environments

CMG’s Mail Connector is easily configured to work with a hosted Exchange environment such as Microsoft’s Office 365. A CMG connection with a hosted environment is configured in the Management Console for Mail Connector, and also requires some minor accommodations in server configurations, as noted in the Mail Connector installation and configuration instructions.

There are no performance tips unique to a hosted Exchange configuration with CMG. Hosted Exchange is a slight variation in CMG’s server connection validation code; everything else is treated just like regular message traffic.

Mail Connector installation and configuration

* 
NOTE: If coexisting with GroupWise 7: Note that inbound external (internet) mail delivered to GroupWise 7 cannot be routed to Exchange users, due to the way the proxy GWIA receives messages and the way messages are written into the production GWIA. To avoid this problem, you could direct inbound internet mail to Exchange instead.

The process of installing, configuring and activating the CMG Mail Connector consists of these general steps, all of which are explained in more detail below. This process begins with the assumption that the GroupWise and Exchange environments are operational, and that the environments conform to the CMG system requirements specified for the current release of CMG (as documented in the most recent RTM Release Notes).

1
Install the CMG Mail Connector software.
2
If necessary: Configure DNS Server for CMG.
This step applies only if you will use MX priorities to distribute message traffic among multiple mail servers. Add MX records for both the GroupWise and Exchange servers to specify the mail servers responsible for handling emails. If you intend to connect CMG with a hosted Exchange environment (e.g., Office 365), be sure to allow inbound routing from the internet to CMG on port 25, and set up MX records or change the internal inbound routing to point to CMG instead of pointing directly to GroupWise.
3
Run the CMG Management Console.
CMG includes a Management Console to configure the Mail Connector service (and the other CMG components) for your environment. Since these settings control the Mail Connector’s functions and scope, the Management Console must be run before the service can be started.
4
Review and (optionally) update other Mail Connector configuration options.
Other configuration options may be set in the .xml configuration file, and elsewhere, although they are all optional.
5
Start the Mail Connector.
The CMG Mail Connector is typically run as a Windows service, but can also be run as a console application. In either case, once started, the application runs with no further input until it is stopped.
6
Reconfigure the mail servers for CMG.
* 
IMPORTANT: These server reconfigurations should occur only after CMG is started (preceding step). Otherwise the mail servers would (at least briefly) be trying to send mail to a non-existent destination.
Quest Coexistence Manager for GroupWise runs in conjunction with one or more GroupWise and Exchange mail servers. As such, the mail servers must be configured to recognize and route mail via CMG.
7
Optional: Configure TLS/SSL encryption.
The Mail Connector supports the TLS encryption protocol (SSL 3.1).
Related Documents