+

Search Tips   |   Advanced Search

Change Detection Connectors

Change Detection Connectors leverage information in the connected system to detect changes, and are either used in Iterator or Server Mode, depending on the Connector. For example, Iterator mode is used for many of the Change Detection Connectors, like those for LDAP, RDBMS, Active Directory and Notes/Domino. They are designed to behave in a common way, as well as provide the same parameter labels for common settings. Change Detection Connectors in Security Directory Integrator are:

The Delta engine feature reports specific changes all the way down to the individual values of attributes. Delta tagging at the AttributeValue level is also available when parsing with either LDIF or DSMLv2 Parsers. The LDIF Parser is used internally by the IBM Security Directory Server Changelog Connector, Sun Directory Change Detection Connector and z/OS LDAP Changelog Connector, therefore these connectors support Delta tagging at AttributeValue level as well. The rest of the change detection connectors are limited to simply reporting if an entire Entry is added, modified or deleted. For more information about the Delta tagging support of a particular component refer to the specific description of that component in the SDI v7.2 Reference Guide.

In some cases, long running AssemblyLines may need to process the same entries more than once. These entries will have a duplicate delta key and will cause the AssemblyLine to throw an exception. If you want to allow duplicate delta keys, we can select the Allow Duplicate Delta Keys check box in the Iterator's Delta tab. This means that duplicate entries can be handled by AssemblyLines having both Iterator Connectors with Delta enabled or Change Detection Connectors and Delta mode Connectors.

Note: It is possible to have, for example, an AssemblyLine with a number of Changelog and Delta mode Connectors. In this case, if the Delta mode Connector is pointing to the same underlying system as the Changelog Connector, the Delta operation could trigger the Changelog again. As there is no way to differentiate between newly-received changes and those triggered by the Delta engine, you should carefully consider your scenario in order not to enter into an endless loop. The delta information computed by the Delta engine is stored in the Work Entry object, and depending on the Change Detection component or feature used can be stored as an Entry-Level, Attribute-Level or Attribute Value-Level operation code.


Parent topic:

Producing Delta Entries