UnitySync - Discovery and Sync

Created: 2012-04-20 08:09:59
Modified: 2017-05-24 10:00:28
Tags: Features UnitySync

By default, communication with the Source and Destination directory is performed over the standard LDAP port 389. Communication with both the Source and Destination is configured on the Source/Destination tabs and requires IP, Port, LoginID, and Password information. You may enable SSL and use 636 and/or for a Global Catalog (GC) Source, you may use the GC ports to pull an entire domain (3268/3269).

Note: While you may utilize the GC port to pull from the Source, you may not write to the GC port. Please use only DC ports on your Destination tab.

When a connection runs, there are two primary and one optional phase: Discovery, Simulation, and Synchronization.

The Discovery phase performs an LDAP query of the Source directory, reading all objects from the Source directory per the Source tab configuration. The Source tab configuration may include a specific Source Context, Object Types, and/or Optional LDAP Query Filters to narrow the search query. Additionally, you may Exclude objects to narrow the search via a Custom tab button. If the Discovery phase ends successfully, an ldif.txt file is generated as output.

Simulation is a phase that is useful for testing out configuration changes. This phase reads the ldif.txt and any internal database files to determine what might happen when you next Sync the connection. There are a few caveats as to what information Simulation can provide. This phase is also useful for setting a tolerance of changes to prevent mass modifications or deletes on your Destination if they are not intended. Please contact our Technical Support Team to discuss how Simulation can be used to failsafe your automated connections and test configuration changes.

The Sync phase reads the ldif.txt and writes to the Destination directory per the Destination tab configuration, creating new objects, modifying existing objects, and/or deleting objects. The Destination tab configuration defines the exact Sync Container determined by Structure Name (new OU created) and/or Placement DN (existing OU). By default, no additional structure is created; all synced objects are created in one flat container. You can, however, define creation of sub-ou’s utilizing the Levels feature. By default, the Sync does not read the Destination at Sync time. The default Synce/Join Mode of Create simply creates new objects and maintains them on the Destination in the Sync Container.

The phases selected will run when you click the Batch Run button (General tab) or when you run a batch script as part of automation. We recommend that you leave Discovery and Synchronization checked, as a rule. Simulation may also be checked if you are utilizing Simulation Tolerance functionality.

Discovery, Simulation, and Synchronization all produce individual log files. By default, these Log Files are set to a level of 2-Default. This limits the information logged but also limits the size of the file. For troubleshooting, our Technical Support team will often request you change the Log File level on the General tab.

As mentioned above, your ongoing sync process may be automated using command line execution options and scripting. Please contact our Technical Support Team with any questions or comments.

Share this article:

  1. Directify - Self Service

  2. Mimic - Replication

  3. UnitySync - Sync
  1. emPass - Sync
  1. Profiler
  2. SimpleSync