How to Export a ProjectArea from one RTC server and can be imported to another RTC server?
Suppose RTC_A server has PRJ_A. PRJ_A is associated with lots of workitems, plans, iterations, team members. Now this PRJ_A needs to be replicated(or cloned) in another server RTC_B with all its associations. How can I achieve that?
case 1)Is there any export facility available for "project area" in RTC server? As well as the import facility so that Full project can be replicated? case 2)Is there any option to keep to projects in different servers can be in sync? For example PRJ_A in RTC_A is in sync with PRJ_A in RTC_B server. Any changes in RTC_A for PRJ_A will trigger the changes in RTC_B server. May be by using OSLS? But need the complete steps to follow. Note : For RTC Jazz Team Server 4.0.3 M3 is referred. |
2 answers
I believe you can clone the entire repository, perform a server rename on the new server, and archive the unneeded projects on the new server. That would give you a de-facto clone project capability (albeit a bit tedious one, also there are some support limitations, like, only one of the two servers can be ever used for production).
I believe there is an enhancement that covers moving project areas from one server to another, but at the moment jazz.net search does not work for me, I will try to find it when it does. |
Hi Soham,
Unfortunately there is no option to move project areas between different repositories. You can move only export/import work items and plans. By the way, is there any particular reason, that you use milestone version of RTC? RTC 4.0.3 has been already released. You can download it from here: https://jazz.net/downloads/rational-team-concert/releases/4.0.3 Best regards, Krzysztof Kazmierczyk Comments Hi Krzysztof Kazmierczyk,
all the workitem numbers will change. All the links will be broken (as the target is different)
Hi Soham,
@Krzysztof Kaźmierczyk : The objective is to clone the projects into different server. Because RTC_A where all the project areas created is a test server and evaluation version. But these project data are real. Now we need to copy(or clone) these data to another server RTC_B which is a brand new production server. These data needs to be cloned to RTC_B as we cant spend several moths to copy that data manually from RTC_A. |
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.
Comments
Why would you want to maintain a cloned project area with redundant data anyway ? What are the objectives ? If you can explain what you want to achieve then you might get better answers or alternate ways to achieve something similar.
@Indradri Basu : The objective is to clone the projects into different server. Because RTC_A where all the project areas created is a test server and evaluation version. But these project data are real. Now we need to copy(or clone) these data to another server RTC_B which is a new production serve. These data needs to be cloned the RTC_B as we cant spend several moths to copy that data manually from RTC_A.
unfortunately there is no support for what you want to do.
in my prior job we built our own tool, that did '90% of the work, but there were still manual tasks. keeping dates/times on history is really really hard.
@sam detweiler: Thank you for your reply. Could you please provide me bit more details about the tool? Have you implemented this using OSLC? Is there any help page/document available in internet so that it can be followed to build the tool.
I do not work for IBM. Unfortunately I am not able to discuss the tool my prior company built. It was built on top of the openSource ETL tool Pentaho, http://www.pentaho.com/
it did not use OSLC interfaces as they are not up to the data movement challenge.