As an IBM Connections System administrator, you can load the profile attributes from LDAP Server, files (such as a CSV file), relational database, and other systems such as human resource system. Profile customization throughTDI include:
- Mapping profile attribute to a custom attribute at LDAP
- Adding extended fields
- Customizing user login attribute
- Customizing search
The most common source of user data is the LDAP directory, to load data from the enterprise LDAP directory to Profiles database, you can use IBM Tivoli Directory Integrator (TDI) and IBM Connections TDI Solutions Package.
IBM Tivoli Directory Integrator
Tivoli Directory Integrator provides the functionality to join different software components an integrated software solution. TDI features includes:
- It is an integration tool that can easily move, copy, and transform data between applications and systems.
- It has a set of connectors that connect to different types of systems and protocols, such as LDAP, JDBC, JMS, SMTP, HTTP (client), JMX, JNDI, IBM MQ, Notes, and so on.
- It has an integrated and agile development tool IDE. Based on the power of Eclipse Platform, the TDI development environment is both comprehensive and extensible.
TDI solutions package
The IBM Connections 4 comes with a set of ready-to-use TDI solution files that can allow IBM Connections System Administrator to easily load their Profiles data with user entries. The TDI Solution Package is located in the /TDISOL
subdirectory. In our environment, the location is /opt/IBM/LotusConnections/TDISOL
This directory contains two archive files, tdisol.tar
, for Linux and Windows, respectively. TDI deployment is simple and straight forward. You just extract the files to a local directory on a server from which you plan to run the Profiles load and synchronization scripts and configure certain files. It is not required to run TDI on the same server as IBM Connections. You can place TDI on the database server to reduce network latency or on its on server.
Profiles TDI solution directory
The following are the subdirectory under the TDI solution directory:
- conf: Used to configure Profiles extensions properties
- etc: Contains log4j.properties where logging can be enabled
- lib: Database driver and profiles backend library files
- logs: Task log files (except for Wizard)
- packages: Used to develop TDI connectors
- samples: Additional optional sample files
- TDISysStore: Local Derby database for TDI specific storage
The files for maintaining the Profiles include:
- profiles_tdi.properties: This file contains the property values relevant to your configuration. See the IBM Connections 4 Wiki for a full explanation of all parameters.
- profiles_tdi.xml: This the TDI solution file that contains all TDI "assembly lines".
- map_dbrepos_from_source.propertie: Defines mappings from the enterprise directory (or input sources) to the Profiles database. The mapping can consist of:
- LDAP Attribute: Specifies the LDAP attribute to assign to the database field
- collect.dn: Contains the distinguished names from the LDAP directory.
- tdi-profiles-config.xml:Defines mapping for custom extension attributes to fields in your source LDAP directory
- t.bat or *.sh: Scripts to run Profiles TDI tasks
How user data is load to Profiles database
The following figure show how TDI works. Aafter loading source data for each user, TDI engine updates Profiles database (PEOPLEDB) using the Profiles Connector. The following is the execution flow of load user data to the Profiles in IBM Connections:
- Based on values in profiles_tdi.properties, TDI searches LDAP and creates a file (default: collect.dns) of users to be imported.
- Based on map_dbrepos_from_source.properties and collect.dns, TDI loads data for each user into PEOPLEDB, using the Profiles Connector, available in TDI Solution.
- If extension attributes are specified in tdi-profiles-config.xml, these are also loaded during step 2.