In this example, we show how to get the data from the custom database and put it into the IBM Connections Profiles database that already was initially populated with the data from the LDAP server during the IBM Connections pre-installation steps.
In this example, we have two source systems with user profile information:
- Domino LDAP server with contact information.
- A custom table in a DB2 database with extended information about employees' background, their alternate emails and IP telephony numbers.
We use the employee's primary e-mail address as the unique user ID for identifying the same user in both systems.
We also assume that IBM Connections and Tivoli Directory Integrator are already installed and configured. The Profiles database has been populated as part of the Profiles installation so we skip the step of the initial population of the Profiles database with data from Domino LDAP. This procedure is described in the following documentation chapters:
In addition, IBM Connections has a number of pre-developed assembly lines for Tivoli Directory Integrator, which allows administrator to manage the profile data and perform user data synchronization tasks between the Profiles database and the LDAP server. Here is a link to the article with details: http://www-10.lotus.com/ldd/lcwiki.nsf/dx/Tivoli_Directory_Integrator_commands_ic301
In our scenario, we create two custom assembly lines. The first one imports new information from table in DB2 to Profiles database and the second one synchronizes updates between databases.
Continue with section 4.4 Setting up the development environment
Parent topic: 4.0 Tivoli Directory Integrator