DanNotes: Using TDI with IBM Connections

3,956 views

Published on

Presentation given at DanNotes May 02 2012

Published in: Technology
1 Comment
0 Likes
Statistics
Notes
  • Be the first to like this

No Downloads
Views
Total views
3,956
On SlideShare
0
From Embeds
0
Number of Embeds
384
Actions
Shares
0
Downloads
53
Comments
1
Likes
0
Embeds 0
No embeds

No notes for slide

DanNotes: Using TDI with IBM Connections

  1. 1. Using TDI with IBM ConnectionsMorten Christensen, IBM Collaboration SolutionsTwitter: @mortench ©2010 IBM Corporation
  2. 2. Tivoli Directory Integrator TDI takes input data... Input Data Performs logic on the data to process it using JavaScript.... Brings in other Tivoli data sources to Directory aid in the Integrator processing... Processing Logic Other Inputs Outputs final data Can connect to a large number of input and output data sources Output Data ©2010 IBM Corporation 2
  3. 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 directory To find current fixpack level: <tdiHome>/bin/applyUpdates -queryreg + Use the TDI updater to install fix pack: Fix Pack 5 <tdiHome>/bin/applyUpdates -update <fix_pack.zip> ©2010 IBM Corporation 3
  4. 4. Profiles update philosophyIBM Connections does NOT document the schema due to the fact that as new enhancements are added, the schema changes; tables may be updated, renamed, deleted, etc. For this reason, updating Connections tables directly is NOT SUPPORTED or recommended. You should always use existing assemblyLines such as SyncDBFromSource, new 3.0 Connectors, or the Service Provider Interface ©2010 IBM Corporation 4
  5. 5. Applying TDI to the Problem.... LDAP Profiles DB 2 1 2 Read user details Match against from LDAP Processing Logic Profiles DB to get unique User ID Update Profiles database 3If the UID can be retrieved fromthe LDAP then step 2 isntrequired! Profiles DB ©2010 IBM Corporation 5
  6. 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. <work_root> <version> TDISOL Expanded tdisol.zip/tar file workspace Where we put our Assembly Lines ©2010 IBM Corporation 6
  7. 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 <tdi_location>/ibmditk -s <container>/<version>/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 directory ©2010 IBM Corporation 7
  8. 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, one example being an email address.This can be handled using the ProfileConnector component.... ©2010 IBM Corporation 8
  9. 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 invocation PopulateProfilesDB ProcessChangesTwo main components will be explored ProfilesConnector JDBCConnector ©2010 IBM Corporation 9

×