E-to-N: Target Location Information
The information on this screen identifies data destination(s) in the target server:
|
• |
Target Server: Name of the server. CMN prefills this field with the value you entered for it on the Target Server Information screen. |
|
• |
Target OU: Drop-down list to specify the container in the target directory that should contain the CMN target container—into which this connector will copy objects from the source. (CMN names its target container ou=cmn in a Domino Directory. CMN will create the target container if it doesn't already exist, in the Target OU specified here.) |
|
• |
[ ] Notes Internal Routing Domain (only if you will use subdomains for mail routing): Mark this checkbox and enter the target’s subdomain name (for example, domino.sitraka.com) into the associated text box. This is the subdomain portion of the addresses (after the @ symbol) that will route mail from the target environment back to the source. |
|
• |
Notes Calendar domain (Optional): Enter the name of the target Calendar domain. |
|
• |
Notes Domain (only if you want contact addresses to be formed with @notesdomain appended to the contact SMTP addresses): The name of the target Notes domain (without the @ symbol, which CMN will insert). For example, enter notesdomain if you want the contact address to take the form name@mydomain.com@notesdomain. If this field is left blank, no Notes Domain will be appended to contact SMTP addresses. |
|
NOTE: The values you enter for Notes Calendar domain, Notes Domain and Server Running QCalCon are merged with the AD source data that is pushed into Notes. There are no comparable fields for this data in Active Directory. If you later change the value of any of these fields, it will appear that the source data has changed, although nothing has actually changed in AD. |
|
• |
Server running QCalCon (only when the Free/Busy Connector is also running): Enter the name of the Domino server that hosts the QCalCon server task for CMN’s Free/Busy Connector. The entry here (if any) must be sufficiently qualified that the server can be identified from the computer hosting CMN’s Directory Connector service (e.g., server/domain). |
When these fields are filled with the correct information, click Next to advance to the next screen (or click Back to revisit an earlier screen in the sequence).
E-to-N: Connector Order Management
This screen provides a table of all previously defined connectors, with a checkbox corresponding to each connector in the list. Mark the checkbox for each connector that must complete its run before the current connector will be permitted to start. Then click Next to advance to the next screen (or click Back to revisit an earlier screen in the sequence).
E-to-N: Connector Scheduling
This screen lets you schedule this connector’s runs in much the same way that you define a recurring meeting in Notes or Exchange. You can define more than one recurrence pattern for any single connector, and if you do the scheduled runs will be the sum of all such recurrence patterns defined here. That is, if more than one recurrence pattern appears in the table (bottom half of this screen), the connector will run for all of the scheduled patterns that appear in the table.
To add a recurrence pattern to the table:
|
2 |
If you want to update all objects in every scheduling run, check the Update all objects check box. |
|
3 |
Click the Add button. |
To remove a recurrence pattern from the table:
|
• |
Select it in the table, and click the Delete button. |
To change some element of a previously defined recurrence pattern:
|
• |
Note that it is possible to define a connector without scheduling it for automatic recurring runs. Some admins, for example, like to have one or more unscheduled connectors defined that can be run as-needed, by the Run Connector Now feature in the DC Management Console.
When the table appears as you want it, click Next to advance to the next screen (or click Back to revisit an earlier screen in the sequence).
|
NOTE: Remember that the Connector Creation Wizard doesn’t save connector definitions to disk. Connector definitions are contained within the DC’s Configuration.xml file, so a connector definition is saved only when you save Configuration.xml from the CMN Management Console. You must select File | Save Configuration File from the Console if you want to save any new connectors you have defined, or save any changes you have made to existing connectors. |
Screens for a Notes-to-Exchange ("N-to-E") connector
This series of screens appears in the Connector Creation Wizard when you select the Notes-to-Exchange Direction in the Connector Information screen (first screen in the series, as noted below).