Importing ClearCase history from a UCM stream

Use the ClearCase® Importer to import Rational® ClearCase data with full or partial baseline history from a UCM stream to Rational Team Concert™ source control. Once imported, you can modify the files in Rational Team Concert source control, but you cannot export to ClearCase.

Before you begin

Before you can import ClearCase data with baseline history, you must configure a synchronization host, then create and add a synchronization process account. If you are going to import a subset of baseline history, rather than all baseline history, from a UCM stream, you must also prepare the ClearCase data.

About this task

Once you have completed or verified all of the prerequisite requirements, complete the following tasks to import a UCM stream and then select files and folders to import with history from the UCM stream.

Importing a ClearCase UCM stream

Create a synchronization stream for importing UCM baseline history by completing the following steps.

Procedure

  1. Click File > Import.
  2. In the Import window, expand Jazz Source Control, select ClearCase Stream or Branch, and click Next.
  3. In the ClearCase Stream Information page, select Import with history from ClearCase. Because the ClearCase Importer does not export changes in Rational Team Concert source control to ClearCase, branch information is not used, so the branch type field is disabled. Click OK to close the Import with History information window.
  4. Specify a configuration for the Rational ClearCase dynamic view that the wizard creates to support the import process:
    1. To configure the view from a UCM stream, select Import from an existing UCM stream.
    2. Enter the name of an existing stream in the form stream-name@PVOB-tag. For example, to specify a stream named my_stream in a PVOB with the tag \projects, enter my_stream@\projects. Use the cleartool lsstream command or the Rational ClearCase Project Explorer to search for stream names.
    Note: You cannot import ClearCase history from a read-only stream. You can import the history from its parent stream if the parent stream is not read-only, or you can create a new, writable child stream identical to the read-only child stream, and then import history from the new stream.
    The wizard validates the syntax (but not the existence) of the stream name, then enables the Next button.
  5. Click Next.
  6. In the ClearCase Storage Information page, specify the network path to a directory where the wizard can create view storage for a Rational ClearCase dynamic view to enable importing from Rational ClearCase to Jazz™. The Importer seeds this entry with a network path consisting of the local host name and the string \VIEWSTORAGE. If this directory exists on the local host and is a valid location for view storage (it must be shared on Windows® or exported on the UNIX® system or Linux®), you can use it. Otherwise, specify the network path to another local or remote directory where the view storage can be created. The wizard creates a dynamic view with storage in this directory and a distinctive view tag (the prefix DO_NOT_USE and a UUID suffix). This view should be considered off limits by Rational ClearCase users.

    If applicable, check Enter additional option set information for creating ClearCase views and enter the appropriate values for Host, Host Path, and Global Path: the hostname, host-local path, and global storage path, respectively, of the ClearCase server storage location.

  7. Click Next. The wizard validates the view storage path and, if provided, the global storage path.
  8. On the Select Project or Team Area page, expand the repository entry and select the project or team area to which you added the synchronization process account (see Adding the synchronization process account to your team area). If there are no entries under the repository, verify that you are connected to the project area, then try again. Click Next.
  9. The Jazz Source Control Information page displays the name of a merge workspace that the wizard will create. You can choose another name if you want. If the repository contains a workspace with the name you chose, the wizard extends it with a string that makes it unique. (A merge workspace is a repository workspace where you resolve conflicts that occur when a file or folder has been modified in parallel in Rational ClearCase and Rational Team Concert source control).
  10. A default Synchronization user ID is displayed in this field. (The default ID is ccsync.) If you are using a synchronization user ID other than the default, replace the ID with the correct value. Enter the password for the Synchronization user ID. For more information, see Creating a synchronization process account.
  11. Type the path name where the ClearCase Connector is installed on this host in the Connector install location field, or click Browse to browse for it. The ClearCase Connector is typically installed in the Rational Team Concert installation directory.
  12. Select Start a Jazz Synchronization Engine process after the wizard finishes, and select Start the Select Files wizard after this wizard finishes.
  13. Click Finish. The ClearCase Importer creates a synchronized stream in Rational Team Concert, starts the synchronization engine process in the background, then opens the Select Files wizard.

Importing files and history with history

About this task

In the Select Files wizard, select ClearCase files and folders as synchronized roots and choose to import all or only some baselines for the component to which each folder belongs.

Procedure

  1. On the Select Files To Import page, complete one of the following actions to select files and folder in a UCM component whose baselines you want to import.
    Restriction: Only select folders or files that are visible in all baselines that you are going to import. As each successive baseline is imported, any synchronized roots that are not visible in that baseline are removed. Once a folder is removed as a synchronized root, no further baseline information is imported for that folder, even if it exists in later baselines.
    • If you have already imported files and folders with history, select Show currently imported objects in the table to display the synchronization roots in the Import Table.
    • To select files and folders by browsing mounted VOBs, click Browse to display a list of VOBs mounted by the synchronization host. (To speed up browsing, unmount any VOBs that you do not intend to access.) If no VOBs are visible in the window, verify that the VOBs from which you want to import are mounted on the synchronization host. When you have finished selecting files and folders, click OK to close the browser and display the selected paths in the list of Import Table.
    • To select files and folders manually, enter a path name that is visible in the Rational ClearCase stream you specified in the Import wizard and then click Add. The path name must be relative to the view root. If you are using a UCM stream, the path name must end at the root of a UCM component. All path names that you specify for import must begin with a VOB tag (without any leading / or \ characters) and include the full path from the VOB root to the project root folder. For example:

      sources\eclipse_projects\my_project

      selects a folder named my_project that is stored in the eclipse_projects folder of the VOB whose VOB tag is \sources.
  2. In the Choose baselines to import area, select the baseline history that you want to import for each component to which the synchronized roots belong:
    • Select Import all baselines to import the history from all baselines in the Rational ClearCase stream.
    • Select Import all baselines which have the following attribute type if you want to import a subset of baselines that have a particular attribute type associated with them. You can use Rational ClearCase to associate the attribute type with specific baselines. (See details above, in Before you begin.)
  3. Click Finish to close the Select Files wizard and begin importing the specified ClearCase files and folder with baseline history. Depending on the size of the component, number of baselines of the component in the stream, and the amount of historical data available in the baselines, the import could take from a few minutes to hours or days.

Results

After the initial import, you can import subsequent baseline history for the specified files and folders by running a synchronization on the synchronized stream. If you select additional files and/or folders as synchronized roots after the initial import, they are not imported with history from the initial baseline. They are imported only with history from baselines that are subsequent to the last import.
Tip: To import additional files and folders with the same history as the originally imported files and folders, create a new synchronized stream, selecting a synchronized root that contains all of the files and folders that you want to import with history.

Feedback

Did this help? You can provide feedback at Jazz.net (registration required): Comment in the forums or submit a bug