Upgrade RQM 2.x into existing RCLM 3 instance?
We currently have a distributed RCLM 3.x architecture. We also have a standalone RQM 2.x instance. We would like to upgrade our RQM 2 instance into our existing RCLM 3.x instance before preparing to upgrade to 4. Do I follow the standard upgrade path from 2.x to 3.x, using the existing JTS server? This will result in 2 RQM 3.x instances (which is fine), correct? None of the project names in the RQM instances overlap, so I don't foresee any problems there. However, work item numbers will overlap - is this an issue? All of the documentation I found seems to relate to a Use Case of upgrading existing 2.x instances into a new JTS server. This is a slightly different use case. Has anyone done this or can provide some advice? |
One answer
Ralph Schoon (63.3k●3●36●46)
| answered Jul 10 '12, 9:21 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER edited Jul 10 '12, 9:22 a.m.
Hi Paul,
yes, you can upgrade your single RQM instance to share the existing JTS and you will have two RQM servers. See https://jazz.net/library/article/662 for how that looks like. Unfortunately I can't answer the work items question. |
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.