Synchronizing IBM Rational DOORS Next Gen [pre Sync 4.0] with HPE QC / ALM [pre Sync 3.5]

This section shows some common mappings between HPE QC / ALM standard task attributes and IBM® Rational DOORS Next Gen™ standard task attributes.

Setting up the proxyStorageAttribute property

Sync requires that the IBM Rational DOORS Next Gen repository has a proxyStorageAttribute property. For information on how to set this up, refer to the instructions on how to set up the proxyStorageAttribute property.

Task mapping

For IBM Rational DOORS Next Gen and HPE QC / ALM, this task-mapping should be used:

     <task-mapping conflict-notification-policy="Log">

Strings

String attributes do not need to be transformed with a caster and can be directly synchronized. Here is an example of a simple string mapping that could be used:

HPE QC / ALM Attribute IBM Rational DOORS Next Gen Attribute
Name Summary

Dates

A date caster is not needed when synchronizing between IBM Rational DOORS Next Gen and HPE QC / ALM repositories. Dates may be synchronized directly.

IBM Rational DOORS Next Gen DateTime, Time and Duration field types are not supported for synchronization.

Boolean attributes

Boolean attributes may be synchronized directly; however, HPE QC / ALM does not support boolean values. Boolean attributes will be treated as strings in HPE QC / ALM during a synchronization.

Value-mapped attributes

IBM Rational DOORS Next Gen tasks have an Unclassified value for severity, while HPE QC / ALM tasks do not. The Severity field is required, so one of the following actions should be taken:

HPE QC / ALM’s Priority IBM Rational DOORS Next Gen’s Severity
5-Urgent Blocker
4-Very High Critical
3-High Major
2-Medium Normal
1-Low Minor

Person Mappings

If users have the same user IDs on both repositories, then these attributes can be synchronized directly. If not, then a person mapping will need to be defined, as described in Person mapping definitions

To use the Person mapping, each attribute that has a person type needs to use a person caster, for example:

	<attribute-mapping>
            <attribute caster="person" id="RQ_REQ_AUTHOR"/>
            <attribute caster="person" id="dc:creator"/>
   </attribute-mapping>

Some attributes that may require person mappings:

HPE QC / ALM Attribute IBM Rational DOORS Next Gen Attribute
Author Reporter

Folder Sync

To configure Folder Sync from IBM Rational DOORS Next Gen to and from HPE QC / ALM, first ensure that the folder structures in IBM Rational DOORS Next Gen and HPE QC / ALM match. For example, folder structures for IBM Rational DOORS Next Gen and HPE QC / ALM could be set up as follows:

Example Folder Structure Example Folder Structure

Next, ensure that requirement folder configuration is configured to be retrieved from the HPE QC / ALM repository by checking the configuration option in the Repository Settings Dialog.

Folder Configuration Caching

Then ensure that the repository schema for each repository is current and refresh if necessary.

Folder synchronization can then be configured by adding an attribute mapping for the Requirement Folder attribute in IBM Rational DOORS Next Gen to the Requirement Folder attribute in HPE QC / ALM. No casters or other transformations are required. For example, configuration can be set up as follows:

Folder Mapping Example

The synchronizer.xml should contain configuration similar to the following:

        <attribute-mapping>
            <documentation></documentation>
            <attribute id="com.tasktop.ibm.rrc.folder"/>
            <attribute id="RQ_REQ_FOLDER"/>
        </attribute-mapping>

Limitations