The Connections Blog

As you will be aware, Tivoli Directory Integrator (TDI) plays a massive role in any Lotus Connections system.  In combination with a number of custom TDI assembly lines (or scripts) shipped with Lotus Connections, it is responsible for importing users into the Connections Profiles system, populating their data from LDAP or other systems, synchronising changes that occur and even deleting users and their data when they are no longer needed.

It is therefore very important to keep up to date with TDI patches...

This one is new this week:

LO46673 Profiles: Recommended ifix for TDI scripts for LC2.5

Recommended ifix for TDI scripts for LC2.5.

Problem Description:
This ifix fixed the following issues:

1. Unable to use function to map extension attribute from LDAP.

2. sync_all_dns is hard coded to match on the $dn.

3. sync_all_dns.bat is failing when an existing user has his or her first or last name changed in LDAP (Domino 8.5).

4. Sync_all_dns does not update a Profile field if the corresponding LDAP field is empty.

5. A new property named perform_deletion_for_sync is added in the profiles_tdi.properties file to control the delete action when perform sync task.

All these individual fixes are important of course, but for me, no.5 is the answer to many a prayer whilst on customer sites deploying and upgrading Lotus Connections systems.  Here's why - when added to the existing 'perform_deletion_for_sync' option, the new 'perform_deletion_for_sync' parameter has these possible values:>sync_updates_show_summary_only=false
perform_deletion_for_sync=true
will perform the deletion.

sync_updates_show_summary_only=false
perform_deletion_for_sync=false
will not perform the deletion.

sync_updates_show_summary_only=true
perform_deletion_for_sync=true
will not perform deletion.

sync_updates_show_summary_only=true
perform_deletion_for_sync=false
will not perform deletion.i.e. the Connections administrator now has much more control over what happens when a sync_all_dns update is run and a user has been removed from LDAP.

You might be able to tell that I'm really really pleased about this addition...  I advocate leaving users in Profiles after they have left the organisation in order to retain some data about them (usually via a 'leaver' profile type) and so this helps a great deal.

[ Thanks to Mitch Cohen for pointing this one out. ]