Home

 

Synchronize user data between Profiles and the LDAP directory

To update profiles data, you typically update the LDAP directory first and then synchronize the changes to the Profiles database. However, there are some cases where you might want to allow your users to make their own changes to their profiles, and these changes need to be written from the Profiles database back to the LDAP For example, users in your organization might need to update their cell phone details in Profiles. They cannot change the LDAP directly and, as administrator, you can allow them to make the changes directly in Profiles. These changes then need to be reflected back up to the LDAP using the drafting process.


The draft table stores values that you edit and for which you specify 'draft="true"' on the draftableAttribute element of the profiles-config.xml file. For example:

These editable fields are sent back to the LDAP instead of being updated into the database immediately.

Configure a DSML server service to receive the update requests. Profiles 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, run a script that initializes a server (daemon) process which 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.

To synchronize changes from the Profiles database back to your LDAP directory...

  1. Define values for the DSML server-related properties in the profiles_tdi.properties file. The DSML server-related properties are the properties with names that begin with “monitor_changes_". Typically, the properties that update include the following:

    • monitor_changes_dsml_server_url

    • monitor_changes_dsml_server_username

    • monitor_changes_dsml_server_password

  2. After providing values for the necessary properties, start the synchronization server process by running the following scripts:

    • AIX and Linux

      chmod +x process_draft_updates.sh

      ./process_draft_updates.sh

    • Microsoft Windows

      process_draft_updates.bat

  3. Update the change log properties in the profiles_tdi.properties file so that the changes to the LDAP can be reflected back to the Profiles database. The change log properties are the set of properties that begin with <db_type>_changelog_.


Updating the LDAP directory

 

Related tasks

Map fields manually

Synchronize user identification data between Activities and the LDAP directory

Synchronize user identification data between Communities and the LDAP directory

Change configuration property values

Synchronize IDs between LDAP and the feature databases

Enable Lotus Connections service extensions

 

Related reference


Activities administrative commands


+

Search Tips   |   Advanced Search