1. Using TDI with IBM ConnectionsMorten Christensen, IBM Collaboration SolutionsTwitter: @mortench 2010 IBM Corporation

2. Tivoli Directory IntegratorTDI takes inputdata...Input DataPerforms logicon the data toprocess it usingJavaScript....Brings in other Tivolidata sources to Directoryaid in theIntegratorprocessing...Processing Logic Other InputsOutputs finaldataCan connect toa large numberof input andoutput datasources Output Data2010 IBM Corporation2 3. Software Requirements The Connections connectors work with TDI 7.0 Fix Pack 5 makes it easy to install them in TDI 7.0 the solutions directoryTo find current fixpack level: /bin/applyUpdates -queryreg +Use the TDI updater to install fix pack: Fix Pack 5 /bin/applyUpdates -update 2010 IBM Corporation3 4. Profiles update philosophyIBM Connections does NOT document the schema due to the fact that as new enhancements areadded, the schema changes; tables may be updated, renamed, deleted, etc. For this reason,updating Connections tables directly is NOT SUPPORTED or recommended. You should alwaysuse existing assemblyLines such as SyncDBFromSource, new 3.0 Connectors, or the ServiceProvider Interface2010 IBM Corporation 4 5. Applying TDI to the Problem.... LDAPProfiles DB 212 Read user detailsMatch against from LDAP Processing Logic Profiles DB to getunique User ID Update Profiles database3If the UID can be retrieved fromthe LDAP then step 2 isntrequired! Profiles DB 2010 IBM Corporation 5 6. Directory Structure It is important to use the correct directory structure so the Assembly Line can see all the Java classes and configuration required.TDISOLExpanded tdisol.zip/tar fileworkspace Where we put our Assembly Lines2010 IBM Corporation 6 7. Starting TDI When TDI is started we need to tell it about the Profiles Solution directory we created. This is done using the -s argument /ibmditk -s //TDISOL/TDI When asked to choose the workspace, select the workspace created in the previous slide. The components we create in the Assembly Lines will now be able to see the Jars contained in the Profiles Solution directory2010 IBM Corporation 7 8. Identifying User in ProfilesUsers on the Profiles database are identified by a UID.When user details are retrieved from the Domino database this information is available....However, data may be retrieved from a source that uses another attribute to identify users, oneexample being an email address.This can be handled using the ProfileConnector component....2010 IBM Corporation 8 9. Demo Populate additional data from DB2Additional data from DB2 table needs to be populated into ProfilesTwo assembly lines will be created and made ready for command line invocationPopulateProfilesDBProcessChangesTwo main components will be exploredProfilesConnectorJDBCConnector 2010 IBM Corporation9