The Delta mode provides incremental modifications to the connected system, based on delta operation codes.
Delta operation codes are set by either the Iterator Delta engine feature (Delta tab for Iterators), or Change Detection Connectors like the IBM Directory Server (IDS), LDAP, or Active Directory (AD) Connectors, or the ones for RDBMS and Lotus/Domino Changes; or by parsing this delta information with the Lightweight Directory Interchange Format (LDIF) or Directory Services Markup Language (DSML) Parsers.
In versions earlier than IBM Tivoli Directory Integrator V6.1, snapshots written to the Delta Store, a feature of the System Store, during Delta engine processing were committed immediately. As a result, the Delta engine would consider a changed entry as handled even though processing the AssemblyLine Flow section failed. This limitation is addressed through the Commit parameter on the Connector Delta tab. The setting of this parameter controls when the Delta engine commits snapshots taken of incoming data to the System Store.
Delta mode is only available for LDAP and JDBC Connectors.
A Connector in Delta mode must be paired with another Connector that provides Delta information, otherwise the Delta mode has no delta operation codes to work with.
The Delta features in Tivoli Directory Integrator (see Deltas) are designed to facilitate synchronization solutions. We can look at the Delta capabilities of the system as divided into two sections:
Parent topic: Connector modes