What is vvc.configuration in header while fetching DNG 6.0 List of Artifact Links
I am using on-premise version of DNG 6.0. I am trying to fetch the related artifacts of an artifacts.
In DNG 5.0 i have used the following query to fetch the data
[https://192.168.2.51:9443/rm/comments?resourceURI=https://192.168.2.51:9443/rm/resources/_LmDoAVuMEeWr09UU68yifg].
I used to get the link collection through this.
The header i have to use is
DoorsRP-Request-Type and Accept along with the CookieContainer(authentication cookies).
So now in DNG 6.0 i can't seem to get the data's at all..
I tried intercepting the request and found one more Header needs to be there in order to complete the request now.
vvc.configuration
Sample Value in my Case : [https://192.168.2.51:9443/rm/cm/stream/_dOaqAFuFEeWr09UU68yifg]
And this header is also mandatory for fetching active comments and attchments(links) of artifacts.
Can anybody help with how get this header params value correctly..?
I am using C#. And trying things out with restclient in chrome.
3 answers
The "vvc.configuration" parameter refers to a snapshot or baseline URL. This is introduced along with configuration management in RDNG 6.0.
https://jazz.net/downloads/rational-doors-next-generation/releases/6.0?p=news#TOC_E_a
https://jazz.net/forum/questions/202941/reportable-rest-api-with-global-configuration
https://jazz.net/downloads/rational-doors-next-generation/releases/6.0?p=news#TOC_E_a
https://jazz.net/forum/questions/202941/reportable-rest-api-with-global-configuration
This REST api you are using is not supported, and is subject to change without notice. IBM does not support your use of this API, and I would recommend that you don't use it.
That said...
The vvc.configuration parameter defines the configuration context of the request (see OASIS OSLC specification for explanation of this term).
The supported DNG api is not yet fleshed out enough for you to discover valid contexts programmatically. There is an OSLC Delegated UI which allows a user to select from the available configurations. Take a look at the root services document and the oslc_config:cmServiceProviders property.
That said...
The vvc.configuration parameter defines the configuration context of the request (see OASIS OSLC specification for explanation of this term).
The supported DNG api is not yet fleshed out enough for you to discover valid contexts programmatically. There is an OSLC Delegated UI which allows a user to select from the available configurations. Take a look at the root services document and the oslc_config:cmServiceProviders property.
Comments
If you are not recomending the use of this API. So how to get the comments for an artifact in RRC. Could you clarify that.
About the Links that you are provided :
The oslc_config:cmServiceProviders Link is not opening up any valid pages.
and the RRC service document doesnot have any oslc_config:cmServiceProviders parameters mentioned in it.
If you are not recomending the use of this API. So how to get the comments for an artifact in RRC. Could you clarify that.
About the Links that you are provided :
and the RRC service document doesnot have any oslc_config:cmServiceProviders parameters mentioned in it.
The oslc_config:cmServiceProviders Link is not opening up any valid pages.