It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Follow this question
Question details

×10,835
×10,699
×4,257
×1,667
×677

question asked: Mar 10 '22, 4:45 a.m.
question was seen: 699 times
last updated: Mar 10 '22, 6:03 a.m.

Related questions

FAQ - How this Forum works

Is there a way to get all test artifacts for specific GC stream with only GC URI context as parameter or Header using OSLC api?

0
Swathi sheshadri (13●2) | asked Mar 10 '22, 4:45 a.m.
Hello Team,
Currently we are using the query to fetch all the testplans for particular stream added under a GC tree.
https://server/qm/oslc_qm/contexts/processAreaUUID/resources/com.ibm.rqm.planning.VersionedTestPlan?oslc_config.context=localStreamUUID along with
header “Configuration-Context” : https://server/gc/configuration/361.Above URL works fine. But is there a way to find all the test artifacts without passing parameter of
localStreamUUID ?
We are expecting something like below :
https://server/qm/oslc_qm/contexts/processAreaUUID/resources/com.ibm.rqm.planning.VersionedTestPlan?oslc_config.context=https://server/gc/configuration/361






One answer

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
David Honey (1.7k●1●7) | answered Mar 10 '22, 5:27 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
edited Mar 10 '22, 5:28 a.m.

Requests may either include a oslc_config.context parameter or a Configuration-Context header. The OSLC Configuration Management specification at https://docs.oasis-open-projects.org/oslc-op/config/v1.0/psd01/config-resources.html#configcontext says:

A server MUST support both these methods of passing configuration context. [CONFIG-RES-82]

If a request contains both a header and a query string, the server MUST use the query string. Servers MUST reject requests that contain two or more different configuration contexts passed in query strings. [CONFIG-RES-83]

Note that oslc_config.context should be a URL encoded URI of a configuration. Specifying just some UUID is not valid usage according to the OSLC Configuration Management specification. Since you specified both a query string and a header, the query string should be used, and the header value ignored.

Assuming that https://server/gc/configuration/361 is a correct GC URI, then https://rb-alm-11-p.de.bosch.com/qm/oslc_qm/contexts/_JcxK8FtpEemmsaDgWtsYZQ/resources/com.ibm.rqm.planning.VersionedTestPlan?oslc_config.context=https%3A%2F%2Fserver%2Fgc%2Fconfiguration%2F361 should work. OSLC compliant servers must accept URIs of global configurations and local configurations. If ETM does not, that would be an ETM defect.

Best regards,
David

Comments
Swathi sheshadri commented Mar 10 '22, 5:54 a.m.
Thank you for your reply.


But it did not give any response, only after we used localstreamcontext we were able to fetch all artifacts.
I'll check if i can raise an IBM case and have someone from the team to look into this.
David Honey commented Mar 10 '22, 6:03 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

If the GC you specified includes that local ETM configuration as a recursive contribution, that sounds like an ETM defect, and raising a ticket with IBM support is the best way forwards.

BTW, I assume that the URI are accessing is an OSLC query base that you discovered from an OSLC Query Capability through the OSLC Service Provider Catalog. If not, that REST service might not be an OSLC one, but an ETM proprietary one, and you might like to try using an OSLC query capability instead.

Your answer

Register or to post your answer.