Sync flow examples
PingDataSync processes changes by fetching the most up-to-date, full entries from both sides and then comparing them. This process flow is called standard synchronization mode.
The processing flow differs depending on the type of PingDataSync change (ADD, MODIFY, DELETE,
MODDN) that is requested. The following examples show the control flow diagrams for the sync operations, especially for those cases when a MODIFY or a DELETE operation is dropped. The sync log records all completed and failed operations.
Modify operation example
About this task
Steps
-
Detect change from the change log table on the source.
-
Fetch the entry or table rows from affected tables on the source.
-
Perform any mappings and compute the equivalent destination entry by constructing an equivalent LDAP entry or equivalent table row.
-
Fetch the entry or table rows from affected tables on the destination.
-
Diff the computed destination entry and actual destination entry.
-
Apply the changes to the destination.
Add operation example
About this task
Steps
-
Detect change from the change log table on the source.
-
Fetch the entry or table rows from affected tables on the source.
-
Perform any mappings and compute the equivalent destination entry by constructing an equivalent LDAP entry or equivalent table row.
-
Fetch the entry or table rows from affected tables on the destination.
-
The entry or table row does not exist on the destination.
-
Create the entry or table row.
Delete operation example
About this task
Steps
-
Detect delete from the change log table on the source.
-
Fetch the entry or table rows from affected tables on the source.
-
Perform any mappings and compute the equivalent destination entry by constructing an equivalent LDAP entry or equivalent table row.
-
Fetch the entry or table rows from affected tables on the destination.
-
The entry or table row exists on the destination.
-
Apply the delete on the destination.
Delete after source entry is re-added
About this task
Steps
-
Detect delete from the change log table on the source.
-
Fetch the entry or table rows from affected tables on the source.
-
The entry or table row exists on the source.
-
Delete request is dropped.
Standard modify after source entry is deleted
About this task
Steps
-
Detect change from the change log table on the source.
-
Fetch the entry or table rows from affected tables on the source.
-
The entry does not exist.
-
Change request is dropped because the source entry no longer exists.
Notification add, modify, modifyDN, and delete
About this task
Steps
-
Detect change from the change log table on the source.
-
Perform any mappings and compute the equivalent destination entry by constructing an equivalent LDAP entry or equivalent table row.
-
Reconstruct changed entries.
-
Push notification with change details to the destination.