HTTP request structure DNG Global Config Server
Hello everyone,
|
Accepted answer
Ian Barnard (2.3k●7●14)
| answered Aug 31 '22, 5:30 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER edited Aug 31 '22, 5:44 a.m.
When not using configuration management you don't need to specify the configuration and DOORS Next then uses the default configuration for that project. The same thing happens when projects are opt-in to configuration management, but using the default configuration (the component's initial stream) isn't going to get you data from any other configuration.
You'll have to include the configuration URL in your query e.g. by adding a query parameter &oslc_config.context=https://jazz.ibm.com:9443/gc/configuration/1234 where the config URL is URL-encoded so in the actual URL you GET from will look more like &oslc_config.context=https%3A%2F%2Fjazz.ibm.com%3A9443%2Fgc%2Fconfiguration%2F1234
The same method can be used with a DOORS Next local configuration URL.
Instead of a query parameter you can use a header Configuration-Context - don't use both header and query parameter, that's just not needed.
You can see more details about these in part of the OSLC Configuration Management specification https://docs.oasis-open-projects.org/oslc-op/config/v1.0/ps01/config-resources.html
Dennis Spohrer selected this answer as the correct answer
Comments
Dennis Spohrer
commented Sep 01 '22, 9:26 a.m.
Thanks for the quick reply, it worked!
Not completely sure but probably yes as these are the OSLC mechanisms for specifying the configuration to use.
|
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.