It's all about the answers!

Ask a question

HTTP request structure DNG Global Config Server

Dennis Spohrer (231) | asked Aug 31 '22, 5:07 a.m.

Hello everyone,
I have a challenge, where I cannot find a solution for.
We are currently switching to a server, where we have global config on. Until now, we gathered our DNG modules via CURL and a http request. Now with global config on we cannot get the modules anymore.
Can you please tell me or give any resources on how to construct the new http string to query the dng with global config on?

Thanks in advance
Dennis :)

Accepted answer

permanent link
Ian Barnard (1.7k613) | answered Aug 31 '22, 5:30 a.m.
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= where the config URL is URL-encoded so in the actual URL you GET from will look more like &

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

Dennis Spohrer selected this answer as the correct answer

Dennis Spohrer commented Sep 01 '22, 9:26 a.m.

Thanks for the quick reply, it worked!
An additional question: is the http request changing for the RQM aswell, like for testcases and testplan?

Thanks in advance :)

Ian Barnard commented Sep 01 '22, 9:28 a.m.

Not completely sure but probably yes as these are the OSLC mechanisms for specifying the configuration to use.

Your answer

Register or to post your answer.