Today, I started to configure IBM Tivoli Directory Integrator (TDI) to load the employee data into the Profiles feature. One challenge is that the customer is only giving us access to their development LDAP which only contains 1% of the company. This will make it hard for us to show the value of Profiles and tagging with such a limited set of data. We are pushing the customer to get us more information.
Another challenge is that we are using Sun ONE LDAP as the LDAP provider and this is not yet supported. In order to get this to work, we had to make two changes:
- Modify the WIM properties
- Find the wimconfig.xml file under D:\WebSphere\AppServer\profiles\AppSrv01\config\cells\<cellName>\wim\config
- Create a copy of the file
- Open the file with your favorite editor
- Add this line to the <config:attributeConfigurations> element of <config:repositories>
- <config:externalIdAttributes name="nsuniqueid"/>
- Modify the TDI properties (map_dbrepos_from_source.properties)
- Ensure that PROF_GUID maps to nsuniqueid
In other news, I started an internal team blog for the community's core team. We intend to use this blog to keep track of meeting notes and disseminate news to the community without having to spam your inbox.