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 2: Prepare Your Exchange/AD and GroupWise environments

Coexistence Manager for GroupWise’s Directory Connector requires that the target Active Directory server have the Exchange schema extensions.

The account configured to run the DC service must be an Exchange domain user account with membership in Exchange View-Only Administrators, and delegated full control to the target OU, and full control of the OUs/containers where the AD user objects currently reside—to ensure Coexistence Manager for GroupWise has access to properly join to the merged user objects and prevent the creation of duplicate contacts.

Coexistence Manager for GroupWise’s Directory Connector requires a non-admin GroupWise user account (for GroupWise 2014) or a GroupWise admin account (for any other GroupWise version) with valid Internet Address and Name attributes, and sufficient permissions to:

For multiple GroupWise servers, one such account is required for each server.

Coexistence Manager for GroupWise requires replication of this attribute to the Global Catalog so that ou=users will appear in the source list of OUs in the Connector Creation Wizard, when creating an Exchange-to-GroupWise connector. The procedure:

2
In the console tree, under Active Directory Schema/Attributes: Click Attributes.
3
In the details pane: Right-click the showInAddressBook attribute, and select Properties.
4
Select Replicate this attribute to the Global Catalog checkbox.

The Directory Connector needs to know which communications port to use for data transmissions between the DC service and the DC Management Console, on the server where these applications reside. The port number for this is set to 9081 by default, and this will be the correct setting in almost all environments.

But if port 9081 is assigned to some other service or function in your environment, you must change the communications port setting in the Directory Connector configuration file. To do this (if necessary):

1
Find and open the Directory Connector configuration file, in Coexistence Manager for GroupWise’s \Directory Connector\ folder (named Configuration.xml by default).
IMPORTANT: The Coexistence Manager for GroupWise Management Console must be closed before you open this configuration file. When you select File|Save in the Management Console, the Console saves all of its open data to the Configuration.xml file, and this will overwrite any manual changes to the file that may have been saved while the Console was open.
2
Find the <ServicePort>####</ServicePort> parameter, usually at or near the end of the <DirectoryConnectorSettings> section.
CAUTION: Be very careful when manually entering or editing values in the Configuration.xml file, where incorrect syntax or even a single-character typo could disable a connector or the DC service altogether.
3
Change the value of the <ServicePort>####</ServicePort> parameter to the port number you want to designate as the Coexistence Manager for GroupWise Directory Connector communications port.

The Console asks you to designate a GroupWise Username as the "owner" of all new shared address books that Coexistence Manager for GroupWise will create for Exchange-to-GroupWise connectors. The Username you specify will be identified as the sender of the emails GroupWise will generate to invite other users to share the address books. For connections with GroupWise 2014 (only), note that this account must not be a GroupWise admin account (use any non-admin user for this purpose).

You may want to create a special GroupWise user account in whose name Coexistence Manager for GroupWise’s DC will create any new shared address books that need to be created.

When GroupWise creates a new shared address book, it can take several minutes to generate invitations to all other GroupWise users to share the address book. The time required depends on the size of your Global Address List.

To prevent such delays during your organization’s routine work day, consider manually creating all of the shared address books you will need before you run any of Coexistence Manager for GroupWise’s DC connectors. You could, for example, create your new shared address books after hours some evening, so the invitations would be generated during off hours, and in that way preempt the need for the Directory Connector to create them when the connectors are running.

Note that every Exchange-to-GroupWise connector is defined with a shared address book name, which must be unique. Coexistence Manager for GroupWise will not let you assign a given shared address book to more than one DC connector.

Step 3 (if necessary): Preempt object collisions in environments with multiple source SMTP domains

Many organizations prefer to use alternate or subdomains to enable mail routing between systems during a coexistence period. Coexistence Manager for GroupWise’s Directory Connector automates the required address updates (if configured to do so) by replacing the domain side of the target address in AD and mail address in GroupWise. Mail routing through the resulting contacts will then use the subdomain addresses. This approach isolates incoming mail from internally routed mail.

