TDI

Card image cap

I had one Connections’ environment that I wanted to switch from OpenLDAP to Active Directory LDAP. The old OpenLDAP environment used LDAPS to connect, and so I assumed that the change was done quickly.

The first step was to make a copy of the tdisol folder I used for OpenLDAP and start changing the configuration files for the new LDAP server.

Created: Read in about 4 min
Aaron Burden: Fountain pen and a notebook
I read an open APAR on IBM Connections today (login required!): LO73245 Description: TDI’s sync_all_users.sh doesn’t allow us to import departmentNumbers longer than 16 chars, although the database schema supports values up to 24 chars. And as local solution: worked around the issue with creating a custom field I had a very similar problem with validation of LDAP Search filter (which is saved in employee-table too) and searched longer to solve this (I set sync_store_source_url=false), but the real error was like here in validate_dbrepos_fields.properties. When you open validate_dbrepos_fields.properties (in your tdisol directory) you found following: deptNumber=16 So here is the validation error and not in the database!
Created:
Last Update:
Read in about 1 min
Aaron Burden: Fountain pen and a notebook
On one of my IBM Connections Site i had a problem with directory search (better the typeahead search). When we searched single characters no business cards are displayed. I use Firebug for Chrome here and you see, that the search gets an result back from Connections, but no business cards are displayed. When i open this get statement i get a list of profile documents in JSON format: In this case i a got a list of about 20 User profiles. When i search a little bit more detailed i get an error of a Javascript, which should interpret the JSON list.
Created:
Last Update:
Read in about 2 min