Hello,
did anybody manage to get this working with Domino/Connections/TDI and may provide me some hints ?
I have followed instructions on https://help.hcltechsw.com/connections/v65/admin/install/t_install_profiles_import_photos_ldap.html?hl=photo . I have imported pictures as binary data using LDAPAdmin(ldapadmin.org) into my person document. I have tried any kind of combination regarding used LDAP field in Domino & TDI configurations (including customized LDAP schema & LDAP field). I think the main problem is with documentation lacks values for profiles_tdi.properties regarding "source_ldap_return_attributes" as this value is already populated with "GUID" by default. My config atm:
source_ldap_return_attributes=jpegPhoto;binary
source_ldap_binary_attributes=GUID;jpegPhoto;binary
The TDI log contains 0 errors. It only says "skipping xy entries"(this 'xy' number covers all users - inactive, active, with LDAP binary data in photo field & without any binary data) and nothing is done.
Any ideas why it is skipping even users with values inside the LDAP field ?
I have already opened a case on this. HCL is working on it since > 2 months without any progress and it seems like nobody knows how to configure this import.
The envoirnment is running Connections 6.5 CR1 & WAS FP16 on Win2016. Domino is on 11.0.1. Image size is < 50kb, most <30kb.
Kind regards,
Jan
Hi Jan,
can't test in the moment, but had a look into profiles_tdi.xml
So in profiles_tdi.properties you need an entry:
load_photos_from_ldap_attr_name=<ldapattribute_with_photo>
Is this configured?
Have you tried to run TDI GUI and start the debugger? I think this will be the easiest way to find out how the AL is working.
Afaik the binary values you mentioned are only needed in combination with map_dbrepos_from_source.properties.
Regards
Christoph
Hi Christoph,
yes, the "attr_name"-parameter is set. ATM I can only run from command line - not from GUI. Will try to fix this & see if I can get any insights from GUI/debugger. Will report back later this week.
Thanks,
Jan
Hi all,
I've been testing this case internally at HCL, and initially could reproduce a problem. It does in fact appear that the issue is with profiles_tdi.xml and how it is configured for this specific batch file (specifically, what apparently is not being returned from LDAP despite being available). I was able to get it to work in the lab by making some modifications to this file, but before making a specific recommendation, we're conferring internally on whether the latest tdisol versions have this issue as well, whether any other config changes are needed/recommended, etc. Will circle back with recommendation once it is available.
Thank you,
Michael Montani
HCL Support
Thank you for the information & insights. I will wait for an update on this.
Just an update on this topic: HCL confirmed that this is an product issue.
After >4 months of analyzing the issue I have received a workaround for this issue (some adjustments to profiles_tdi.xml). If you also need a workaround before HCL offers a permanant fix please use "CS0209391" for support case reference.