Copy project artifacts from RQM 2.0.x to RQM 3.0.x
Hi all I have a situation where a customer has RQM 2.0.1 on one server and RQM 3.0.1.2 on another server. They now need to copy projects from RQM 2.0.1 to RQM 3.0.1.2. Here migration does not seem to work because these are 2 different machines and public URI cannot be changed. We cannot also change the name of the CLM 3.0.1.2 server to that of the old one. The customer is not agreeing. So please let me know what could be the best possible way to copy projects. Will Copy utility work here? Regards V.Niranjan |
One answer
Will Copy utility work here? As per https://jazz.net/wiki/bin/view/Main/RqmApi The Reportable REST API is not compatible between Rational Quality Manager versions, due to differences in the Rational Quality Manager XML schemas. RQM Copy Utility uses the Reportable REST API, which means that it is not suitable for copying assets between 2.x and 3.x servers. There is really no supported solution for the scenario you described, at least not as of CLM 2011 (version 3.x). As you pointed out, you cannot change the public URI as per Moving Jazz Servers and URI Stability with CLM 2011. The best I can think of is this: Assumptions: 1) Old server (running RQM version 2.0.1) is rqm2.IBM.com 2) New server (running RQM version 3.0.1.2) is rqm3.IBM.com Steps: (1) Make a duplicate of the existing rqm2.IBM.com server and deploy it in an isolated network (so that it can still be addressed as rqm2.IBM.com without interfering with the production server which is addressable at the same rqm2.IBM.com hostname outside of the isolated network). (2) Upgrade the rqm2.IBM.com server in the isolated lab from 2.0.1 -> 3.0.1.2. (3) Shut down the production "rqm2.IBM.com" machine and temporarily re-introduce the rqm2.IBM.com instance running 3.0.1.2 into your network. (4) Use RQM Copy Utility to copy the assets from rqm2.IBM.com (running 3.0.1.2) to rqm3.IBM.com (also running 3.0.1.2). (5) Reverse the changes made in step 3. The major caveat is the RQM Copy Utility does not do a "full" copy. Meaning that certain metadada such as snapshots, history, etc will be lost during the process. The better long-term solution (if you can afford to wait) is to delay this project until a future version of CLM which supports proper server rename, move, and merging. Cheers, Patrick |
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.