Chat now with support
지원 담당자와 채팅

Coexistence Manager for GroupWise 1.7.1 - Quick Start Guide

About the Coexistence Manager for GroupWise documentation

The documentation for Quest Coexistence Manager for GroupWise includes these documents:

Release Notes (printable PDF): Describes the current Coexistence Manager for GroupWise release—any new and enhanced features, resolved issues, and known issues. Also documents minimum and recommended installation requirements, and provides Quest contact information.
Quick-Start Guide (printable PDF): An orientation to the product's basic purposes, features and capabilities, with brief case studies showing how its primary components are most commonly used within a typical coexistence scenario. Also documents System Requirements, and explains how to download and install the software.
Coexistence Manager for GroupWise User Guide (printable PDF): Overview of features, deployment considerations and typical configurations for the Coexistence Manager for GroupWise Directory Connector, Mail Connector and Free/Busy Connector. Also provides process instructions and application notes for installing, configuring, starting and running the Coexistence Manager for GroupWise Directory Connector and Mail Connector, and explains how to configure the GroupWise and Exchange/AD environments to work with these Coexistence Manager for GroupWise components. (The same information for the F/B Connector is deferred to a separate FBC Configuration Guide—see next item below.)
Coexistence Manager for GroupWise FBC Configuration Guide (printable PDF): Process instructions and application notes for installing and configuring Coexistence Manager for GroupWise’s Free/Busy Connector (FBC). An introductory chapter is followed by 12 chapters that each describe the complete process for installing and configuring the FBC for a particular combination of GroupWise environment and Exchange environment, for either a single- or multi-namespace environment.
Coexistence Manager for GroupWise Program Parameters Reference (printable PDF): Listing of all Coexistence Manager for GroupWise program parameters that are not associated with UI fields in Coexistence Manager for GroupWise’s Management Console, with descriptions and default values and usage/application notes. (Parameters associated with UI fields do appear in the Configuration.xml files, but should not be edited manually.)
Management Console Online Help (three compiled Windows Help files, one for each Coexistence Manager for GroupWise component): Context-sensitive instructions and application notes for the various screens and features of Coexistence Manager for GroupWise’s Management Console utility.

This table shows where you can find particular types of information about particular Coexistence Manager for GroupWise components:

 

for Dir Connector & Mail Connector

for Free/Busy Connector

Introduction and orientation:

— — Coexistence Manager for GroupWise Quick-Start Guide and User Guide — —

Installation instructions:

— — Coexistence Manager for GroupWise Quick-Start Guide — —

Configuration instructions:

Coexistence Manager for GroupWise User Guide

Coexistence Manager for GroupWise FBC Configuration Guide

Operating instructions:

— — Coexistence Manager for GroupWise User Guide — —

Troubleshooting info:

Coexistence Manager for GroupWise User Guide

Coexistence Manager for GroupWise FBC Configuration Guide

The Coexistence Manager for GroupWise application Help files contain the same information as the User Guide, but make the information available on-screen at the push of a button (from the Coexistence Manager for GroupWise Management Console).

All Coexistence Manager for GroupWise documentation is intended for network administrators, consultants, analysts, and any other IT professionals who will install or use the product components, or who may help plan for their use in a coexistence scenario. All of these documents, including the online Help, are bundled and installed with the product, and all except the Help files are also available separately at Quest's Support Portal.

IMPORTANT: Coexistence Manager for GroupWise provides coexistence solutions for several GroupWise versions, whose directory services are variously named NDS and eDirectory. Coexistence Manager for GroupWise supports both NDS and eDirectory. For simplicity, our Coexistence Manager for GroupWise documentation uses the more generic term "Novell directory" to specify either NDS or eDirectory.

Note also that the GroupWise Global Address Book (also called Global Address List, or GAL) is different from the Novell directory. The GAL is a separate entity, periodically refreshed from the Novell directory, but the GAL is then an independent data source until it is next refreshed from the Novell directory. This is an important distinction for understanding the data flows facilitated by Coexistence Manager for GroupWise's Directory Connector.

Product overview

The GroupWise and Exchange environments offer similar email, calendar and directory capabilities, but implement many of these features differently. An effective coexistence between the GroupWise and Exchange environments will address three primary concerns:

Quest Coexistence Manager for GroupWise (Coexistence Manager for GroupWise) provides rich directory, email and calendar coexistence features between Novell GroupWise and Microsoft Exchange — both an on-premises servers and hosted Exchange environments. Coexistence Manager for GroupWise can be deployed either for a finite transition period, as when migrating from GroupWise to Exchange, or for indefinite or even permanent coexistence.

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

Directory Connector (DC): Updates directory data between the Novell directory and Active Directory, configurable for any number of servers.
Mail Connector: Remediates calendar-data emails to permit delivery of fully functional meeting invitations, acceptances/declines, reschedules and cancellations, and task data.
Free/Busy (F/B) Connector: Facilitates lookups of calendar free/busy data between users in the two different environments.

Coexistence Manager for GroupWise’s three components are separate, but designed to work together in any combination to suit a broad range of coexistence needs, as shown in the illustration. The Scenario case study later in this Guide explains these components in greater detail—what they do, and how they are installed and configured in typical scenarios.

Scenario case study

