It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×10,958
×10,915

question asked: Feb 10 '14, 8:13 a.m.
question was seen: 6,109 times
last updated: Feb 18 '14, 2:10 a.m.

Related questions

PUT method failing on test plan xml

0
Chandrahasa Reddy D (57●1●53●60) | asked Feb 10 '14, 8:13 a.m.
Hi All,
I am trying to execute PUT method on test plan xml, but its failing and gives me response code as 500. I am using RQM 4.0.4 build. My RQM url utility is older version i.e., probably RQM 3.0.1. Do I need to update RQM url utility to 4.0.4 version to execute this successfully or is there any other workaround? please suggest.

One answer

Most liked answers ↑|Newest answers|Oldest answers

1
permanent link
Erica Tran (1.4k●7) | answered Feb 10 '14, 8:28 a.m.
JAZZ DEVELOPER
Hi Chandrahasa,

I'd first download the version of the utility that matches the version of RQM you're using (i.e. 4.0.4).  Since the utility is built on the REST API and this is not compatible between versions.  Here is the wiki page for the tool and the section on compatibility. 

RQM URL Utility Compatibility

I hope this helps. 
Comments
Chandrahasa Reddy D commented Feb 11 '14, 8:12 a.m.

Even after using RQMUrlUtility 4.0.4 I am getting same error while performing PUT on test plan resource. "RQMUrlUtility: Server Response code: 500"

Erica Tran commented Feb 11 '14, 11:37 a.m.
JAZZ DEVELOPER

Hi Chandrahasa,

Does a GET on a test plan work?  I would use this to make sure the XML and command syntax is OK.  Are there any more details for the error 500 that will help you narrow down the problem?  Anything in the qm.log?

Chandrahasa Reddy D commented Feb 12 '14, 2:22 a.m.

I don't think I have errors on xml syntax, because I am getting xml from GET method and thereafter posting it. Any suggestions? and also I am using administrator account only, no issues with permissions.

Chandrahasa Reddy D commented Feb 12 '14, 8:58 a.m.

Even for PUT on testsuite also not working ..same error here also. But I am able to PUT successfully on testcase resource.

Erica Tran commented Feb 12 '14, 12:14 p.m.
JAZZ DEVELOPER

It's interesting that it works with test cases and not test plans.  I was looking around on the forum and found the following post.  It is an Error 500 trying to use the utility to PUT a test case.  There is a defect noted in this post, so it appears test cases were fixed and maybe there's a defect with the other resources. 

RQMUrlUtility: Server Response code: 500 When adding New Tes
https://jazz.net/forum/questions/72292/rqmurlutility-server-response-code-500-when-adding-new-tes

Chandrahasa Reddy D commented Feb 13 '14, 1:09 a.m.

Thank you Erica.. what will be the solution that I can look for now ? Should I raise request to IBM ?

Erica Tran commented Feb 13 '14, 12:50 p.m.
JAZZ DEVELOPER

Yes, at this point it would probably be a good idea to open a PMR.  I suggest including the command, XML and qm.log when submitting the PMR.  You could also include a link to this forum post for some history.

Chandrahasa Reddy D commented Feb 18 '14, 2:03 a.m. | edited Feb 18 '14, 2:10 a.m.

Hi Erica,
I have examined the issue very closely using qm.log file, if the test plan is associated with requirements, requirements collection the PUT method fails. If I dont have these in test plan then PUT method will be successfully executed. In qm.log file, it says unable to get the requirement type, the error is "com.ibm.team.repository.common.TeamRepositoryException: Unable to get Requirement Type https://host:9443/rm/types?resourceContext=https://host:9443/jts/process/project-areas/_Ceb_9ZhWEeOVsq25hMgU2Q from RM Repository: https://host:9443/rm/ , RM Project Area: https://host:9443/jts/process/project-areas/_Ceb_9ZhWEeOVsq25hMgU2Q , the return code is: 403 (Forbidden)". What suggestions you can give me to resolve this issue, ?  pls note I have given all required permissions to the use.

showing 5 of 8 show 3 more comments

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.