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

Step 1: Install Coexistence Manager for GroupWise Mail Connector software

Verify that Microsoft .NET Framework 2.0, and 4.0 Full Framework are installed on the computer that will host the Mail Connector. (The Coexistence Manager for GroupWise Installer provides a link to these, in case they are not already installed.)

The Coexistence Manager for GroupWise Mail Connector is installed by the same AutoRun installer that installs all components of the Quest Coexistence Manager for GroupWise product. If you have already installed one or more other components, just run the AutoRun installer again to install the Mail Connector. The AutoRun installer must be run on the computer where you want to the Coexistence Manager for GroupWise component to reside.

For complete installation instructions, see the Getting Started section of either the Quick-Start Guide or the associated Release Notes.

Step 2 (conditional): Configure DNS server for Coexistence Manager for GroupWise

NOTE: Conditional Step: This step applies only if you will use MX priority ranking to distribute message traffic among multiple mail servers. Skip this step if MX priorities will not be used.

Add MX records for both the GroupWise and Exchange servers to specify the mail servers responsible for handling emails. More than one MX record can be entered for a single domain name using more than one mail server, so the MX records can be prioritized to indicate the order in which the mail servers should be used. For example:

You will configure the Mail Connector for DNS MX resolution in a later step below.

For Coexistence Manager for GroupWise with a Hosted Exchange Environment

If you intend to connect Coexistence Manager for GroupWise with a hosted Exchange environment (e.g., Office 365):

Connection with a hosted Exchange environment also requires two slight changes within the Management Console for Mail Connector, as explained in the field notes later in this chapter.

Step 3: Run the Management Console for the Mail Connector

Coexistence Manager for GroupWise includes a Management Console to help you configure the Coexistence Manager for GroupWise Mail Connector. The MC Management Console edits the component’s configuration file according to your entries in the GUI screens.

Most of the processing options for your Mail Connector can be configured in the Mail Connector Management Console. Other operational options can be set manually, by entering or changing settings in the active configuration file, as described below in the next step of this process.

A later section of this chapter provides screen-by-screen field notes for the Mail Connector screens in the Console. Run the Management Console now, working through all the program screens, and then return here to continue.

Step 4 (optional): Review and update other Mail Connector configuration options

By default, Coexistence Manager for GroupWise is installed with the log42net utility to generate log files of Coexistence Manager for GroupWise components’ system activity. This information is critical to diagnosing any problems that may arise. Logging is enabled by default for all Coexistence Manager for GroupWise components.

The log42net utility may be configured to work a particular way with each Coexistence Manager for GroupWise component. The default configurations will be suitable for almost all organizations and circumstances, but you can customize logging features if you like.

Configuration instructions for logging are nearly identical from one component to another. See User Guide Appendix C.

DNS MX resolution may be enabled or disabled by a checkbox in the Mail Connector Management Console (on the Network Settings screen). If you will configure Coexistence Manager for GroupWise to enable DNS MX resolution, you may also want to reset the associated cache-update interval, by updating the <mxcacheupdateinterval> parameter value in Coexistence Manager for GroupWise's active .xml configuration file. This parameter sets the number of seconds you want MX lookups to be cached, and the default is 300 seconds (5 mins). You may want to increase this value to reduce the load on the DNS server and/or the network. You may want to decrease the value if you want changes to take effect faster or to allow for round-robin resolution.

To reset the cache-update interval for the DNS MX Resolution feature:

2
Find the <mxcacheupdateinterval> parameter, in the <root> node. If the <mxcacheupdateinterval> parameter does not already exist, create it as explained in the next step.
4
Close and Save the configuration file under the same filename.

The new settings will take effect the next time the Coexistence Manager for GroupWise service is restarted.

By default, the Mail Connector waits up to 5 seconds for an available socket channel before opening a new one (if none are then available). This is a "throttling" feature to enforce a time interval for Coexistence Manager for GroupWise to conclude its communications protocol with a channel before opening another. The actual delay, in seconds, is a "delay factor" (5 by default) x the ratio of the number of open channels to the maximum allowed number of channels. If you want to change the delay factor, you can manually edit the setting in Coexistence Manager for GroupWise’s active configuration file:

2
Find the <routerwaitsec> parameter in the <root> node of the Coexistence Manager for GroupWise Configuration file and update its value to suit your circumstances. The value specified (default=5) is the "delay factor."
3
Close and Save the configuration file under the same filename.

The new settings will take effect the next time the Coexistence Manager for GroupWise Mail Connector service is restarted.

By default Coexistence Manager for GroupWise will ignore any message larger than 30MB (including attachments), but you can change this value if you want to allow larger messages, or to prevent smaller messages. The <maxbodysize> parameter lets you set the maximum message size, in bytes, that Coexistence Manager for GroupWise will accept to process. The default is 31457280 bytes (30MB = 30 x 1024 x 1024).

To change the value:

2
Find the <maxbodysize> parameter in the <root> node of the Coexistence Manager for GroupWise Configuration file and update its value to suit your needs.
3
Close and Save the configuration file under the same filename.

The new setting will take effect the next time the Coexistence Manager for GroupWise Mail Connector service is restarted.

Related Documents