Synchronizing IBM Tivoli Directory Server and Microsoft Active Directory LDAP changesAdded by IBM on February 11, 2013 | Version 1 (Original)
|To keep your profiles synchronized with your LDAP directory, use the generic sync_all_dns command. However, if your LDAP directory is IBM® Tivoli® Directory Server or Microsoft® Active Directory, you can use the process_tds_changes or process_ad_changes commands.
About this task
commands do not support synchronizing multiple LDAP directories or multi-branch LDAP directories. If you have populated your profiles database with data from multiple locations, running the process_tds_changes
commands applies changes related to the current LDAP directory only.
To synchronize Tivoli
Directory Server and Microsoft
Active Directory LDAP directory changes with Profiles, perform the following steps.
The process_tds_changes task keeps track of the changelog number in a persistent field. If your LDAP directory is reset, you can do one of the following:
- Update the change log properties in the profiles_tdi.properties file so that the changes to the LDAP directory can be reflected back to the Profiles database. The change log properties are the set of properties that begin with <LDAP_type>_changelog_* .
- Process changes using one of the following options:
Parent topic: Synchronizing source changes such as LDAP with Profiles
Synchronizing source changes such as LDAP with Profiles
Batch files for processing Profiles data
- Delete the changelog number value using the following script:
- AIX or Linux:
chmod +x reset_changelog_state.sh
- Microsoft Windows:
- Set a particular value using the following script and passing it the count value to set: