About this task
If you are going to import any data from base ClearCase
or if you are going to import only a subset of baselines, rather than
all baselines, from a UCM stream, there are some steps that must be
completed to prepare Rational ClearCase data
for importation.
UCM baseline subset
If you are
going 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 ClearCase:
- Create an attribute type in a VOB that is in the component's administrative
hierarchy. The attribute vtype must be of the form [string][integer],
and the attribute value can be any valid string. For example, the
value could be "true."
- Apply this attribute type to all baselines that you want to import
for the component.
Base ClearCase data
If
you are going to import ClearCase data from base ClearCase, you must
complete the following requirements in ClearCase:
- Label types must be applied to the base ClearCase data that you
intend to import with history. These label types must be applied fully
to the file-system hierarchy in the VOB, starting from the VOB root.
All of these label types must be locked before you begin to import
history.
- An attribute type must be created and applied to the label types
whose associated version history you want to import. The attribute
vtype must be of the form [string][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 label types' VOB's administrative hierarchy.
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 for the creation of the synchronized stream.