RQM Reportable REST API filter issue
Hello,
I am running into a strange issue, and was hoping someone might be able to help. I am supporting a RQM 4.0.6 environment (tomcat frontend, and DB2 database backend). We are running into issues with running a RqmApi call that uses a filter.
The following call works:
https://<server>:<port>/qm/service/com.ibm.rqm.integration.service.IIntegrationService/resources/<project>/testplan?fields=feed/entry/content/testplan/(identifier|title)
The following call does not work - it just seems to hang:
https://<server>:<port>/qm/service/com.ibm.rqm.integration.service.IIntegrationService/resources/<project>/testplan?fields=feed/entry/content/testplan[title='Test Plan']/(identifier|title)
The only difference is the second call should just return information about the testplan with a title of Test Plan, and filter out the other testplan (the part in bold). I have tried a similar calls on one of our 5.0.2 RQM environments and both calls pass.
Is there something wrong with the call I am using, or is there something wrong with RqmApi in version 4.0.6?
I have been told that the second call used to work on this environment, but I personally haven't gotten it to work.
Could any changes on the server (tomcat) prevent this type of call from succeeding (maybe some configuration was changed from when they said it worked to now when it doesn't work).
Any help would be greatly appreciated! Thanks!
Have a good day,
Steven J. Tuttle
Steven J. Tuttle
One answer
Hi Steven,
A couple of comments:
-You can remove the |title selection since it's included in the filter predicate.
-Remember to URL-encode your fields parameter value (if not already handled by your HTTP client).
-Your fields expression looks good. If the problem persists, please open a PMR.
A couple of comments:
-You can remove the |title selection since it's included in the filter predicate.
-Remember to URL-encode your fields parameter value (if not already handled by your HTTP client).
-Your fields expression looks good. If the problem persists, please open a PMR.
Comments
Don Yang
Jun 11 '15, 9:42 p.m.I tried with v4.0.6 (created a named "Test Plan" testplan) and there is no problem in return the expected test plan item in Firefox. I don't see any problem in this Reportable REST API itself. In your environment, whatever title of test plan, you will see the same hanging problem, is that right?
if you try with REST client, would you be able to get any result?
Steven Tuttle
Jun 15 '15, 9:43 a.m.I have tried the URL in the browser, as well as using the Advanced REST client in Chrome. Any title filter similar to the one shown will hang, and not get a return. I have tried testplan titles that contain spaces and some that don't, and they all hang. If I remove the title filter the call returns all testplans as expected, so parts of the RqmApi are working, but for some reason filters are not. I have tried the title filter on a 5.0.2 environment and that worked fine. I am thinking something might be messed up on the tomcat server, but no idea what would effect just the RqmApi because the environment itself seems to be working fine.