Attribute mapping for Profiles
When the Profiles directory service is enabled, IBM Connections relies on the Profiles database to provide user data such as user name, ID, and email.The internal name of the Profiles database is PEOPLEDB.
The following table shows the mapping relationships between Profiles, the Profiles directory service, Virtual Member Manager, and LDAP.
Table 1. Attribute mapping table
Profiles database column Profiles Directory Service Virtual Member Manager LDAP PROF_GUID ID uniqueId UUID/GUID/UNID (defined in RFC4122) PROF_DISPLAY_NAME Name cn/displayName cn/displayName PROF_MAIL mail/ibm-primaryEmail mail/ibm-primaryEmail PROF_SOURCE_UID DN uniqueName DN PROF_UID UID UID UID or samAccountName (in MS AD/ADAM only) PROF_LOGIN LOGIN Login attributes other than UID and mail LDAP login attributes other than UID and mail
Parent topic
Add LDAP data to the Profiles database
Related tasks
Use the Profiles population wizard
Use the Profiles population wizard in silent mode
Manually populating the Profiles database
Mapping fields manuallyRelated reference
Population functions for populating ID into PROF_GUID