Chat now with support
Chat with Support

Coexistence Manager for GroupWise 1.7.1 - Quick Start Guide

Coexistence Manager for GroupWise Mail Connector

The Coexistence Manager for GroupWise Mail Connector is a Windows service that monitors SMTP traffic between GroupWise and Exchange to resolve calendar-email incompatibilities. The service permits delivery of functional event invitations, acceptances, declines, cancellations, and reschedules, including for complex recurring meeting patterns.

The Mail Connector functions as a passive SMTP interface between GroupWise and Exchange. That is, the Mail Connector does not store output of processed messages. The Mail Connector translates message elements that would otherwise be lost or misunderstood by the other mail system, and converts messages containing calendar data, while other messages simply pass through to the destination server.

Before introducing Coexistence Manager for GroupWise, Ellen configures Novell directory object records to permit internal SMTP mail-routing during coexistence. SMTP mail routing can be configured for either single- domain or multi-domain environments, and Ellen prefers using smart hosts to configure a single-domain routing scheme, as shown here.

She configures Exchange to route mail to a smart host if Exchange determines the recipient is not in the local internet domain, via the targetAddress attribute in the AD object record. Meanwhile, she configures GroupWise to do the same thing in reverse for a recipient whose local internet domain address does not occur in any Novell directory object record. Then she configures both smart hosts to point to the Coexistence Manager for GroupWise Mail Connector server.

Once installed, Coexistence Manager for GroupWise occasionally encounters an incompatibility between GroupWise and Exchange that it cannot correct by any practical means. Coexistence Manager for GroupWise is able to detect most such instances and insert a brief note into the message body notifying the recipient and recommending a manual resolution.

For example, if this invitee is on an Exchange server in a different time zone from your GroupWise server: The counterproposed date shown here may be a day off from the actual date, due to incompatibilities between the GroupWise and Exchange servers.

Your calendar will process the counterproposal correctly, but you should then check your calendar to verify the date for your own information.

In some uncommon scenarios, uncorrectable calendar incompatibilities prevent the completion of whatever the sender intended. In such cases, Coexistence Manager for GroupWise will abort the attempt rather than relay an item that is known to fail.

Coexistence Manager for GroupWise Free/Busy Connector

Ellen knows that calendar features are popular among all American Widgets users, but obviously the features will be useful only if they have access to accurate, timely free/busy information for all users. Coexistence Manager for GroupWise’s Free/Busy (F/B) Connector is a coordinated set of applications that together let Exchange and GroupWise query the calendar availability of each other's users. This sharing of free/busy data between GroupWise and Exchange makes possible automatic calendar updates when accepting a meeting invitation, or changing the day/time or canceling a meeting, or making some other change to an existing meeting or recurring series.

When a user in one environment requests F/B information about a user in the other environment, the asking server’s query must be translated into a form the other server will understand. Likewise, the data reply has to be translated into a form that the asking server will understand. This is true of free/busy queries and replies in both directions, and a separate translator application is required for each direction.

Both the Exchange and GroupWise servers also require services to facilitate data communications between themselves and external data sources and destinations (each other). Exchange uses an Exchange Web Service (EWS) to enable communications between Exchange and other applications, while GroupWise requires a similar application for the same purpose. Exchange also requires an Autodiscover service to track and report the location (URL) of the EWS. Microsoft provides EWS and Autodiscover services that are suitable for incoming queries and outbound replies, but are not suitable for queries and replies in the other direction.

To support bidirectional F/B queries and replies between GroupWise (version 8 or later) and Exchange (with Outlook 2007 or later clients), Coexistence Manager for GroupWise’s Free/Busy Connector provides the five necessary subcomponents that Microsoft does not provide, as shown here.

(Other Coexistence Manager for GroupWise subcomponents, not shown here, support scenarios with GroupWise 7 and an API Gateway, and/or Outlook 2003 clients with Exchange 2003 or 2007 servers.)

Ellen maps out a deployment plan for American Widgets and installs the subcomponent software. Next she uses Coexistence Manager for GroupWise’s Directory Connector to run a bidirectional directory update between the two. And finally, she configures the F/B Connector components so the service will work in her American Widgets environment, according to her preferences.

Getting started

Coexistence Manager for GroupWise system requirements are documented in the RTM Release Notes that accompany every Coexistence Manager for GroupWise release.

Deployment considerations

Before installing Coexistence Manager for GroupWise, it is important to document a deployment plan. The plan should specify the components, where they will be installed, and how many instances will be required. You can install and configure the Coexistence Manager for GroupWise components in any order you like, but consider that the Directory Connector provides directory updates the Free/Busy Connector needs to facilitate its functionality.

It is possible to install two or more Coexistence Manager for GroupWise components on a single server, but some production environments with a greater volume of message and free/busy traffic may benefit from installing on separate servers for optimal performance. One common approach involves installing the three Coexistence Manager for GroupWise components to three separate computers, one for each component.

Environments with very high message volume may also deploy multiple Mail Connectors and/or install the Free/Busy components on different computers:

For more information, review Mail Connector Deployment Options in chapter 3 of the Coexistence Manager for GroupWise User Guide.

Coexistence Manager for GroupWise’s Free/Busy Connector subcomponents are deployed in different configurations for different combinations of GroupWise environment and Exchange environment. These scenarios and their associated deployment considerations are fully described in the FBC Configuration Guide.

The relative processing and hardware requirements of the different components will vary based on the typical activity in each environment. However, the Free/Busy Connector will see heavier demand in many environments. The Mail Connector will also have requirements around mail and calendar processing, but the volume of required updates may not be excessive for many GroupWise and Exchange coexistence environments. Directory Connector activity is typically scheduled and requires resources only during active processing. As a result, the demands and requirements are typically lower than either the Mail Connector or Free/Busy Connector.

Related Documents