https://servername/rm/discovery/RMCatalog is not available on root service result
Hi team,
"https://servername/rm/discovery/RMCatalog", but under "<oslc_rm:rmServiceProviders" tag I am only get URL
"https://servername/rm/oslc_rm/catalog"
can anyone assist me , why I am not getting RMcatalog, and how can I able to get it.
2 answers
I confirmed for myself that you can find the tag oslc_rm:rmServiceProviders in the rootservices and the selected resource is as you point out
Comments
Note, before you ask for the other links, I am pretty sure the paths with discovery do not exist any more, use the paths you get from the documents you retrieve.
Hi Ralph,
https://servername/rm/oslc_rm/catalog and result
I am not able to get any creation factory URL which will be base for creating all further PUT and POST methods mentioned in the document.
Can you please assist
I did a GET on the project area service provider as mentioned above, being authenticated and passing along the required OSLC header OSLC-Core-Version 2.0 and Accept application/rdf+xml and I was able to find the factory URIs along with all the other expected URIs.
1 vote
Hi Ralph and Ian,
"<oslc:creation rdf:resource="https://grarrc.ibm.com:9443/rm/requirementFactory?projectURL=https://grarrc.ibm.com:9443/jts/process/projectareas/_zpWqELrZEeG3OKR6fZ1svQ" />
According to the document when I hit this URL to get the data, I am getting below error,
"<rdf:Description>
I have used same headers as you mentioned. Please help
You always avoid providing the essential information in a consumable way e.g. the method, this discourages responding.
You can not GET a factory URI.
Finally, you can and must GET a resourceShape, to find out the properties needed to create a resource. The resource shape can be found in the same information that contains the factories.
Hi Ralph,
Method: POST
Headers:
content-type= application/rdf+xml
URL: https://servername/rm/requirementFactory?projectURL=https://servername/jts/process/project-areas/_Ou6HwCo7EeuYz8KHPSBUuA
Error: <html><head><title>Error 400: Bad Request</title></head><body><h1>Error 400: Bad Request</h1><p>getProjectTypesystem called with no parameters<hr><i>Requirements Management/7.0.2 SR1</i></p></body></html>
Comments
Missing OSLC-Core-Version header.
After adding also it is not working giving same error.
If you are creating a requirement in a DN project area that has opted-in for configuration management, you must also include either a
Configuration-Context
header or
oslc_config.context
parameter in your request.
Also, your requirement doesn't specify which component it should belong to. I suggest you look at the RDF of an existing requirement and the resource shape referenced by the creation factory to determine what data must be specified to create a new one.