It's all about the answers!

Ask a question

Error Migrating RQM Artifacts to RM (restResponse code 403)


Russell Stanley (1623) | asked Jul 24 '11, 8:53 p.m.
New enterprise topology (4 physical server) CLM 3.0.1 deployment with 16 RQM 2.0.1.1 ifix3 projects getting migrated. So far, successful with most issues. Problem migrating RQM internal requirements (Non-ReqPro).

repository.common.TeamRepositoryException: Unable to create RM artifact, the restResponse code is: 403 (((Invalid Data)))

Note: Successfully migrated TEST project that had 6 native RQM requirements (((this validates that it is working)))

Please ADVISE how to clean out the internal RQM requirements fields (pre-migration) of MSFT Word special characters?

Need a way to traverse the RQM database and purge MSFT Word special characters.

Am I on the right track? Am I off base.

(Thanks for all comments)
-Stan

3 answers



permanent link
Paul Slauenwhite (8.4k12) | answered Jul 25 '11, 9:20 a.m.
FORUM MODERATOR / JAZZ DEVELOPER
Hi Stan,
Can you provide the XML of the failing requirement (https://jazz.net/wiki/bin/view/Main/RqmApi#ScenarioCreateTip)?

To answer you question, you can Create, Read, Update, and Delete (CRUD) most RQM resources using the public RQM Reportable REST API (see https://jazz.net/wiki/bin/view/Main/RqmApi), but you would have to manually (or write code) reads the feed of requirements, normalizes the special characters, and writes each requirement.

permanent link
Russell Stanley (1623) | answered Jul 25 '11, 11:45 a.m.
Hi Stan,
Can you provide the XML of the failing requirement (https://jazz.net/wiki/bin/view/Main/RqmApi#ScenarioCreateTip)?

To answer you question, you can Create, Read, Update, and Delete (CRUD) most RQM resources using the public RQM Reportable REST API (see https://jazz.net/wiki/bin/view/Main/RqmApi), but you would have to manually (or write code) reads the feed of requirements, normalizes the special characters, and writes each requirement.


I have not had the opportunity to come up to speed on hard-core XML extraction. Here is what I saw in the Tomcat window:

{START OF SCREEN SHOT}
<j><div xmlns="http://www.w3.org/1999/xhtml ><p>The system shall display relevant detailed data from the relevant archive database to an authorized user.<br><br>
Validate that yata yata {END OF SCREEN SHOT}

VERY CONCERNED ABOUT THE <p> AND THE <br>
embedded in the requirement text.

I did open a PMR too.

permanent link
Paul Slauenwhite (8.4k12) | answered Jul 25 '11, 12:09 p.m.
FORUM MODERATOR / JAZZ DEVELOPER
Please follow-up with the IBM Rational Support on the PMR for the solution.

As a work-around, you will have to manually remove these characters from the requirement text.

Your answer


Register or to post 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.