Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

https://servername/rm/discovery/RMCatalog is not available on root service result

 Hi team,


I am working on DNG 7.0.2 SR1. I am referring the document "https://jazz.net/library/article/1197" for OSLC APIs get and POST methods to artifacts ion DNG.
In that, I can able to find the root service output, but as per the instruction in the document I want the below URL
"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.

Thanks

0 votes



2 answers

Permanent link

 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

<oslc_rm:rmServiceProviders rdf:resource="https://elm.example.com:3443/rm/oslc_rm/catalog"/>

You are supposed to use that URI, maybe the service provider catalog had a different URI back 10 years in 2013 for version 4.0, maybe not. The important part is the discovery mechanism.

2 votes

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,


Thanks for your prompt support. 
This is the only URL we get from root services:
https://servername/rm/oslc_rm/catalog and result
 <oslc_disc:ServiceProvider> <dcterms:title>projectname</dcterms:title>
Here when I hit "https://servername/rm/oslc_rm/_Ou6HwCo7EeuYz8KHPSBUuA/services.xml"
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

Thanks

 

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

The whole point of "discovery" is that you discover the actual server URLs to use which are identified by unchanging RDF/xml tags.

FYI there's a discovery walkthough in my answer to this question https://jazz.net/forum/questions/266334/dng-oslcfetch-components-from-project-area

You can follow this using a REST client in a browser - once you get the hang of it then start writing code; IME it's much easier to "debug" manual steps.

Hi Ralph and Ian,

As you said, I am able to get creation factory URLs  and able to get below URL also

"<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>
  <err:detailedMessage rdf:datatype="http://www.w3.org/2001/XMLSchema#string" >com.ibm.rdm.fronting.server.exception.MethodNotAllowedException</err:detailedMessage><err:errorMessage rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
    >Method not allowed</err:errorMessage> <err:errorStatus rdf:datatype="http://www.w3.org/2001/XMLSchema#long"
    >405</err:errorStatus>
    </rdf:Description>"

I have used same headers as you mentioned. Please help

Thanks

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.

You also can not use a creation factory (POST) without providing a valid request body - plus the associated header Content-Type.  

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.

showing 5 of 7 show 2 more comments

Permanent link

 Hi Ralph,


Please check below details I am passing to create artifact in DNG on root folder as I am not mentioning any folder URL.

Method: POST
Headers:
content-type= application/rdf+xml
URL: https://servername/rm/requirementFactory?projectURL=https://servername/jts/process/project-areas/_Ou6HwCo7EeuYz8KHPSBUuA

Request-Body:
 xmlns:oslc_rm="http://open-services.net/ns/rm#"
<rdf:Description rdf:about=""> 
<dc:description rdf:parseType="Literal">OSLC Creation Example</dc:description> 
<dc:title rdf:parseType="Literal">OSLC Created Requirement</dc:title>  
<oslc:instanceShape rdf:resource="serverename/rm/types/OT_6ccbkVpHEeuZWs39_oc7ww"/> 
</rdf:Description>  
</rdf:RDF>  


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>


Please assist , as per the document "https://jazz.net/library/article/1197" I am doing the steps, I can able to get required output as per the document and the things you mentioned above but while posting this is the error.
Thanks

0 votes

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.

Your answer

Register or log in 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.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details

Question asked: Jul 06 '23, 6:49 a.m.

Question was seen: 1,520 times

Last updated: Jul 11 '23, 6:13 a.m.

Related questions
Confirmation Cancel Confirm