Synchronize changes users have made to their profiles

Overview

To update profiles data, we typically ...

1. Update the LDAP directory
2. Synchronize changes to Profiles database

To synchronize changes users have made to their profiles, we write from the Profiles database back to the LDAP directory.

Configure IBM HTTP Server before attempting to synchronize data between the Profiles database, and the LDAP server.

Changes made by users to the Profiles database are reflected back to the LDAP directory using the drafting process. Draft table values are specified using the draftableAttribute element in profiles-config.xml...

<profileDataModel>
   <draftableAttribute>telephoneNumber</draftableAttribute>
   <draftableAttribute>displayName</draftableAttribute> 
   <draftableExtensionAttribute extensionIdRef="tieline"/>   
</profileDataModel>

The Profiles database is updated immediately with the specified values.

Configure a Directory Services Markup Language (DSML) server service to receive the update requests. The Profiles application does not provide this service because each implementation of an LDAP server is unique.

To synchronize changes between the draft table and the LDAP server, we must run a script that initializes a daemon process that monitors the Profiles database for updates and, when one is made, formats the update as a DSML request and transmits it to a configured DSML server.

Synchronize changes users have made to their profiles

1. Define values for the DSML server-related properties in profiles_tdi.properties.
   • monitor_changes_dsml_server_url
   • monitor_changes_dsml_server_username
   • monitor_changes_dsml_server_password

2. Start the synchronization server process...
   ./process_draft_updates.sh

   This script tracks the database change record number in a persistent field.

Your task cannot run successfully in the following situations:

• You recreate the Profiles database after already running the TDI Solution at least once.
• You clear the content of the CHG_EMP_DRAFT and EMP_DRAFT tables manually.

In such situations, reset the persistent field, and run the script again...

1. Delete the database change record number value:
   ./reset_draft_iterator_state.sh

2. Set a particular value and pass it the count value to set:
   ./set_draft_iterator_count.sh

Parent topic:
Sync LDAP with Profiles

Related:
Configure IBM HTTP Server
Map fields manually
Populate peopledb
Change Profiles configuration property values
Use the Profiles database as the user directory
Activities administrative commands