It's all about the answers!

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

×7,450
×4,710
×1,279

question asked: Aug 07, 7:13 a.m.
question was seen: 289 times
last updated: Aug 16, 2:13 a.m.

Related questions

Migrating project form one RTC instance to another RTC instance.

0
Mohd Khan (11●1●2) | asked Aug 07, 7:13 a.m.

we are having two diffrent RTC instance on diffrent servers and we need to migrate one from with complete history form one RTC to another one as due ho high heap utilization on servers. is there any way to migrate it from with History?

Comments
Ralph Schoon commented Aug 07, 8:13 a.m. | edited Aug 07, 8:41 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

If you have performance issues, I would suggest to contact IBM support.

Unfortunately, as far as I am aware, there is no such capability out of the box. There is no feature that would copy a project area over to another server, preserving history.

There is no built in feature to recreate a project area based on an existing one. It would be possible to write tools like this using the APIs. IBM Service might have something.

You can use Work Item export/import (e.g. using WCL), but you will loose history. 

You could use the distributed SCM feature of EWM to bring the source code SCM data over and preserve history.

This is my current state. I post as a comment. Maybe someone else has better answers.

Mohd Khan commented Aug 08, 6:32 a.m.

Hi Ralph, Thanks for the esponse


Ralph Schoon commented Aug 08, 7:45 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

Please note, the user Rick Williams below is spamming to create some kind of credibility. Ignore the content. 

You can only export a complete CCM repository, but that does not allow to split the servers. You can use Distributed SCM to migrate data over. You can also use https://jazz.net/wiki/bin/view/Deployment/MovingAComponentToANewServer to move an SCM component to another server. 

For work item history is not possible to keep the history. Also build related result data can not be kept, as far as I can tell.

Mohd Khan commented Aug 15, 11:12 a.m.

Hi Ralph can you please let me know how can I export project templete with all users and access roles.



Thanks and Regards,
Mohd Esteyak

Ralph Schoon commented Aug 16, 2:13 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

You can't, as mentioned. It is possible to use the API to recreate that information, but that is obviously not for free.

2 answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
sam detweiler (12.5k●6●195●201) | answered Aug 14, 3:52 p.m.

wow, is it really 10 years later ?


as a contractor i wrote a project copy tool including scm data from 3.x to 4.x
another team member did the work item migration part. 
we stored the source system work item number as a link in the new system work item.
we kept the old system readonly for a year as i recall 

good times

Sam 

Comments
Ralph Schoon commented Aug 15, 2:24 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

See answer below. Did not fit as comment.
0
permanent link
Ralph Schoon (63.3k●3●36●46) | answered Aug 15, 2:29 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

Yes, miss those good times. I know you guys and others e.g. IBM internal, myself and others have coded up ways to export, massage and import data.

I still believe my assessment is correct.
There is no out of the box tool to migrate project area structure. You can create a process template and try that, you can code something using the Plain Java Client Libraries/EWM SDK. I have done partial implementations.
We have a new capability to export SCM Components with history. The distributed SCM allows bringing over the SCM data and history as well.
It is technically possible to recreate the history for work items using the Plain Java Client Libraries/EWM SDK. otherwise there are limited import/export capabilities for EWM Work items. You can use CSV and I implemented a special 2 pass implementation for the import that could keep a link back to the old work item - in the same repository. See https://github.com/jazz-community/work-item-command-line

Users have also used off the shelf 3rd party synchronizers to bring over data. Usually it is not lossless and usually the history is lost. The best way to handle the work item history, is a back link to the original work item. The new only has the history after the import, the old keeps the old history. Once proven there is nobody looking into the old system, switch it off.   

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.