It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Follow this question
Question details

×5,999

question asked: May 16 '22, 6:01 a.m.
question was seen: 479 times
last updated: May 17 '22, 1:49 p.m.

Related questions

FAQ - How this Forum works

Problem following links from DM

0
Björn Bartels (11●1) | asked May 16 '22, 6:01 a.m.
Hi,

in a current project I need to to follow links from DM elements to QM and CCM.

While this works for local configs using

https://<server:port>/dm/reporting/collaboration/Link?referencingId=https://<server:port>/dm/models/<resourceID>&rmps.context=https://<server:port>/dm/cm/stream/<streamID>

I can not get the same links when providing global configs either directly as the rmps.context or by appending the oslc.context.

Thanks for any hints...

3 answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
David Honey (1.8k●1●7) | answered May 16 '22, 8:10 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
As described in https://docs.oasis-open-projects.org/oslc-op/config/v1.0/psd01/config-resources.html#configcontext, OSLC supports two ways of specifying the configuration context:
  1. A oslc_config.context parameter. 
  2. A Configuration-Context header.
I'm not aware of any oslc.context parameter. It's not part of the OSLC Configuration Management specification.
Comments
Björn Bartels commented May 16 '22, 8:26 a.m.

Thank you David, you are totally right. I wanted to refer to the oslc_config.context parameter. I am not able to retrieve the DM links when using it with the collaboration/Link service.

David Honey commented May 16 '22, 8:34 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

Are using the correct parameter value?
From the spec:

Syntax of the query string for configuration context: 

?oslc_config.context=uri_ref_esc


</pre>

The uri_ref_esc is an angle bracket-delimited URI reference in which > and \ are -escaped, as defined in [OSLCCore3].

For example, if you want to use a configuration context of https://localhost:9443/gc/configuration/123 , then the unencoded parameter value would be <https://localhost:9443/gc/configuration/123> (note the angle brackets enclosing the URI) and the URL encoded parameter value would be %3Chttps%3A%2F%2Flocalhost%3A9443%2Fgc%2Fconfiguration%2F123%3E .

Björn Bartels commented May 16 '22, 7:33 p.m. | edited May 16 '22, 7:35 p.m.
Thanks again for your detailed answer David. I have now tried all possible combinations based on your answer:

- appending oslc_config.context=global_conf using ? and & with or without <>, encoded not encoded but with no success

When I look at the DM element in the webinterface (with the desired global_conf https%3A%2F%2Fserver%2Fgc6%2Fconfiguration%2F2 enabled), all QM, RM and CCM links are there. The URL has the following form:


Am I getting something totally wrong here ?


0
permanent link
David Honey (1.8k●1●7) | answered May 16 '22, 11:40 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

This may be something that DM doesn't support. The use of the oslc_config.context parameter is required to be supported for a GET of a concept resource. However, the URI you are using seems to be a web browsing URL, not the URI of an artifact itself. Whether an application supports that is not defined by OSLC.

0
permanent link
Björn Bartels (11●1) | answered May 17 '22, 1:48 p.m.
edited May 17 '22, 1:49 p.m.

Hi David, thanks again for all your help! I was able to figure out the correct parameters for my reporting query by looking at the webinterface of DM. I had to drop &rmps.context and instead use &projectId= and &oslc_config.context= to make it work! The query leads to the different artifacts linked to from a DM element.


Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.