cmi_migrate.pl

Generate a file of element versions that require CMI task associations

Applicability

Product

Command type

ClearCase®

Perl script

Platform

UNIX

Linux

Windows

Synopsis

ratlperl cmi_migrate.pl

Description

For the purpose of migrating from the (Perl) base-ClearCase/ClearQuest® integration to CMI, the script cmi_migrate.pl generates a file that lists ClearCase element versions that require CMI task associations. After you run cmi_migrate.pl, you use the clmutil cmi_repair ...-migration_file command to associate versions with the tasks. The migration does not remove the CrmRequest hyperlinks that were created by the V2 integration, but the V2 integration should be disabled after you complete the migration.

The script is interactive; you are prompted to supply the following information:
  • The VOB tag of the VOB that is to be migrated
  • A temp directory (which must exist) in which to store the output files
  • A filename for storing the results of parsing the V2 integration's config.pl file for CrmRequest hyperlinks (default: cmi_migration.txt)
  • A filename for storing the list of element versions that require CMI task associations (default: cmi_migration_versions.txt)

After you supply this information, the script parses the V2 integration's config.pl file and stores the extracted information in cmi_migration.txt. At this point you can specify CMI configuration information for all of the branch types that require migration, or you can quit the utility and modify the cmi_migration.txt file manually.

If you choose to quit, you can run the script again to resume the migration process. If you choose to continue, you are prompted for a description for the CMI provider, a query URI, and a name for the provider. After the configuration is complete, cmi_migrate.pl creates the attribute type required by CMI, runs the mkcmprovider command to configure the VOB and the participating branch types, and generates cmi_migration_versions.txt, the file that is used as input to clmutil.

Restrictions

You must run this script in a view, but the view's config spec is disregarded.
Note: Before running the script, lock the VOB so that users cannot generate new hyperlinks while the operation is under way (cleartool lock -nusers ...).

See also

IBM® Rational® Team Concert documentation, clmutil