It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,880
×4,715

question asked: Jan 21 '14, 2:24 a.m.
question was seen: 5,305 times
last updated: Jan 22 '14, 7:02 a.m.

Related questions

Migrating elements with history from CC to RTC 4.0.5

0
Dhruv Bansal (16●6●7) | asked Jan 21 '14, 2:24 a.m.
Hi,

While migrating elements with history from CC to RTC 4.0.5 what has been found is that versions that are baselined got migrated whereas versions that are not baselined didn't.

Is there some other way to migrate/import those versions as well.


5 answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Arun K Sriramaiah (3.2k●2●36●77) | answered Jan 21 '14, 2:49 a.m.
Hi Dhruv,

Pls find the below link, and see if it helps.

http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0m5/index.jsp?re=1&topic=/com.ibm.team.connector.scm.cc.doc/topics/c_intro.html&scope=null

Regards,
Arun
0
permanent link
Dhruv Bansal (16●6●7) | answered Jan 21 '14, 3:25 a.m.
Hi Arun,

Checked that and already imported version but my question how can we import all the version even those versions that are not baselined.

Thanks
Dhruv
0
permanent link
Dr. Hans-Joachim Pross (1.1k●44●58) | answered Jan 21 '14, 4:21 a.m.
JAZZ DEVELOPER
edited Jan 21 '14, 4:21 a.m.
AFAIK importing uses only baselined OR labeled versions. If you really need all - and I assume, not labeled versions are not important because if so, they would have been labeled - you might want to label them before importing.
0
permanent link
Dhruv Bansal (16●6●7) | answered Jan 21 '14, 6:19 a.m.

RTC 4.0.5 supports but how to do that??


ClearCase Importer

New ClearCase Version Importer has improved migration capabilities

Previously, the ClearCase history importer could import versions with labels in a single sequence. The importer did not import versions without labels or UCM baselines, and it also required several manual steps to import multiple branches or UCM streams from Rational ClearCase. Now, the new ClearCase Version Importer can migrate all the versions in any branches in Rational ClearCase in a single operation, and the version branching is also replicated in Rational Team Concert source control. The importer also preserves the checked-in user information.

Two new sub-commands were added to the ClearCase Synchronizer installation package. When you migrate data from a Rational ClearCase VOB to Rational Team Concert source control, you first export the versions and their metadata to intermediate files with this command: 

	>ccc export ccase -d <intermediate data directory> 
	                  -i <ClearCase view-extended path>
	                  -F <format string(fmt_ccase) for RTC change-set comment>
Then, you can import the intermediate data to Rational Team Concert source control with this command: 
	>ccc import ccase -d <intermediate data directory> 
	                  -s <RTC stream>
	                  -c <RTC component>
	                  -r <RTC repository URL>
	                  -u <user name>
	                  -P <password>
Before you run the import command, you can optionally configure the credential mapping from Rational ClearCase to Rational Team Concert. By specifying the credential mapping, you can see the Rational Team Concert change sets created during the import are owned by the specified mapped account in the file's history.

When the import command completes, all the files under the specified Rational ClearCase view-extended path are imported into Rational Team Concert, and when you open a file's history, you can find all the versions that were in the Rational ClearCase VOB:

Note: This new importer can be used for both Base ClearCase and UCM ClearCase, but it does not import UCM metadata. And it does not import label types as a Rational Team Concert baseline in this release.
0
permanent link
Dhruv Bansal (16●6●7) | answered Jan 22 '14, 7:02 a.m.
C:\Program Files (x86)\IBM\ClearCaseSynchronizer\ccctools\eclipse>ccc import cca
se -d \\IBM-2TDINACNRHC\Views\MIG_CC_RTC -s Test_Migration_Integration -c COMP_S
OPS -r https://ibm-2tdinacnrhc:9443/ccm/ -u DHRUV -P ADMIN
Ambiguous selector "COMP_SOPS" matched multiple items:
Possible matches:
  (1000) "COMP_SOPS"
  (1001) "COMP_SOPS"
Problem running 'import ccase':
Could not import data to Jazz SCM because of the following error:
Ambiguous component "COMP_SOPS".

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.