Populate custom extension attributes

To map custom extension attributes to fields in the source LDAP directory, configure settings in tdi-profiles-config.xml for each custom extension attribute.

To populate custom extension attributes into the Profiles database:

1. Open tdi-profiles-config.xml.

   After the TDI solution files are extracted, the file is located in:

   TDI/conf/LotusConnections-config

2. Modify the file to indicate the property to extend, the property's name, data type, and key. Use the following parameters:

   Parameter	Description
   extensionId	Required. The ID of the extension attribute.
   sourceKey	Required. Name of the LDAP attribute that maps to the extension attribute.
   userLabel	An administrator-defined label for the extension attribute that is populated into the database. This string does not display in the user interface or API.
   userTypeString	An administrator-defined string defining the data type of the extension attribute. This string does not display in the user interface or API.

   For example, to add an attribute called spokenLangs, the configuration would look similar to the following configuration in profiles-config.xml:

   <simpleAttribute extensionId="spokenLangs"
     length="64" 
     userLabel="Spoken Languages"
     userTypeString="String"
     sourceKey="spokenLang"/>

   The formatting is compatible between tdi-profiles-config.xml, and profiles-config.xml, allowing you to copy and paste configuration information between the files.

3. Save the changes to tdi-profiles-config.xml, and then close the file.

4. To populate the custom extension attributes, run one of the following...
   ./sync_all_dns.sh
   ./populate_from_dn_file.sh

Parent topic:
Extension properties in the data model