American Widgets Corp. recently acquired a regional rival, Midwest Widgets Inc. Naturally, American Widgets wants to integrate all of Midwest Widgets’ administrative operations, processes and infrastructure with its own operations, but American Widgets and Midwest Widgets have until now run their email and collaboration applications in different worlds. American Widgets is a Microsoft shop, using an Exchange 2010 server and Outlook clients for the email and calendaring needs of its 26,000 employees. But Midwest Widgets’ 8,000 workers have been using Novell GroupWise for those same functions.

American Widgets doesn’t want to force either group to immediately give up the apps they’ve used daily. Its CIO, Ellen Oliver, believes they can implement a coexistence between the two. She is hopeful a good coexistence strategy will allow the two groups to communicate and collaborate effectively and uneventfully. Ellen knows that she is going to need some specialized solutions to accomplish the integration of the two disparate mail, calendar and directory systems.

Ellen knows she can configure SMTP routing between the two environments, but she also knows SMTP routing alone will be insufficient because it will forfeit email fidelity and calendaring features. Ellen has heard of a Quest product called Coexistence Manager for GroupWise (Coexistence Manager for GroupWise) that facilitates a richer coexistence solution between GroupWise and Exchange. Coexistence Manager for GroupWise addresses the three primary elements of coexistence with three components: a Directory Connector for cross-environment directory updates, a Mail Connector for SMTP email and calendar remediation, and a Free/Busy Connector to facilitate free/busy queries between the two environments.

The full installation and configuration details are beyond the scope of this summary narrative, but we will briefly view each component and see how it addresses Ellen’s coexistence needs.

Coexistence Manager for GroupWise Directory Connector

The Quest Coexistence Manager for GroupWise Directory Connector (DC) updates directory information between the Novell directory and Active Directory (AD). Within the DC component, one or more individual connectors are defined, each to copy directory data in only one direction. A bidirectional update is accomplished by defining a pair of connectors to run sequentially in opposite directions.

Note that while Directory Connector is the name of the Coexistence Manager for GroupWise component as a whole, and of the Windows service that performs directory updates, the term connector also refers to the individual processes within the component, each defined to perform a particular directory update in just one direction. Think of the DC service as the engine that does the actual work, while the individual connectors are the instructions that tell the engine how to apply its capabilities. A connector definition tells the DC service the direction of the update, where the source objects reside, which object types to include, where within the target server the objects should be copied, access credentials to both the source and target servers, when to run updates, and so forth.

For each defined connector, the Coexistence Manager for GroupWise Directory Connector sends a query to the source directory (step 1 in the illustration below), which then (2) replies by transmitting its object data back to the Directory Connector. The illustration below shows the process for a typical GroupWise-to-Exchange connector (coexisting with GroupWise 8 or later).

External contact objects in the Novell directory reside in a shared address book, reserved for Coexistence Manager for GroupWise use to keep contact records for external AD objects separate from Novell’s own local users, and thereby prevent directory loops between the two systems. In a connector that updates AD with Novell directory objects, as shown here, the GroupWise source data is drawn only from the Global Address Book.

The Directory Connector then (3) maps the attributes of the GroupWise source objects to the corresponding contact attributes in AD. If an object in the source already exists in the target, a configuration setting tells the connector whether object data collected in the source should overwrite any corresponding data in the target.

Finally (4), the DC passes the data to the reserved cn=cmg container within Active Directory. If a target container by that name does not already exist, Coexistence Manager for GroupWise will create it, within a target container that you specify. The cn=cmg container thus will be a subset of the specified target container ("ou=users" in the illustration).

When a connector is defined to run from Exchange to GroupWise, the process works approximately the same way in reverse. Coexistence Manager for GroupWise’s Directory Connector queries the source Active Directory (step 1 in the illustration below), which then (2) replies by transmitting its object data back to the DC.

In an Exchange-to-GroupWise update, as shown below, AD sends object records for its entire ou=users container, which in AD includes the contact records in cn=cmg, a subcontainer within ou=users. The Coexistence Manager for GroupWise Directory Connector therefore (3) filters (removes) the objects that were in the source cn=cmg container, to prevent object looping, before finally (4) passing the filtered object data on to a shared GroupWise address book. As noted above, the GroupWise shared address book is reserved for Coexistence Manager for GroupWise use, to keep external AD objects separate from Novell’s own local users, to prevent looping.

Each of the query–reply processes illustrated above is defined within the Coexistence Manager for GroupWise Directory Connector as one connector. Two connectors defined for opposite directions, and run sequentially, together facilitate a bidirectional update.

The DC lets you define as many connectors as you need to facilitate separate directory updates for different administrative entities or geographic locations, etc., and/or for updates among multiple directory servers on either or both sides. If multiple AD-to-GroupWise connectors are defined, you can define them to flow to different, separate shared address books.

Coexistence Manager for GroupWise’s Directory Connector service is started manually, and once started it runs continuously. The DC service is idle most of the time except for periodic momentary checks to determine whether a defined connector is scheduled to run. If so, the service verifies that any prerequisite connectors have already run, and then launches the connector. When the connector finishes, the DC service returns to its idle state, waiting for the next scheduled connector.

셀프 서비스 도구
지식 기반
공지 및 알림
제품 지원
소프트웨어 다운로드
기술 설명서
사용자 포럼
비디오 자습서
문의처
라이센싱 지원가져오기
기술 지원
모두 보기
관련 문서