CMN's Connector Creation Wizard is designed to scan the source and target OUs to generate lists of valid options for the source and target OUs. Ordinarily, the Wizard requires source and target OUs be selected for a connector definition based on the results of these scans. However, in the rare event the Wizard encountered a corrupt OU structure, it may be impossible to select an OU and complete the Connector configuration.
Corrupt OU structure.
A CMN configuration parameter provides an option to bypass these OU scans and disregard the OU verifications. With this option configured, the Wizard can advance to the next screen whether or not the OU selection can be confirmed—so you can continue the connector definition.
To enable this feature (to disable the verifications), set this boolean parameter setting in CMN's Configuration.xml file from false to true:
Note: CMN automatically adds this new parameter to Configuration.xml when installing the Directory Connector. The parameter is set to false by default (which leaves the Wizard's verifications intact). To enable this feature, change the value to true. Quest recommends maintaining the false setting for this feature unless the Wizard encounters a corrupt OU structure.
Then, use the Custom Configurations tab of the connector’s Advanced Settings to configure the Directory Connector for the OU(s) you want to appear in CMN’s selectable list. You can define separate lists of available OU(s) for the Notes environment as the source and as the target.
The table in the Custom Configurations tab shows parameter names (the Key column) and their corresponding Values, as they now occur in the connector’s config.txt file. You can change the value of an existing parameter, or add a new one. Click Add to add a new parameter. A dialog box opens with two fields: Key and Value.
For Notes as the source, define a parameter and its value:
* Key: sourcecontext
* Value: [the desired OU(s) – e.g., "ou=org1,o=contoso"]
For the source parameter (only), you can enter a Value with multiple containers by using vertical bars (|) to separate the containers.
Then define another parameter and its value for Notes as the target:
* Key: destsubtree
* Value: [the destination OU for synched data – e.g. "o=contoso"]