Migrating context roots from 2.0 to 4.0
Hello,
We've been running into errors migrating an RRC project up from 2.0 to 3.0.1 and from there to 4.0.1. Can one change the context roots of the contents of a repository using the repo tools cli? I assumed this was how it worked, given the oldContextRoot and newContextRoot attributes. Should the 3.0+ environments be set up with the standard 3x/4x context roots?
Ultimately the 2.0 project needs to come to a modern production server, for which naturally we would like to use modern context roots.
|
Accepted answer
Benjamin Silverman (4.1k●6●10)
| answered Dec 06 '12, 11:43 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Unfortunately not. Repotools -export/-import can be used to move data from one server to another, but the requirement of maintaining the same public URI remains in place. If you must change the public URI, you can go through the server rename process, but the server needs to be configured with the original public URI first.
Joshua Boston selected this answer as the correct answer
|
3 other answers
|
Benjamin Silverman (4.1k●6●10)
| answered Dec 06 '12, 8:10 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Hi Joshua,
The context root of the RRC application needs to be the same as it was in 2.x, as does the public URI. Assuming the context root was "/rdm" in 2.x, you need to install 3.x/4.x with the same context root (/rdm). You do not have to keep the old "jazz" context root for the Jazz Team Server however (ie - you can use /jts instead of /jazz for Jazz Team Server when you upgrade). You also need to make sure the server you are migrating to has the same host name as the old 2.x server, as you cannot change the host name or any part of the public URI (ie - protocol, host, port, context root) during the migration. Hope it helps, Comments Even using the repo export command line tools, it is not possible to move artifacts/projects up the versions into a new public URI (and new context roots)? No, it is not.
Hello, I should add that the above reference includes a workshop we had back in 2011 to help educate folks on how to perform an upgrade from 2x to 301. This should help you understand what the process is. Try it out. The reference page also has articles that explain the public URI constraint.
|
Since you mentioned upgrading all the way to v4.0.1, there are some enhancements to the server rename process in the 4.0.1 release. The server rename is not for everyone. It should be performed after an upgrade. Please read the updated documentation to see if server rename is appropriate for your situation, server rename doc in 4.0.1.
|
In addition to the updated documentation, there is this article -
https://jazz.net/library/article/1120 and also another article - https://jazz.net/library/article/1148 which is specifically about the context root. 1148 has not been published yet, but will be published soon. |
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.