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 5 (conditional): Change communications port

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 CMN’s \Directory Connector\ folder (named Configuration.xml by default).
IMPORTANT: The CMN 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 CMN Directory Connector communications port.

Step 6 (conditional): 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. In environments with multiple source SMTP domains, applying a constant subdomain to all users could result in collisions. The Directory Connector uses organizational units as the selection criteria for each connector’s operation. Multiple SMTP domains within a single OU create a possibility of address collisions during the operation. In this case, additional configuration may be required 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 7 (recommended): Configure LDAP to write to a secondary address book

The Directory Connector can write to a secondary address book, if you use Notes Directory Assistance (DA) to direct LDAP writes to a selected address book. Many organizations prefer this approach to isolate the updates and eliminate direct updates to the production NAB. To configure Notes for this:

NOTE: Newer versions of Domino have renamed the File | Database | ... menu path to File | Application | .... If you are running one of these newer Domino versions, just substitute "File | Application | .. " for "File | Database | ..." wherever that menu path appears in this procedure.
a
Open the database pubnames.ntf (File | Database | Open) by selecting the server, then manually typing in the filename. (If the database does not already exist, create it: File | Database | New.)
b
Edit the database's ACL: File | Database | Access Control.
a
Create the new database: File | Database | New.
b
Select the server in the Database Name section.
d
In Advanced Templates, check Show All Templates.
e
Select the server in the Template section.
f
Select Domino Directory as the template, and click OK.
g
Assign a unique domain name (e.g. secondAB), then Save & Close.
Note: This domain name will be used in step 6b below.
a
Edit the database's ACL: File | Database | Access Control.
a
In Domino Administrator, on the Configuration tab: In the navigation tree at left, expand Directory, then expand LDAP, and then select Settings.
c
In the LDAP Settings: Set Allow LDAP users write access to Yes.
d
Save & Close the document.
b
Select the server in the Database Name section.
d
Select the server in the Template section.
e
Check Advanced Templates to show all templates.
f
Select Directory Assistance as your template.
g
Click OK and leave the new Directory Assistance database open.
b
In the Basics tab, enter the domain of the address book you want to add.
Note: The primary address book domain name must match the domain name of the address book, and the domain name of the secondary address book must match the domain name specified in step 2g (e.g., secondAB).
c
Under the Naming Rules tab, enter a unique Organization Name for this address book, and leave all other fields for that line as "*" (e.g., secondary).
Note: The Organization Name will appear in the Name Rules for the secondary address book and will be used in step 9 below to create a CMN Directory Connector connection.
e
Switch back to the Add Directory Assistance dialog box, and select the Replicas tab.
f
Drag and drop the top tab (marking the address book you want to link to this Directory Assistance rule) into the field marked Database Links. This should produce a blue book in the field. Then Save & Close the rule.

Repeat steps 1–6 to create a unique Directory Assistance document for each address book, including the primary address book.

When you have completed steps 1–6 for all address books, you should see one document for each address book in the new Directory Assistance Database (newDAdb). This includes the primary address book. For example:

primaryDomain

Notes

companyA

*/*/*/*/<primary>/*

secondary AB

Notes

companyX

*/*/*/*/<secondary>/*

... where <primary> and <secondary> are variables that should be filled with the actual primary and secondary organization names, respectively.

1
In Domino Administrator, on the People & Groups tab: Select the secondary address book from the navigation tree at left, and click Certificates.
2
Select Notes Certifiers (in the pane at right), and click Add Certifier.
3
Add two Certifier entries of O=xxxxxxxx (or OU=xxxxxxxx if configured at a higher level), where xxxxxxxx is the string you added to the secondary address book configuration (in place of the <secondary> variable in the routing table, as shown above).
4
Click Save & Close.

When you have completed steps 1–6 for all address books, continue this procedure with step 7:

b
In the Servers part of the tree, open the document for your server.
c
Under the Directory Information, enter the name of the Directory Assistance Database file from step 5c (newDAdb.nsf).
d
Save & Close the primary address book.

Step 8 (if necessary): Verify Exchange DL configuration

Check the Message Delivery Restrictions settings for any Exchange group to which you want Notes users to be able to send messages. Any such Exchange group must be of the universal distribution type to be mail-enabled. To change the settings, beginning in the Exchange Management Console:

1
Select the group under Recipient Configuration | Distribution Group, then double-click the group you want to edit.
2
Click the Mail Flow Settings tab, and highlight Message Delivery Restrictions, then click Properties above.
3
De-select (unmark) the check box for Require that all senders are authenticated.
4
Save, and then restart the MS Exchange transport service.
Related Documents