For environments with a single SMTP domain in the source and no existing users in the target, this approach can be implemented with minimal additional consideration. The subdomain address can be applied with little concern for address collisions.

However, in environments with multiple source SMTP domains, applying a constant subdomain to all users could result in collisions. Address collisions are possible If multiple SMTP domains are used within a single OU (in a GroupWise-to-Exchange connector) or within the GroupWise Global Address Book (Exchange-to-GroupWise connector). These scenarios require additional consideration and configuration to avoid duplicate addresses.

For many organizations the easiest solution is to create multiple connectors (one for each source SMTP domain) with separate subdomains for each, and then define object filters for the different connectors (see Advanced Settings tab: object filtering features later in this chapter). Use the object filters to have each connector pull users only from the specified SMTP domain. This will allow a different subdomain to be used for each source SMTP domain and eliminate any chance of address conflicts between domains.

Step 4 (optional): Configure Coexistence Manager for GroupWise logging

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 most organizations and circumstances, but you can customize logging features if you like. Configuration instructions are nearly identical from one component to another, so we present the instructions separately, in Appendix C of the User Guide.

Step 5: Run the DC Management Console and Connector Creation Wizard to create connector(s)

Use Coexistence Manager for GroupWise’s DC Management Console and its Connector Creation Wizard to define and manage the connectors that will update the directories you want to keep current, and to schedule the connectors to run.

The Connector Creation Wizard is run separately for each DC connector you want to create (or edit), as shown in the diagram below. The Management Console’s DC screens and Connector Creation Wizard are described in the remaining sections of this chapter.

Note that this step alone does not start the Directory Connector service, and that the defined connectors will run only if the Directory Connector service is running. See Running and stopping the Directory Connector service later in this chapter.

Optional, per connector: Configure the <AppendAttributes> parameter

The <AppendAttributes> parameter lets you specify a list of one or more target attributes whose values will be appended to, rather than replaced by, a connector running in Update mode. That is, for each object in the directory, the value of each designated attribute in the source will be added to any existing value in the target.

This parameter is optional, and is configured separately for each DC connector in the connector's section of the DC Configuration.xml file. To designate the attribute(s) that should function this way in Update mode for a particular connector, find (or add) the <AppendAttributes> tags for the connector, and enter the names of the target attributes separated by a pipe character ("|") between the tags, like this:

Three DC connector parameters let you control which attributes a GroupWise-to-Exchange connector will capture and copy for different object types (users vs. groups vs. resources):

This feature can improve connector performance, perhaps dramatically, in an environment with slow response times and long distribution lists. The feature can be configured only by these parameters (not in the Connector Creation Wizard), and are available only for existing connectors in the GroupWise-to-Exchange direction.

If a GwXxxxAttributeList parameter is unspecified, the connector copies all attributes for that object type by default. But if particular attributes (one or more) are unnecessary for a particular object type, these parameters let you specify which attributes to include for a particular connector. (Any attribute not listed for the parameter will be excluded.)

The parameters are set in the Configuration.xml file for the Directory Connector (in Coexistence Manager for GroupWise's DC subfolder), and are set (or not) separately for each defined connector. For each connector, enter the parameter name with a list of all attributes to be included, all in one continuous line and separated by pipe characters ("|"), with no spaces between. For example:

To create a suitable list of attributes for the parameter value:

1
Open the file Directory Connector\attributes\groupwiseConnector_XXX, where XXX is the object type (user or group or resource). The attributes in this file appear listed one attribute per line.
3
For the remaining attributes in the list (the ones you want to include), replace all the hard returns with pipe characters ("|"), to produce a single-line continuous list (no spaces) of attributes separated by pipe characters.

Then you can insert that list as the parameter value in the DC configuration.xml file:

1
Find the section for the connector you want to modify by this parameter, and its <ConnectorSettings> section, and add a new line for the <GwXxxxAttributeList>...</GwXxxxAttributeList> parameter.
Related Documents