Welcome to the Jazz Community Forum
RQMCopyUtility Use Questions: Copy from RQM 2.0.x to 3.0.1
At times we have a problem where the data on our RQM test and development environments is "old" compared to what we currently have on our production environments. Complicating this is that our RQM test and development environments are used be various groups/teams and complete data refreshes are not practical or feasible as it would compromise data that a specific team is working with.
1) Reading through the description of this tool it appears it will copy data from one RQM instance to another.
2) Does the tool copying data from one RQM release version to another?
2.a) Is it possible to use this tool to copy data from RQM 2.0.1.1 instance to a RQM 3.0.1 instance?
3) Is this tool something we should even consider using?
4) What are the Pros and Cons in using this tool?
We might want to only copy specific RQM artifacts from Source to Destination: To do so I assume we will need to execute the utility for each specific artifact using the -id, artifactId=<id> parameter in conjunction with artifactType.
5) Is this assumption correct?
6) How is the REST ID of the artifact obtained?
2 answers
2) Does the tool copying data from one RQM release version to another?
2.a) Is it possible to use this tool to copy data from RQM 2.0.1.1 instance to a RQM 3.0.1 instance?
The copy tool is designed to copy artifacts between endpoints which use the same XML schema. Notable differences between the XML schemas in v2.x and v3.0.1 are described here: https://jazz.net/wiki/bin/view/Main/RqmApi#Notable_Schema_changes_from_RQM.
In summary, this scenario is not supported because the RQM 3.0.1 Reportable REST API (foundation of the RQM Copy Utility) is not backward compatible with RQM 2.x. There is work item to update the documentation to reflect this: Defect 55321 - Update RQM Copy Utility documentation with a cross-product-version support statement..
1) Reading through the description of this tool it appears it will copy data from one RQM instance to another.
2) Does the tool copying data from one RQM release version to another?
2.a) Is it possible to use this tool to copy data from RQM 2.0.1.1 instance to a RQM 3.0.1 instance?
3) Is this tool something we should even consider using?
4) What are the Pros and Cons in using this tool?
We might want to only copy specific RQM artifacts from Source to Destination: To do so I assume we will need to execute the utility for each specific artifact using the -id, artifactId=<id> parameter in conjunction with artifactType.
5) Is this assumption correct?
6) How is the REST ID of the artifact obtained?
1) Yes. See https://jazz.net/wiki/bin/view/Main/RQMCopyUtility#Introduction.
2) Yes. See https://jazz.net/wiki/bin/view/Main/RQMCopyUtility#Introduction.
2) a) No. See https://jazz.net/jazz02/resource/itemName/com.ibm.team.workitem.WorkItem/55321.
3) Yes. Also, consider using http://publib.boulder.ibm.com/infocenter/clmhelp/v3r0m1/topic/com.ibm.jazz.install.doc/topics/r_repotools_copy.html. Finally, you may be interested in https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/166347.
4) By way of pros, it's simple, public, proven, and customizable/configurable. By way of cons, it can be costly (performance) for larger repositories.
Note: The RQM Copy Utility is based on the RQM Reportable REST API (https://jazz.net/wiki/bin/view/Main/RqmApi).
5) Yes for specific artifacts. All artifacts of a specific type can be copied at one.
6) In the resource XML (see https://jazz.net/wiki/bin/view/Main/RqmApi#ScenarioCreateTip) or derived from the ID in the UI (see https://jazz.net/wiki/bin/view/Main/RqmApi#Internal_ID).