Mapping Resource Attributes

When an organization model is created using the TIBCO Business Studio Organization Modeler, you can also create resource attributes. These attributes can contain data that the business process may access during runtime.

The following shows an example of some resource attributes that were created in TIBCO Business Studio:

These attributes are available for each resource that you create or map to groups or positions using the Organization Browser. For example, each resource’s cell phone number can be stored in the CellPhone attribute.

For information about creating attributes for the “Human Resource Type”, see the TIBCO Business Studio Organization Modeler User’s Guide.

When you display the LDAP Container Editor dialog in the Organization Browser, the resource attributes that were created in the organization model are displayed in the Resource Attribute Mapping section. For example:

The Organization Browser reads these from the organization model that it imports from the Directory Engine.

You may need to map one or more of these resource attributes to attributes in the LDAP sources you have defined in your LDAP container. You may need to do this because the business process does not have direct access to the attributes in the LDAP sources, but it does have access to the resource attributes in the organization model.

When you map a resource attribute to an LDAP attribute, it gives the business process access to the data in the LDAP attribute at runtime.

Also see Resource Attributes for information about editing the data in resource attributes that are not mapped to an LDAP source.

Assumption: For the example shown in these steps, let’s assume we know that the mail attribute in the deLAP2 LDAP source contains data that the business process needs. The business process has been designed in such a way to expect this data in the EmailAddress resource attribute. Therefore, if we map the mail LDAP attribute to the EmailAddress resource attribute, the business process will be able to access the user’s email address at runtime.

1. From the LDAP Container Editor dialog, click in the LDAP Attribute column in the Resource Attribute Mapping section, next to the resource attribute name you would like to map to the LDAP attribute.

   For this example, we will click next to the EmailAddress resource attribute:

   
2. Click in the white field that is exposed when you clicked in the LDAP Attribute column:

   

   This exposes a list of all attributes available in all of the LDAP sources that are defined in your LDAP container.

   Note: If there are LDAP attributes that contain binary data, those attributes may or may not be included in the list of LDAP attributes, depending on the setting of the getBinaryLDAPAttributes parameter in the WCC configuration file (config.xml). For information about this parameter, see the TIBCO Workspace Configuration and Customization guide.

   LDAP attributes that contain binary data are base-64 encoded, therefore they can be mapped to resource attributes of type String.

3. Select the desired LDAP attribute from the list — in this example, we’ll select “deLdap2 - mail” (this selects the “mail” attribute from the “deLdap2” LDAP source):

   

   Note - You can remove a mapped attribute by selecting “(none)” from the list of LDAP attributes.

4. Repeat steps 1-3 for each attribute you would like to map.
5. Click the Save button to save the mapping information.

   The Organization Browser is displayed. If you look at the list of potential resources, you’ll see the values that are being read from the LDAP source in the column for the attribute to which you mapped it. For example: