cmi_migrate.pl

Generate a file of element versions that require CMI task associations

Applicability

Product

Command type

VersionVault

Perl script

Platform

UNIX®

Linux®

Windows®

Synopsis

ratlperl cmi_migrate.pl

Description

For the purpose of migrating from the UCM VersionVault/Compass integration (SQUID) to CMI, the script cmi_migrate.pl generates a file that lists all activities in a user-specified project VOB that require task associations, based upon a user-specified list of Compass-enabled projects to migrate. After you run cmi_migrate.pl, you use the clmutil cmi_repair ...-migration_file command to associate activities with the tasks and to update the Links tab on the Compass records. The migration does not remove the artifacts that were created by the SQUID integration, but it is recommended that the SQUID integration be placed in suspend mode or disabled after the migration process has been completed. Note that disabling the SQUID integration is irreversible and will remove all artifacts it has created in the VOB. If you do not yet want to disable the SQUID integration, you can instead suspend it temporarily.

The script is interactive; you are prompted to supply the following information:
  • The VOB tag of the project 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 the user-specified list of Compass-enabled projects to migrate (default: cmi_migration.txt)
  • A filename for storing the list of UCM activities that require CMI task associations (default: cmi_migration_activities.txt)

After you supply this information, the script parses the specified list of Compass-enabled projects, lists the streams contained in those projects, and stores the extracted information in cmi_migration.txt. At this point you can specify CMI configuration information for all of the streams 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 project VOB and the participating streams, and generates cmi_migration_activities.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 project VOB so that users cannot generate new SQUID artifacts while the operation is under way (cleartool lock -nusers ...).