Design Manager and OSLC Config Context with GC
Hi,
when accessing DM via local config, query is working. The same query with global config (which exists and is set up correctly) does not work.
There is something wrong on our side or is it simple not working with GC?
Works: https://myserver/dm6/reporting/rhapsody/uml/UseCaseDiagram?id=https://myserver/dm6/models/_kkl6QFaJEey3bftBoEUiOQ~GUIDabaec89a-2268-4cc5-a536-ce160c987598&oslc_config.context=https://myserver/dm6/cm/stream/_ktOR0FaJEey3bftBoEUiOQ
Does not work (404): https://myserver/dm6/reporting/rhapsody/uml/UseCaseDiagram?id=https://myserver/dm6/models/_kkl6QFaJEey3bftBoEUiOQ~GUIDabaec89a-2268-4cc5-a536-ce160c987598&oslc_config.context=https://myserver/gc6/configuration/2
2 answers
Design Manager project areas use concepts such as streams and baselines (both known as configurations to allow the development of models to branch, with different versions of the same model element known generically as an artifact existing within different streams of the same project area. This is referred to by the Jazz applications as Configuration Management.
Comments
Subramanya Prasad Pilar
Dec 17 '21, 2:53 a.m.What if you use local configuration context instead of GC context? Probably this is an issue with the DM API when GC context is used.
Thomas Noack
Dec 20 '21, 6:40 a.m.Hi. Local config just works as expected. Only GC seems to be a problem.