In this sample, data exported from an LDAP or constructed from another means contains data for the Profiles users in your IBM
® Connections deployment. If you have user data in a text file such as in LDIF format, you can use this sample connector in conjunction with sync_all_dns
to synchronize the source data with connections.
Using this process, you’ll do the following:
- Configure TDI to use the iterator connector during operations to synchronize the Profiles database form the source.
- Use TDI mapping and extension attribute processing functions to upload data from the LDIF file to the Profiles database. Based on the source content, you will specify the mapping functions as needed.
A sample connector for use with an LDIF file is supplied as samples/ldifSourceConnectorIterator.xml
The following is sample LDIF file content for a single user:
dn: uid=asingh, cn=users, dc=ibm,dc=com
cn: Allie Singh
ou: Office of the CEO
title: Administrative Assistant to George Bandini
manager: uid=gbandini, cn=users, dc=ibm,dc=com
In this example, using source data from am LDIF text file, the iterator connector is available but the lookup connector is not. TDI assembly lines that work in an iterative manner will read from the LDIF file, however assembly lines that must look up a particular user will not. For example, the collect_dns
utility and the sync_all_dns
utility will work but the populate_from_dn file
utility will not because it also requires a lookup connector.
Use the following procedure:
Parent topic: Using the ProfileConnector
Using the ProfileConnector
- Create or otherwise obtain the LDIF file from your source data repository, for example an LDAP database.
- Move the supplied ldifSourceConnectorIterator.xml connector file from the samples directory to the packages subdirectory.
- Add the following statement to the profiles_tdi.properties file:
- Open the map_dbrepos_from_source.properties file and configure mappings as needed based on the attributes in your source LDIF file. Note the following sample mapping for a single user:
In this example, a guid
field was not present in the LDIF file so the guid
entry in the following sample is mapped to employeeNumber
, which will enable processing. See Mapping fields manually
and Creating an iterator connector
- Uncomment and change the following statement in the profiles_tdi.properties file to enable access to the connector:
- Run a command to process the connector, such as sync_all_dns, to update the corresponding Profiles user data.
Summary output will appear in the console and any errors generated will appear in the log file.