Move data from one RTC server to another RTC server
Hi,
I have a few questions regarding merging data from one RTC server to another. Let's say I have two RTC servers: RTC server1, RTC server2, and a RQM server - RQM serverA
1. Is there a possible way to move RTC server1 to RTC server2, i.e merging the data from server1 to server2?
2. RTC server1 and RQM serverA are linked (Testcases link to Task, Defects link to Execution Record), after data in RTC server1 is merged to RTC server2, will the links to RQM still work? If not, is it possible to update the linkage to make it again linked correctly?
Looking forwards to quick reply. This is kind of urgent. Great thanks!
Regards,
Jinhui
I have a few questions regarding merging data from one RTC server to another. Let's say I have two RTC servers: RTC server1, RTC server2, and a RQM server - RQM serverA
1. Is there a possible way to move RTC server1 to RTC server2, i.e merging the data from server1 to server2?
2. RTC server1 and RQM serverA are linked (Testcases link to Task, Defects link to Execution Record), after data in RTC server1 is merged to RTC server2, will the links to RQM still work? If not, is it possible to update the linkage to make it again linked correctly?
Looking forwards to quick reply. This is kind of urgent. Great thanks!
Regards,
Jinhui
3 answers
Hi,
what do you want to do? Move the whole server to another machine or move some data over?
Moving project areas form one server to another: as far as I know this is not possible today. Project move is one thing Development is looking into see this work item: https://jazz.net/jazz/web/projects/Jazz%20Foundation#action=com.ibm.team.workitem.viewWorkItem&itemId=_1C-2sKEqEeCM9svai9nXMw
You mention the biggest problem: it would be necessary to change all links between artifacts. If there are hidden links, e.g. in attachments, These links would be wrong or broken.
If you want to move the servers to new machines, the only way that is supported in released versions is by preserving the public URI using proxies or using DNS redirecting the logical host name used in the URI to the new machine. See https://jazz.net/library/article/749. There are numerous posts on this forum you might want to search for and look into for further hints. If ou have set up your system using logical host names in the URI e.g. https://rtc.my.domain.com:9443/ccm,https://qm.my.domain.com:9443/qm or proxies during the setup of your machine, you can install on a new machine and use the proxy or DNS to redirect. If you have used the hostname in the URL, you would have to make the new machine accessible using the old host name.
There is work being done in 4.0 to support server rename which is related to moving to a new machine.
what do you want to do? Move the whole server to another machine or move some data over?
Moving project areas form one server to another: as far as I know this is not possible today. Project move is one thing Development is looking into see this work item: https://jazz.net/jazz/web/projects/Jazz%20Foundation#action=com.ibm.team.workitem.viewWorkItem&itemId=_1C-2sKEqEeCM9svai9nXMw
You mention the biggest problem: it would be necessary to change all links between artifacts. If there are hidden links, e.g. in attachments, These links would be wrong or broken.
If you want to move the servers to new machines, the only way that is supported in released versions is by preserving the public URI using proxies or using DNS redirecting the logical host name used in the URI to the new machine. See https://jazz.net/library/article/749. There are numerous posts on this forum you might want to search for and look into for further hints. If ou have set up your system using logical host names in the URI e.g. https://rtc.my.domain.com:9443/ccm,https://qm.my.domain.com:9443/qm or proxies during the setup of your machine, you can install on a new machine and use the proxy or DNS to redirect. If you have used the hostname in the URL, you would have to make the new machine accessible using the old host name.
There is work being done in 4.0 to support server rename which is related to moving to a new machine.
And just to emphasize one point ... the work being done in 4.0 will allow you to move an entire repository to a new URL address (including a different server), but it does not provide any support for merging two repositories into one (the original request) or splitting a single repository into two. That functionality would be provided by the "project move" enhancement.
Cheers,
Geoff
Cheers,
Geoff
Hi,
what do you want to do? Move the whole server to another machine or move some data over?
Moving project areas form one server to another: as far as I know this is not possible today. Project move is one thing Development is looking into see this work item: https://jazz.net/jazz/web/projects/Jazz%20Foundation#action=com.ibm.team.workitem.viewWorkItem&itemId=_1C-2sKEqEeCM9svai9nXMw
You mention the biggest problem: it would be necessary to change all links between artifacts. If there are hidden links, e.g. in attachments, These links would be wrong or broken.
If you want to move the servers to new machines, the only way that is supported in released versions is by preserving the public URI using proxies or using DNS redirecting the logical host name used in the URI to the new machine. See https://jazz.net/library/article/749. There are numerous posts on this forum you might want to search for and look into for further hints. If ou have set up your system using logical host names in the URI e.g. https://rtc.my.domain.com:9443/ccm,https://qm.my.domain.com:9443/qm or proxies during the setup of your machine, you can install on a new machine and use the proxy or DNS to redirect. If you have used the hostname in the URL, you would have to make the new machine accessible using the old host name.
There is work being done in 4.0 to support server rename which is related to moving to a new machine.