Custom attribute mapping configuration

This page has not been liked. Updated 8/5/15, 9:48 AM by cfjohnstTags: None

This page contains information about how to map values from IBM SmartCloud Control Desk 7.5.1 or higher tickets to custom attributes in Rational Team Concert 4.0.1 or higher.  

Note: This configuration cannot be done if either product is at an earlier version.


Most OSLC Providers like Rational Team Concert have shape documents which describe the resources they provide.

By default, this integration makes use of the standard Change Management 2.0 shape document to describe work items in the Rational products.  In the OSLC Providers application, you can view the Change Management shape document by using the Add/Modify Resource Types action.  You can also use this application to map attributes from IBM Control Desk tickets to properties listed in the shape document.  If such a mapping is created, the defect will be pre-filled with the values you specify from IBM Control Desk when you choose to create a defect from the Problem ticket.

This example shows how the summary of the ticket can be mapped to the summary of the defect.

  1. Go to Integration > OSLC Providers.
  3. Select the create interaction in the OSLC Interactions table.
  4. In the Interaction Mappings table, notice that the Problem summary is mapped to the defect summary.

This means that when you choose to Create a defect in the Problem application, the Problem description is pre-filled in the defect title.

If you add custom attributes to work items in Rational Team Concert, those attributes will not be in the standard Change Management 2.0 shape document, which means you cannot map IBM Control Desk values to your custom attributes.  If you want to map to custom attributes, you must retrieve an updated shape document from Rational Team Concert and import it into IBM Control Desk.  

Note: This approach is not recommended if you are integrating one IBM Control Desk with both Rational Team Concert and Rational ClearQuest.  In that case, the common Change Management 2.0 shape document should be used for both.


1. After custom attributes are added in Rational Team Concert, retrieve the new shape document.

a) Go to the Service Provider catalog, typically https://<rtc_host>:9443/ccm/oslc/workitems/catalog.

b) Look for the Project Area where you added custom attributes and request the services.xml link for that provider using a tool like Firefox Poster.  Set the OSLC-Core-Version header to 2.0.

c) Look for the creation factory with usage set to <oslc:usage rdf:resource=""/>.

d) Inside that creation factory, you will see an <oslc:resourceShape> tag which points a URL that contains the shape document.

e) Request the shape document from the URL, for example, from https://<rtc_host>:9443/ccm/oslc/context/_5wuzkEkZEeKeZ_KnLx0K_Q/shapes/workitems/defect

f) Save the XML that is returned in a file on the IBM Control Desk administrative workstation.


2. Rational Team Concert 4.0.1 has a defect where custom attributes always get exposed with a value-type of Resource.  IBM Control Desk cannot map to properties with a value-type of Resource, so you must change the value-type of the custom attribute in the shape document before importing it into IBM Control Desk.  A fix for this defect is planned for Rational Team Concert 4.0.4.


a) Open the shape document you saved in Step 1, Part f.

b) Find the custom attribute you added by searching for the name of the attribute.  You should find an entry like this:



          <oslc:Property rdf:about="">

            <oslc:valueType rdf:resource=""/>

            <oslc:representation rdf:resource=""/>

            <oslc:readOnly rdf:datatype="">false</oslc:readOnly>

            <oslc:propertyDefinition rdf:resource=""/>

            <oslc:occurs rdf:resource=""/>

            <oslc:name rdf:datatype="">CustomAttribute</oslc:name>


            <dcterms:title rdf:parseType="Literal">CustomAttribute</dcterms:title>




c) Find the <oslc:valueType> tag.  Change the value of the rdf:resource to be the correct type.  For example, if the custom attribute added in Rational Team Concert was a string, the line:


    <oslc:valueType rdf:resource=""/>


    should be replaced with:


    <oslc:valueType rdf:resource=""/>


A list of valid value-types can be found in the OSLC Core Specification.

d) Repeat steps b and c for all custom attributes that were added in Rational Team Concert.

e) Save the changes to the shape document.


3. Import the shape document in IBM Control Desk.

a) Go to Integration > OSLC Providers.

b) Select the Add/Modify Resource Types action.

c) Expand the SCCDCR resource type.

d) Select Import.

e) Browse for the shape document file and choose OK.


4. Now you can map IBM Control Desk attributes to custom attributes in Rational Team Concert.


a) Go to Integration > OSLC Providers.


c) Select the create interaction in the OSLC Interactions table.

d) Under the Interactions Mapping table, select New Row.

e) In the Source Mapping Expression field, choose the value you want to pre-fill into the defect from IBM Control Desk.

f) In the Target Resource Property field, choose the custom attribute you want to map to.

g) Save the changes and attempt to create a new defect.  You should see that the custom attribute is being pre-filled with the value you specified from IBM Control Desk.