Coexistence Manager for Notes 3.8.4 - Quick Start Guide

The solution: Quest Coexistence Manager for Notes

Quest Quest Coexistence Manager for Notes (CMN) provides rich directory, email and calendar coexistence features between Lotus Notes and a local Microsoft Exchange, or a hosted Exchange environment. CMN can be deployed either for a finite transition period, as when migrating from Notes to Exchange, or for indefinite or even permanent coexistence.

To accommodate the three elements of Notes–Exchange coexistence, Quest Quest Coexistence Manager for Notes includes three primary components:

The three CMN components are separate, but designed to work together in any combination to suit a broad range of coexistence needs. All three components are described in greater detail in the CMN User Guide.

Getting started

These topics explain how to prepare for and install CMN to your greatest benefit.

Deployment considerations

Before installing CMN, it is important to document a deployment plan. The plan should specify the components you will install, where they will be installed, and how many instances of each will be required. Remember to accommodate all system requirements (as documented in the CMN Release Notes) when planning component deployments. You can install and configure any number of CMN components, in any order you like, but consider that the Directory Connector provides directory updates that the Free/Busy Connector will need to function.

It is possible to install two or more CMN components on a single server, but production environments with higher volumes of message and free/busy traffic may benefit from installing on separate servers for optimal performance. One common approach installs the three CMN components to three separate computers, one for each component (in addition to the Free/Busy Connector’s QCalCon, which must be installed separately on a Domino server).

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

For technical reasons, the QCalCon subcomponent of the Free/Busy Connector must be installed on a Domino server. But if the Domino environment contains more than one Domino server, QCalCon is installed on only one server. (Other Domino servers must be configured to find and use the single QCalCon instance on the “bridgehead” server.) The other four Free/Busy Connector subcomponents can be installed on a single computer, although deployment to two separate computers (as illustrated in chapter 4 of the CMN User Guide) will improve performance in environments with higher volumes of F/B queries and replies.

The relative processing demands and hardware requirements of CMN components vary based on typical activity in different environments. The F/B Connector usually exerts the heaviest demand on computing resources, compared to the other two CMN components. The Mail Connector runs continuously, but in most settings its email and calendar remediation functions are less demanding than the F/B Connector. Meanwhile, Directory Connector activity is typically scheduled, and consumes resources only during active processing, so its resource requirements are usually lower than either the Mail Connector or F/B Connector.

Installation instructions for CMN components appear below. After installation, CMN components must be configured before they can be used. Deployment and configuration options for the three primary CMN components vary to accommodate local environments and needs. These considerations are more fully explained in chapters 2, 3 and 4 of the User Guide and, for the Free/Busy Connector, in the FBC Scenarios Guide.

AutoRun

The installation media for CMN includes an autorun.exe application. The AutoRun application provides access to useful information and links to tools needed for the CMN product, including:

The Install tab includes links to install the various CMN components.