How to move RTC 2.x into another server running 3.0
We would like to move an RTC 2.x environment from one server into another server running RTC 3.0. By doing this, we also get to keep the 2.x environment as a fallback.
On the 3.0 server, we would prefer not to have any traces of RTC 2.x installed on it. Because of this restriction, upgrading on the same server from 2.x to 3.0, wouldn't be an option. Does anyone have any suggestions on how we can accomplish this ? |
One answer
Ralph Schoon (63.5k●3●36●46)
| answered Mar 14 '11, 1:58 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Hi,
as a first note, currently it is (as far as I am aware) not supported change the host name of an RTC server. RTC needs a stable URL which includes the host name. I think you could migrate to RTC3 on your initial server. Then you could install the software on the new server. You could configure RTC on the new server, keeping the URI stable (you could also get some important information here: http://jazz.net/library/article/547). Afterward you could migrate the content of the RTC and JTS repositories to the new server using repotools. You could shutdown your old server and switch to the new one. Please note due to DNS and the host name you can probably not run both servers in the same network. Ralph We would like to move an RTC 2.x environment from one server into another server running RTC 3.0. By doing this, we also get to keep the 2.x environment as a fallback. |
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.