Chat now with support
Chat with Support

Coexistence Manager for Notes 3.8.2 - User Guide

About the CMN Documentation Suite Introduction CMN Directory Connector
Directory Connector overview Installation and configuration DC Management Console Connector Creation Wizard Connector Advanced Settings Starting and stopping the Directory Connector service
CMN Mail Connector
Mail Connector features overview Coexistence mail routing basics Deployment of CMN Mail Connector Installation Configuration Mail Connector Management Console
CMN Free/Busy Connector The Log Viewer Appendix A: Known limitations Appendix B: Troubleshooting Appendix C: CMN Logs

Step 9 (optional): Configure CMN logging

CMN is installed with the log4net utility to generate log files of CMN components’ system activity. This information is critical to diagnosing any configuration issues that may arise. Logging is enabled by default for all CMN components.

The default configurations will be suitable for most organizations and circumstances, but you can customize logging features. The log4net utility may be configured to work a particular way with each CMN component. Configuration instructions are nearly identical for all components, so we present the instructions separately, in User Guide Appendix C.

To synchronize dynamic distribution lists

CMN’s Directory Connector lets you synchronize dynamic distribution lists between the source and target directories. This feature is enabled (or not) and configured independently per connector.

The following xml attributes can be used to overwrite the default values for the source or target object type used during synchronization:



To use one of the values listed above to change the default source or target object type:

Edit the Configuration.xml file located in the Directory Connector directory.
Find the configuration (<ConnectorSetting>) section for the connector you intend to modify and add a line for the desired xml attribute as shown in the example below. The new line is shown here in red italicized type. In this example, the SourceGroupObject is used to modify the default value Groups to the value msExchDynamicDistribList:

DC Management Console

The CMN Directory Connector (DC) includes a configuration tool, called the Management Console, that directs the Directory Connector’s features and functions according to entries in the Console application: source and target directories, access credentials, update scope, scheduled runs, and so forth. One of the Console’s screens also lets you launch a Connector Creation Wizard— a separate application to create or modify the configuration details for individual DC connectors that will copy directory data from one environment to the other.

The configuration data for both the DC service as a whole and its individually defined connectors is saved in a configuration file named Configuration.xml (by default), in CMN’s \Directory Connector\ folder. The DC configuration file may be opened, modified and saved as needed, by any XML editor, but CMN’s Management Console provides a "friendlier" interface for managing configuration settings. The Console also makes DC configuration safer, since a single typo in the xml file (when hand-editing) can cause unintended consequences or even disable a connector altogether.

Note that the DC configuration file controls only the Directory Connector, not CMN’s Mail Connector or Free/Busy Connector—which are controlled by their own, separate configuration files.

The relationships among the CMN Directory Connector Management Console, its Connector Creation Wizard, and the Configuration.xml file are illustrated in the diagram above and in this chart:

Chapter 1 of the User Guide explains the basic operating concepts for the CMN Management Console. This DC chapter provides the field notes for the Console screens that pertain to DC configuration, and for the Connector Creation Wizard.

DC Management Console screens

The Management Console contains this screen for the Directory Connector:

Directory Connector | Connector Settings: Create, change or delete a connector definition, or run it immediately (rather than waiting for its next scheduled execution).
Related Documents