Preparing to import Rational ClearCase data with history

Edit online

Before you can import Rational® ClearCase® data with history to IBM® Engineering Workflow Management (EWM), the ClearCase Synchronizer must be configured and any prerequisite work must be completed in Rational ClearCase.

Configuring the ClearCase Synchronizer

Edit online

About this task

Before you can use the ClearCase Baseline Importer to import Rational ClearCase history, you must configure the ClearCase Synchronizer for synchronization by completing the following tasks:

Configure a synchronization host.
Create a synchronization process Rational ClearCase account.
Create a synchronization process EWM account in the repository.
Add the synchronization process EWM account to your team area.

See Preparing the synchronization environment for details on how to complete these tasks. If you have already completed these tasks for a previous synchronization or import, you can reuse your existing configuration.

Preparing Rational ClearCase data

Edit online

About this task

If you import data from base Rational ClearCase or if you import only a subset of baselines, rather than all baselines, from a UCM stream, you must complete some steps to prepare Rational ClearCase data for importation.

UCM baseline subset

If you need to import a subset of baselines, rather than all baselines, for a given component in a UCM stream, you must complete the following requirements in Rational ClearCase:

Create an attribute type in a VOB that is in the administrative hierarchy for the component. The vtype for the attribute must be string or integer, and the attribute value can be any valid string. For example, the value can be true.
Apply this attribute type to all baselines that you want to import for the component.

Base Rational ClearCase data

To import Rational ClearCase data from base Rational ClearCase, you must complete the following requirements in Rational ClearCase:

Labels must be applied to the base Rational ClearCase data that you want to import with history. These labels must be applied fully to the file system hierarchy in the VOB, starting from the sub-VOB component root or the VOB root. All of these labels must be locked before you begin to import history.
An attribute type must be created and applied to the label types with the associated version history that you want to import. The vtype for the attribute must be string or integer, and the attribute value applied to label types must be an incrementally increasing positive integer. The attribute type must be created in a VOB that is in the administrative hierarchy for the label type VOB.

The attribute values signify the order in which the importer processes label types. The importer sorts all available label types based on their attribute values and starts processing the type with the lowest value. For this reason, the lowest attribute value must be applied to the backstop label type that is used to create the synchronized stream.

Base Rational ClearCase data (separately labeled components)

To import separately labeled sub-VOB components in a single synchronization stream with history, you must complete the following requirements in Rational ClearCase:

Labels must be applied to the base Rational ClearCase data that you want to import with history. These labels must be applied fully to the file system hierarchy in the VOB, starting from the sub-VOB component root or the VOB root. All of these labels must be locked before you begin to import history.
A filter attribute type value is interpreted as a semi-colon separated list containing the order number and sub-VOB component name in pairs. For example:
```
1@subCompA;1@subCompB;1@subCompC
```
Note: The importer also accepts simple integer values for the filter attribute, where the integer value is treated as an order number for any sub-VOB components.
An attribute type must be created and applied to the label types with the associated version history that you want to import. The vtype for the attribute must be string or integer, and the attribute value applied to label types can be either a semi-colon separated list or an incrementally increasing positive integer. The attribute type must be created in a VOB that is in the administrative hierarchy for the label type VOB.
Create a filter attribute type for each folder using the following command:
```
cleartool mkattype -global -nc -shared -vtype string {filter attribute type name}
```
For example:
```
cleartool mkattype -global -nc -shared -vtype string subComp.order
```
In the following example, subCompA, subCompB, and SubCompC are the names of the Jazz® Team Server SCM components created in the ClearCase Synchronized Stream, and dir1, dir2, and dir3 are the component subfolders in the Rational ClearCase VOB, named vobD, that are mapped to the EWM SCM component:
```
vobD\dir1\subCompA 
vobD\dir2\subCompB
vobD\dir3\subCompC
```
Given a set of label types (BACKSTOP, LB1, LB2, LB3), specify the order in which the label types are imported for the specific sub-components.
```
cleartool mkattr subComp.order \"1@subCompA;1@subCompB;1@subCompC\" lbtype:BACKSTOP
cleartool mkattr subComp.order \"2@subCompA;2@subCompB;4@subCompC\" lbtype:LB1
cleartool mkattr subComp.order \"3@subCompA;3@subCompC\" lbtype:LB2
cleartool mkattr subComp.order \"4@subCompA;3@subCompB;2@subCompC\" lbtype:LB3
```
The components are imported in the following order:
```
subCompA: BACKSTOP, LB1, LB2, LB3
subCompB: BACKSTOP, LB1, LB3
subCompC: BACKSTOP, LB3, LB2, LB1
```