Populating 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 Tivoli Directory Integrator Solution files are extracted, the file is located in the following directory:


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

      Table 1. Custom extension attribute parameters
      Parameter Description
      extensionId The ID of the extension attribute. Required.
      sourceKey The name of the LDAP attribute that maps to the extension attribute. Required.
      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.

      This parameter is optional.

      userTypeString An administrator-defined string defining the data type of the extension attribute. This string does not display in the user interface or API.

      This parameter is optional.

      For example, to add a simple attribute called spokenLangs, the configuration would look very similar to the configuration in the profiles-config.xml file:

      <simpleAttribute extensionId="spokenLangs"
        userLabel="Spoken Languages"

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

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

  4. To populate the custom extension attributes after the above configuration has been completed, run one of the following scripts:

    • IBM AIX or Linux™:


    • Microsoft™ Windows™:


    • AIX or Linux:


    • Microsoft Windows:


Parent topic

Add custom extension attributes for Profiles