For Gabriel Ruelas, how to make RM LinkService send OSLC Query for Links to Peer Providers?
Gabriel,
Supposedly, when associated with a peer AM Service Provider that is GC-compatible and which claims to support Link Discovery via OSLC Query, DNG is supposed to issue an OSLC Query to the Query Capability of that ServiceProvider to ask the AM ServiceProvider for any Links that reference the current DNG Requirement.
For example, the query is supposed to resemble:
oslc.where=jazz_dm:trace IN [ <https://clm.server.com/rm/resources/abcde12345 > ]
However, despite all attempts to assure that the ServiceProvider's properties are nearly identical to DM's, we cannot get the RM LinkService to issue any such OSLC Query following the HTTP PUTs of the modified AM Resources back to the AM ServiceProvider.
Can you confirm that DNG does indeed use OSLC Queries for getting /rm/links?sourceOrTarget when associated with an AM ServiceProvider? If so, do you know of any additional checks that DNG makes which would lead it to decide not to request such queries?
|
2 answers
|
With the note that the OSLC Query which goes out from DNG looks like:
This is a much more complex request to optimize and to process on the backend.
However, yes, the primary outage was that the ServiceProvider resource has to go back to DNG as abbreviated RDF+XML and the Content-Type header has to be application/rdf+xml. Any deviation and DNG, during the Linking step, cannot process the ServiceProvider response.
In Lyo, there is a System Property that can be set to force this serialization.
|
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.