Introduction to IBM Tivoli Directory Integrator
IBM Connections uses IBM Tivoli Directory Integrator to transform, move, and synchronize data from the LDAP directories to the Profiles database.
AssemblyLines
An AssemblyLine processes data such as entries, records, items, and objects from an LDAP directory, transforms it, and outputs it to the Profiles database. When you import data from multiple LDAP directories, the AssemblyLine processes, transforms, and combines all the source data before outputting it.
Databases usually store information in records with a fixed number of fields. Directories usually work with variable objects called entries, and other systems use messages or key-value pairs.
Connectors
Connectors are used to build AssemblyLines. Each type of connector uses a specific protocol or API to handle the details of data source access. We can create our own connectors.
work Entries
TDI collects and stores information in a Java data container called a work Entry. The data values are kept in objects called Attributes the work Entry holds and manages. AssemblyLine components process the information in the work Entry by joining in additional data, verifying content, computing new attributes and values, as well as changing existing ones, until the data is ready for delivery to the Profiles database.
TDI internal attribute mapping, business rules, and transformation logic do not need to deal with type conflicts.
Attribute mapping
Attribute Maps are your instructions on which attributes are brought into the AssemblyLine during input, or included in output operations. An AssemblyLine is designed and optimized for working with one item at a time, such as one data record, one directory entry or one registry key. To perform multiple updates or multiple deletes, write AssemblyLine scripts.
Parent topic:
Configure Tivoli Directory Integrator
Related: