IBM Security Directory Server Changelog Connector

Existing configuration that use the IBM Security Directory Server EventHandler can be migrated to use the IBM® Security Verify Directory Integrator Changelog Connector using the information provided here.

1. Set the following Connector parameters to the values of the EventHandler parameters with the same names: ldapUrl, ldapUsername, ldapPassword, ldapAuthenticationMethod, ldapUseSSL, ldapSearchBase.
2. Leave the jndiExtraProviderParams Connector parameter empty.
3. Set the iteratorStateKey Connector parameter to some unique identifier, one that has no corresponding state saved in the System Store.
4. Set the nsChangenumber Connector parameter to the next change number that the EventHandler would process. The last change number that the EventHandler has processed is normally stored in an external properties file, referenced by its ldapChangeNumberFileName parameter.
5. Set the stateKeyPersistence Connector parameter to "After read" (the EventHandler writes the last received change number to its file backend after it reads a changelog entry and before it dispatches it for processing).
6. Set the mergeMode Connector parameter to "Merge changelog and changed data". This will ensure that the changelog attributes (changenumber, targetdn, ...) appear as attributes of the Entry.
7. Set the useNotifications Connector parameter to true.
8. Set the batchRetrieval Connector parameter to false.

Note: As opposed to the EventHandler, the Connector does not let you select a part of the directory tree, for whose notifications it will listen - it subscribes for changes in the whole directory tree (the Connector does not have equivalents of the

ldapEventBase and

ldapSearchScope EventHandler parameters). If this is critical for you, you can implement some custom filtering in your solution to overcome this limitation of the Connector.