Configuring and using the ClearCase Synchronizer

You must configure the synchronization host and create a ClearCase® Synchronized Stream before any files or folders can be synchronized with Rational® ClearCase.
Edition note: The feature described here applies to Rational Team Concert™ Standard edition and Enterprise edition only.
To use the ClearCase Synchronizer, you configure one or more Rational ClearCase hosts to support synchronization between Rational Team Concert source control and Rational ClearCase and then define one or more ClearCase Synchronized Streams that contain files and folders to import from Rational ClearCase or export from Rational Team Concert source control. After this step is complete, users can modify these files and folders in either environment. Regular, automated synchronization keeps both environments up to date.

A synchronization process retrieves changes created in Rational Team Concert source control and checks them in to Rational ClearCase as new versions. It also retrieves changes created in Rational ClearCase and delivers them to a Rational Team Concert source control stream called a ClearCase Synchronized Stream. When conflicts occur because a file or folder has been modified in both Rational ClearCase and Rational Team Concert source control, they appear as incoming change sets for a special repository workspace known as the merge workspace. The merge workspace owner (typically a team lead) resolves the conflicts and then delivers the merged change sets to the synchronized stream, where they can be accessed by any team member.

To configure synchronization:
  1. Configure a synchronization host.
  2. Create a synchronization process account in the repository.
  3. Add the synchronization process account to your team area.
  4. Create a ClearCase Synchronized Stream.
Figure 1 illustrates the interactions among the synchronization host, the Jazz Team Server, and Rational ClearCase.
Figure 1. Synchronization data flow
The synchronization process copies versions selected by a ClearCase view to a Jazz source control stream called a ClearCase Synchronized Stream.
New versions selected by a Rational ClearCase dynamic view running on the synchronization host are committed to the ClearCase Synchronized Stream by the synchronization process. If any items in the synchronized stream have been modified concurrently by Rational Team Concert source control users and Rational ClearCase users, they appear in an incoming change set for the merge workspace. The merge workspace owner resolves the conflicts, and then delivers the merged results to the ClearCase Synchronized Stream. Any Rational Team Concert source control user can create a repository workspace from this stream or add it as a flow target of a repository workspace. Changes delivered from a repository workspace to the ClearCase Synchronized Stream are checked in to Rational ClearCase the next time the synchronization process runs.

Feedback

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