Some DOORS Next reportable REST URLs not returning module data
Running ELM 6.0.6.1 and some DOORS Next modules' reportable REST URLs are not working. When I convert the OSLC link:
To a reportable REST link:
All the browser returns is this:
Instead of the expected module data:
Has anyone else encountered this? Any troubleshooting ideas?
|
One answer
You can try passing also the projectURI parameter to the request to be more specific in the scope (see Scope Parameters in https://jazz.net/wiki/bin/view/Main/DNGReportableRestAPI )
Alternatively, have you tried other ways to retrieve the module's artifacts as a workaround like creating a view and then querying like this
https://server:port/rm/publish/resources?viewURI=_E14X0U_GEeS8F9LvY4XGgg&projectURI=_CP50EE_GEeS8F9LvY4XGgg&moduleUri=_cb887c1a497e4525adb1be8f0f31172f
Comments Cristobal, thank you for your response. I have actually found a workaround to get the module published by using the RM local configuration instead of the global configuration. However, this does not provide RPE access to any link relationships, so it is truly a temporary workaround.
One concern I have with your view idea is that the view URI still needs to have an OSLC configuration context parameter. Here is an example view URI that is fully formed:
https://hbsclmprd1.url.com:9443/rm/web#action=com.ibm.rdm.web.pages.showArtifactV2&artifactURI=https%3A%2F%2Fhbsclmprd1.url.com%3A9443%2Frm%2Fresources%2F_fCIF0XRYEeq0RNvNhPIVfg&filterId=_uH39CXRYEeq0RNvNhPIVfg&oslc.configuration=https%3A%2F%2Fhbsclmprd1.url.com%3A9443%2Fgc%2Fconfiguration%2F22
My real desire is to understand why DOORS Next is not rendering the module via the reportable REST API correctly and fix it.
|
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.