How to retrieve the components of a global configuration from outside Jazz
Accepted answer
Christoph,
APIs for global configuration management are summarized at https://jazz.net/wiki/bin/view/Main/GlobalConfigurationManagement . That page also contains other important information to consider when integrating with global configuration management.
There is no single API to find at one call all the recursive component configurations in a given global configuration. However, you can find the component of a contribution to a global configuration by looking at its oslc_config:component property, and you can find all the direct contributions to a global configuration by looking at the oslc_config:configuration property on the parent configuration's oslc_config:contribution properties.
You can find the component properties of all the direct contributions to a single global configuration using OSLC query, but you still need to recurse through nested contributions to find all the components in the GC hierarchy. There are examples of using OSLC queries for global configurations and components on the GC REST API page at https://jazz.net/gc/doc/scenarios .
The OSLC specs can be found at https://open-services.net/specifications/ , but the Configuration Management spec link on that page is currently broken, so use a direct link to the version-controlled copy as an interim measure: https://raw.githack.com/oasis-tcs/oslc-core/master/specs/config/oslc-config-mgt.html .
Nick.
Comments
UPDATE: I wrote "There is no single API to find at one call all the recursive component configurations in a given global configuration."
In the milestone M4 of 7.0.2 on jazz.net, we've introduced a new API to get the recursive contributions; see https://jazz.net/gc/doc/scenario?id=GetFlatListOfContributionsForGcHiearchy .
1 vote
Hi Nick,
All the links in your answer yield a 404 not found. Are there updated urls for this information.
For some reason, some browsers are treating the period as part of the URL ... so I edited Nick's answer to put a space between the URL and the following period, and they seem to be working now.