Add profile typesProfile types can be used to configure the layout of the main Profiles page and the layout of the widgets used in Profiles.
IBM Connections supports multiple attribute layouts based on different profile types. In addition to different attribute layouts, custom extension attributes are also supported for every profile type.
Because all profiles share one schema, an extension attribute, such as customers, has the same semantic meaning for all profile types. However, you can choose to associate a particular attribute with a profile based on profile type. The user interface configuration, including display characteristics and whether an attribute can be edited, is also configurable for custom extension attributes based on profile type.
The following applications can be associated with a profile type:
- Attributes and attribute layout
- Custom extension attributes and custom extension attribute layout
- Search results layout
- Business card layout
- ATOM API attributes
- Widgets and widget layout
Note: For more information on adding widgets to Profiles, see Add custom widgets to Profiles.
To enable multiple profile types, add the following line to the IBM Tivoli Directory Integrator map_dbrepos_from_source.properties file before population or synchronization:
profileType=<LDAP field or function>
If you do not add this line to the file, the default profile type is used.
For more information about mapping LDAP properties, see the Mapping fields manually topic.
When configuring profile types for the layout of Profiles, you make the configuration changes in the profiles-config.xml file. To add profile types for widget layout, you make the configuration changes in the widgets-config.xml file.
Configure profile types for widget layout
To configure widget layout, you can add a profile type containing the widget layout configuration to Profiles in the widgets-config.xml file.
Configure profile types for attribute layout
To configure a profile type for profile attribute layout, you add the profile type containing the attribute layout to the profiles-config.xml file. Profile attribute data is included in the output of the Profiles API by default. To prevent attributes from being included in the API, you need to define which attributes should not be output for each profile type.
Parent topicCustomize Profiles
Configure features by profile type
Add custom widgets to Profiles
Mapping fields manually