Home
Synchronize IBM Tivoli Directory Server and Microsoft Active Directory LDAP changes
To keep your profiles synchronized with your LDAP directory, it is recommended that you use the generic sync_all_dns command. However, if your LDAP is IBM Tivoli Directory Server or Microsoft Active Directory, you can use the process_tds_changes or process_ad_changes commands.
The process_tds_changes and process_ad_changes 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 and process_ad_changes commands will apply changes related to the current LDAP only. To synchronize Tivoli Directory Server and Microsoft Active Directory LDAP changes with Profiles, perform the following steps:
- Do one of the following:
- For Tivoli Directory Server, use the following script to process changes made to LDAP and have those changes made to the corresponding records in your database repository:
- AIX and Linux
chmod +x process_tds_changes.sh
./process_tds_changes.sh
- Microsoft Windows
process_tds_changes.bat
- For Microsoft Active Directory, use the following script to process changes made after the initial population:
- AIX and Linux:
chmod +x process_ad_changes.sh
./process_ad_changes.sh
- Microsoft Windows:
process_ad_changes.bat
- The process_tds_changes task keeps track of the changelog number in a persistent field. If your LDAP is reset, you can do one of the following:
- Delete the changelog number value using the following script:
- AIX and Linux:
chmod +x reset_changelog_state.sh
./reset_changelog_state.sh
- Microsoft Windows:
reset_changelog_state.bat
- Set a particular value using the following script and passing it the count value to set:
- AIX and Linux:
chmod +x set_changelog_count.sh
./set_changelog_count.sh
- Microsoft Windows:
set_changelog_count.bat
Synchronize LDAP changes with Profiles