4.2 Accessing IBM Connections from a custom Tivoli Directory Integrator assembly lineAdded by Amanda J Bauman on November 21, 2011 | Version 1 (Original)
There are a number of Tivoli Directory Integrator Connectors available for different types of systems and protocols, such as: LDAP, JDBC, JMS, SMTP, HTTP (client), JMX, JNDI, IBM MQ, Notes, and so on. You can find all of them in the following chapters of the Tivoli Directory Integrator 7.0 documentation: http://publib.boulder.ibm.com/infocenter/tivihelp/v2r1/topic/com.ibm.IBMDI.doc_7.0/referenceguide10.htm?path=7_9_0_5_5_0#availability
In addition, IBM Connections contains four more connectors to manipulate data in Profiles database:
- ProfileConnector for retrieving, creating, updating, and resetting profile entries in the Employee, Profile Extension, and various ancillary employee tables in the Profiles database.
- PhotoConnector for retrieving, creating, updating, and deleting photo entries in the Photo table in the Profiles database.
- PronunciationConnector for retrieving, creating, updating, and deleting pronunciation entries in the Pronunciation table in the Profiles database.
- CodesConnector for retrieving, creating, updating, and deleting code entries, such as Department codes, Work location codes, and so on, in the various look-aside tables in the Profiles database.
These four connectors are the only supported options for managing data in Profiles database. Using other connectors, such as JDBC, and manipulating data directly inside the tables of Profiles database is not supported.
With this large variety of out of the box Tivoli Directory Integrator Connectors, it is possible to bring data from various type of sources into IBM Connections Profiles. For example, Tivoli Directory Integrator can get various parts of user's profile information from different systems such as: LDAP repository, HR databases, custom Domino database. In addition, Tivoli Directory Integrator can keep the data from all these systems synchronized with the IBM Connections Profiles database.
Continue with section 4.3 Scenario description
Parent topic: 4.0 Tivoli Directory Integrator