Implementing Global Configuration using doors next
I am currently working in a tool that uses RM configuration to copy and combine streams. The URL
requestManager.webSite + "/rm/oslc_rm/" + requestManager.projectArea + "/services.xml"
is used to discover the root folder for RM. Similarly, I need to implement global configuration. Please assist me in implementing global configuration in this.
One answer
Do you mean: how do I find the root folder in an RM component when using global configurations?
The root folder URL, and the entire content of services.xml, is the same whether using local or global configurations, but instead of providing the local configuration URL in query parameter oslc_config.context or header Configuration-Context, you provide the GC url.
Comments
Thanks for sharing this.
BTW you should use discovery starting from rootservices to find the services.xml and avoid constructing URLs by concatenating strings, because that's fragile if we change internal implementation across versions. Example of discovery here
| https://jazz.net/forum/questions/266334/dng-oslcfetch-components-from-project-area |