Manage user data using Tivoli Directory Integrator scripts
There are a number of scenarios in which you might want to synchronize changes between the Profiles database and the LDAP directory, using IBM Tivoli Directory Integrator.When you want to update user information in the Profiles database, the model typically used is to update the information in the LDAP directory and then synchronize the changes back to the Profiles database. For example, if your organization has taken over a new division, you can add new employees to Profiles by importing their details into the LDAP directory and then synchronizing the changes to the Profiles database. One way to keep your profiles data synchronized with changes to the LDAP directory is to use the sync_all_dns task. For more information, see Synchronize LDAP directory changes with Profiles.
However, there might be instances in which your organization wants to allow users to update their information directly in the Profiles database. For example, if users want to update their personal cell phone details, as administrator, you might allow them to make the changes in Profiles themselves. These changes must be synchronized back to the LDAP directory from Profiles. To start the synchronization process, you need to define values for the DSML server-related properties in the profiles_tdi.properties file and then run the appropriate process_draft_updates script. For more information, see Synchronize user data between Profiles and LDAP.
Although it is not expected to be a frequent occurrence, there might also be instances in which you want to change your LDAP directory. In this scenario, you can run scripts that are provided with IBM Connections to synchronize the user information used in Profiles with the user information stored in your new LDAP directory. For more information, see Update Profiles when changing LDAP directory.
Synchronize LDAP directory changes with Profiles
As administrator, you need to synchronize changes from your LDAP directory to the Profiles database to ensure that your organizational information is kept up-to-date. Use the sync_all_dns task to keep your profiles data synchronized with changes to the LDAP directory.Update Profiles when changing LDAP directory
When you need to change your LDAP directory, synchronize the user data stored in profiles with the information in your new LDAP directory. You can run commands that synchronize the information in the Profiles database with the user information stored in your new LDAP deployment.Delete or inactivating users in the Profiles database
You can use an IBM Tivoli Directory Integrator assembly line command to delete or inactivate users in the Profiles database.Customize the logic used for the delete operation
You can customize the delete logic to use when deleting users from the Profiles database by defining a custom assembly line that contains the logic.
Parent topic
Manage users when the Profiles application is installedRelated concepts
Developing custom Tivoli Directory Integrator assembly lines for Profiles
Developing custom Tivoli Directory Integrator assembly lines for Profiles
Add supplemental content to Profiles
Related tasks
Troubleshooting problems with Tivoli Directory IntegratorRelated reference
Tivoli Directory Integrator commands
});