Chat now with support
Chat with Support

Coexistence Manager for GroupWise 1.7.1 - User Guide

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

Redundant Coexistence Manager for GroupWise Mail Connectors

Multiple instances of the Mail Connector can be deployed for load balancing and to provide redundant mail paths. As illustrated below, any Coexistence Manager for GroupWise 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-Coexistence Manager for GroupWise schemes, the Coexistence Manager for GroupWise 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

Coexistence Manager for GroupWise'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 Coexistence Manager for GroupWise’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 Coexistence Manager for GroupWise servers, messages are distributed in random round-robin fashion among all configured servers.

Coexistence Manager for GroupWise and hosted Exchange environments

Coexistence Manager for GroupWise’s Mail Connector is easily configured to work with a hosted Exchange environment such as Microsoft’s Office 365. A Coexistence Manager for GroupWise 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 Coexistence Manager for GroupWise. Hosted Exchange is a slight variation in Coexistence Manager for GroupWise’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 Coexistence Manager for GroupWise 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 Coexistence Manager for GroupWise (as documented in the most recent RTM Release Notes).

IMPORTANT: These server reconfigurations should occur only after Coexistence Manager for GroupWise is started (preceding step). Otherwise the mail servers would (at least briefly) be trying to send mail to a non-existent destination.
Related Documents