Help getting a requirement using OSLC and Global Configurations
I am trying to get a Requirements data using OSLC and Global Configurations. I know that if I use the direct link to an item, eg: https://Svr:9443/rm/resources/TX_vyxJkSjjEeuLj_u8pP3M9Q and set my Request Headers to: OSLC-Core-Version = 2.0 Accept = Application/rdf+xml I get the OLSC Resource data. If I don’t include the Accept header, this will open the item in the DOORS Web Interface. Now if I try and do the same for a Requirement that is in a Global Configuration and add the oslc_config.context parameter to the URL, eg: https://Svr:9443/rm/resources/TX_vyxJkSjjEeuLj_u8pP3M9Q?oslc_config.context=https%3A%2F%2FSvr %3A9443%2Frm%2Fcm%2Fstream%2F_u8rPECjjEeuLj_u8pP3M9Q
I get an ERR_INVALID_RESPONSE but by removing the Accept = Application/rdf+xml I do get the Resource Data back in rdf+xml format. Is this a bug or am I trying to access OLSC data for a Resource in a Global Configuration incorrectly? |
One answer
Ralph Schoon (63.5k●3●36●46)
| answered Mar 05 '21, 6:39 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER Please see https://jazz.net/wiki/bin/view/Deployment/CLMProductAPILanding and check the stuff about OSLC and the documented APIs.
Your question, it is almost certainly you issuing a wrong call, missing request headers and not being authenticated.
Also see https://rsjazz.wordpress.com/2019/05/13/using-a-rest-client-to-authenticate-to-elm-clm-applications/ how to use Postman (should also work for RESTCLIENT) to authenticate. Once that is done you can issue other calls. For RM authenticate with JTS.
Comments
Ralph Schoon
commented Mar 05 '21, 6:45 a.m.
| edited Mar 05 '21, 6:46 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Note, it is Accept:application/rdf+xml and not Accept:Application/rdf+xml not sure if that is an issue, just in case. You also might have to add
Content-Type: application/rdf+xml
Hi Ralph,
Thanks, yeah we managed to discover the issue with Access: application/rdf+xml, not Application/rdf+xml.
Interesting that this is inconsistent, as it works for getting other data with no problems. It feels like this might be a bug, given that all of the other interactions we do with OSLC work fine with the Accept:Application/rdf+xml set, including getting GC's, components, streams, artifacts etc. |
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.