4. Introduction
● Sjaak Ursinus
● Working 11 Years for ilionx as consultant
● Working with IBM Connections since Jan 2007
● IBM Champion since start of program
● Twitter → sursinus
● Skype → sursinus
● Linkedin → www.linkedin.com/in/sursinus
● Various other social website's
5. Purpose of this presentation
● Knowledge about how IBM Connections
(DSX/Waltz) integrates with WIM/VMM
● Knowledge about what to do when some things
don't work in IBM Connections
● Why IBM States in documentation that some
attributes of LDAP need to be mapped to
certain COLUMNS in the PEOPLEDB
● Beter understanding how things work so you
can play with configs in your environment
when needed (warning : leave default as
much as possible)
6. Agenda
● Websphere Identity Manager components
● Explaining DSX
● How does this all work together
● Example
● Recap
● Questions
10. What do we call DSX ?
● DSX stands for Directory Service Extension
● Is part of IBM Connections profiles and
communities
● Is enabled in LotusConnections-config.xml
– <sloc:serviceReference
profiles_directory_service_extension_enabled="true
" serviceName="directory"/>
● WALTZ = Client for DSX and VMM (or LDAP)
● WPI = Waltz Profile Integration
● WCI = Waltz Communities Integration
11. So what is VMM
● VMM is basically an LDAP of its own
● With its own Schema
● Schema can be manipulated
● <node_profile>configcells<CellName>wim
– config
– model
● wimconfig.xml & wimdomain.xsd &
wimxmlextension.xml
13. Login properties
● So the login properties are LDAP attributes ?
NO!
● As said before VMM has its own schema
● The first VMM login property is a special one
because that is mapped to userPrincipal
● Connections applications use this
userPrincipal property to interface with WPI
20. Member tables
● Every app has its own member table
● Because of independent developed applications in
IBM TAP's environment
● DSX (WPI/WCI) is the VMM for IBM Connections
● WALTZ is the glue between DSX and VMM
● http://www.stickfight.co.uk/blog/Connections-Db-
Schema-Tip2-Finding-the-UserID
● Basically every application member table is a profiles
table on its own
21. Example
● EmployeeID (attribute available according domino
schema)
● Not default available in VMM schema
● VMM schema need to be extended
● Can then be used by VMM
● Can then be used by DSX/Waltz
– <sloc:serviceReference
profiles_directory_service_extension_enabled="true
" custom_user_id_attribute="EmployeeID"
serviceName="directory"/>
23. Example
● EmployeeID (attribute available according domino
schema)
● Not default available in VMM schema
● VMM schema need to be extended
● Can then be used by VMM
● Can then be used by DSX/Waltz
– <sloc:serviceReference
profiles_directory_service_extension_enabled="true
" custom_user_id_attribute="EmployeeID"
serviceName="directory"/>
24. Recap
● We have talked about WIM and VMM
● We have talked about DSX and what it does for IBM
Connections
● We have talked about WALTZ and where it is used for
● Member tables have been explained as well
● I have shown how all these different components
work together
● I have shown where config settings can be applied
and how they need to be applied