Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

RPE traceability from RQM to DNG for CLM 6.0.3 with Configuration Management enabled?

Questions
Tags
Users
Badges
Oana Capatana
(23●5●20) Nov 08 '17, 12:28 a.m.

Hello,

I am creating an RPE template that traces from test cases to requirements in CLM 6.0.3 with Configuration Management enabled. I found that requirements were no longer retrievable via the testcase/requirement query so I had to use OSLC request to get the requirements that validate the test cases.
My problem is that all the above work fine if I run the report from RPE Launcher component, but when I upload the template and doc spec in RQM and the report is generated using RRDG I get the following error for the OSLC test case data source:
Error in engine Can not redirect to the OAuthentication identify URL. Request URL: https://<jazz_server>/qm/ <wbr> oslc_qm/contexts/_ <wbr> 4RCHUcK3Eeeh3IMpo5venA/ <wbr> resources/com.ibm.rqm. <wbr> planning.VersionedTestCase? <wbr> oslc.where=oslc:shortId=1 Reponse code: 200 Reponse message: OK 
I have tried setting other types of Authentication for that particular dynamic data source in the RPE template but with no luck.

Any ideas how this must be set to run from RQM 6.0.3?

0 votes

Comments
Kumaraswamy Gowda
Dec 06 '17, 5:36 a.m.

Hi Oana,

You don't have to go through the route of OSLC request to get requirements. You could either directly use OSLC URL along with pox profile header (https://rpeactual.com/2016/07/03/oslc-api-and-pox-profile-simplifies-clm-traceability/).... or convert OSLC URL into REST URL using javascript (from /rm/resources/1234 to /rm/publish/<text><resource>?resouorceURI=1234 (See https://jazz.net/wiki/bin/view/Main/DNGReportableRestAPI#Reporting_contexts).

This might still result in authentication issue. That is something we'll continue discussing here.

Thanks,
Kumar

Paul Slauenwhite
FORUM MODERATOR / JAZZ DEVELOPER Dec 06 '17, 6:26 a.m.

Oana, please see https://jazz.net/wiki/bin/view/Main/RqmOslcQmV2Api#Plain_Old_XML_POX_Profile_Reques.

1 answer
3,320 views
0 votes

One answer

Permanent link
Paul Slauenwhite
FORUM MODERATOR / JAZZ DEVELOPER (8.4k●1●2) Nov 29 '17, 11:15 a.m.

Looks like you're not including the oslc_config_context parameter (see https://jazz.net/wiki/bin/view/Main/RqmOslcQmV2Api#oslc_config_context).  That said, this should not cause an authentication issue.  The OSLC QM API does use oAuth.  Where you able to run an OSLC query when CM is disabled?

0 votes

Comments
Kumaraswamy Gowda
Dec 06 '17, 5:29 a.m.

@Paul, Within RPE, one could set configuration (local or global) with Configuration-context parameter (mostly header) for the data source URL. RPE UI supports picking the configuration using config picker delegated UI. I'm not sure how configuration version is set. Is it the olsc_config parameter appended to the data source URL? If yes, this oslc_config information needs to be used for the DNG OSLC/REST URL as well.

Paul Slauenwhite
FORUM MODERATOR / JAZZ DEVELOPER Dec 06 '17, 6:29 a.m.

Hi Kumar, yes, the configuration context (oslc_config_context parameter - see https://jazz.net/wiki/bin/view/Main/RqmOslcQmV2Api#oslc_config_context and https://jazz.net/wiki/bin/view/Main/RqmApi#oslc_config_context) is appended to the request URL.  I would assume it's required for the DNG REST requests. 

That said, this appears to be more of an authentication issue.  Are you able to make the requests using an external HTTP client (e.g. Poster)?

Your answer

Register or log in 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.

Ask a question
Guidelines
FAQ
Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details
× 7,495
× 6,121

Question asked: Nov 08 '17, 12:28 a.m.

Question was seen: 3,320 times

Last updated: Dec 06 '17, 6:29 a.m.

Confirmation Cancel Confirm