Great, is seems like Jazz successfully uses the OSLC Selection Dialog feature of your OSLC server.
Now, my suspicion is that Jazz is refusing to store the xyz link (due to oslc-specs/notes/linking-profiles/link-profiles.md at master · oslc-op/oslc-specs · GitHub) on its resource A towards your resource B on your AM server and is trying to “force” your OSLC server to “take it”. It should do so by making a POST request to your server, trying to modify the resource B you want to link to from a Jazz resource A to store an inverse link (B)-[xyzBy]->(A).
You now need to verify that Jazz attempts to make such a request. Your options:
use GoReplay to capture Doors NG payloads to RefImpl AM
use Wireshark to see that Doors NG (backend) as much as tries to make an HTTP request to RefImpl AM
The POST request happens on the backend, you won’t see it in the browser. The one you see I think is the GET request via the Jazz proxy?
P.S. You may also want to put some of the Jazz Wiki (password-protected in some cases) into your LLM context, e.g. DeploymentIntegrating < Deployment < TWiki To be fair, the information there is fairly scattered and inconsistent.
I have enabled ‘trace’ logging at highest/default level on AM server + removed or set to trace all other level settings.
After selecting an item to link to,
in the AM logs I see this:
server-am-1 | [TRACE] JenaModelHelper - createJenaModel - Execution Duration: 2 ms
server-am-1 | [TRACE] AbstractOslcRdfXmlProvider - Using 'RDF/XML' writer for 'application/rdf+xml' Accept media type
server-am-1 | [TRACE] JenaModelHelper - createJenaModel - Execution Duration: 2 ms
server-am-1 | [TRACE] AbstractOslcRdfXmlProvider - writeObjectsTo - Execution Duration: 5 ms
in the RM server logs I only see this occuring: ERROR m.ibm.rdm.fronting.server.services.RMBridgeService - Service Error: Unable to resolve expected configuration.
niether of which indicates that any request is sent from RM-tool to the AM server after I click ‘OK’.
I will see if I can try and track it down with one of the other methods, i.e. wireshark!
It looks like you are somehow triggering RDF deserialization, might be worth putting goreplay in front of the AM server or run it in the IDE with a debugger to see which controller methods get hit with what payloads.