How to fix "CRRRS6546E The specified configuration cannot be found" error when calling DNG Comparison API
We are using Doors Next Generation 7.0.3 (we are using it with ELM) and I am trying to call it's Comparison API since I will eventually use it within a custom widget. I found this example: https://www.ibm.com/support/pages/how-compare-two-configurations-rest-api-ibm-engineering-requirements-management-doors-next . However when I call the API, I get a ""CRRRS6546E The specified configuration cannot be found" error. For example:
https://server.url/rm/publish/diff?sourceConfigUri=https://server.url/gc/configuration/1343&targetConfigUri=https://server.url/gc/configuration/1326&includeItems=artifacts, where server.url is the URL of our ELM server.
If I access the soucrceConfigUri (https://server.url/gc/configuration/1343) and targetConfigUri (https://server.url/gc/configuration/1326) on the browser, I am taken to the streams in GCM so I don't see how the URIs I'm using are incorrect. Is there a particular method that has to be done to get the URIs so that they will work in the comparison API? The example document above did not explain how to get the URIs. I'm trying to get the URIs manually right now, but is there also a way to get them programmatically?
|
Accepted answer
Ian Barnard (2.3k●7●14)
| answered Sep 30, 12:11 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER edited Sep 30, 12:30 p.m. AFAIK the comparison API does comparison between two configurations in the same DOORS Next component - so first: use local configuration urls, i.e. not GC urls; second: make sure to URL encode query parameter values, i.e. the configuration urls. For example your URL should look like: https://server.url/rm/publish/diff?sourceConfigUri=https%3A%2F%2Fserver.url%2Fgc%2Fconfiguration%2F1343&targetConfigUri=https%3A%2F%2Fserver.url%2Fgc%2Fconfiguration%2F1326&includeItems=artifacts
You can find DOORS Next configuration URLs by discovery using the Process and OSLC APIs - there's a walkthrough of discovery here https://jazz.net/forum/questions/266334/dng-oslcfetch-components-from-project-area/266667
FYI The GC application has an OSLC Query API which will make it easier to find e.g. the GC URL for a configuration with a specific name. DOORS Next doesn't have this - you have to do the discovery sequence like above checking the dcterms:title of configurations for the one you want. The GC APIs are documented on your http://SERVER:PORT/gc/doc/scenarios
For an overview of all APIs start here https://jazz.net/wiki/bin/view/Deployment/ELMProductAPILanding
Joshua Baxter selected this answer as the correct answer
Comments I didn't know i had to use the local configuration URLS and not the GC URLS. I used the local configuration URLS and that worked, thanks! I honestly don't understand what the difference is between local configuration and global configuration other than the fact that working off the global configuration in ELM allows you to link to different project areas, and that you have to use local configuration URLs and not GC URLS for the comparison API. Are those the only 2 differences? 1
There are many differences. I guess one difference is that a GC can include multiple contributions from DOORS Next local configurations, so trying to use a GC URL would be ambiguous - isn't specific about which actual local configs should be compared. 1
I updated the comparison API doc on jazz.net wiki to say that both configs must be local. See https://jazz.net/wiki/bin/view/Main/DNGReportableRestAPI
Sorry don't know to both questions, except that there is only one public supported comparison API. |
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.