Using REST API for RDNG
![]()
Hi,
I am trying to change an attribute of a requirement. I copied XML from firebug but it still gives me the error "Error 403: Forbidden CRRRS6401E Error parsing content. Content must be valid rdf+xml." I am trying this with CLM version 6.0.1. Operation = PUT URL = "https://server:9443/rm/resources/_32c08e5bd98b4275b4cc47a860407868" HEADERS X-Jazz-CSRF-Prevent = 0000TD823zabfG0TvMoZcH_TNOO:38137356-3ab9-434b-bccd-0d4f2a791cf4 If-Match = %220%22&%22_5ev5L8qAEeWw7MAd8gfbhw%22 Content-Type = application/rdf+xml <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:rm="http://www.ibm.com/xmlns/rdm/rdf/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:dcterms="http://purl.org/dc/terms/" xmlns:jfs="http://jazz.net/xmlns/foundation/1.0/" xmlns:xs="http://www.w3.org/2001/XMLSchema#" xmlns:h="http://www.w3.org/TR/REC-html40"><rm:Artifact rdf:about=""><rm:hasAttrVal rdf:parseType="Resource"><rdf:value rdf:resource="https://server:9443/rm/types/_KdkscMmqEeWt-5UMFpH9Aw#dd84ed1c-9786-469b-85a2-517388d6a09b"></rdf:value><rm:hasAttrDef rdf:resource="https://server:9443/rm/types/_K6D0IcmqEeWt-5UMFpH9Aw"></rm:hasAttrDef></rm:hasAttrVal><rm:hasAttrVal rdf:parseType="Resource"><rdf:value></rdf:value><rm:hasAttrDef rdf:resource="https://server:9443/rm/types/_lR2cscmpEeWt-5UMFpH9Aw"></rm:hasAttrDef></rm:hasAttrVal><rm:hasAttrVal rdf:parseType="Resource"><rdf:value rdf:resource="https://server:9443/rm/types/_j2stUcmpEeWt-5UMFpH9Aw#Text"></rdf:value><rm:hasAttrDef rdf:resource="https://server:9443/rm/types/_lHLdwcmpEeWt-5UMFpH9Aw"></rm:hasAttrDef></rm:hasAttrVal><rm:hasAttrVal rdf:parseType="Resource"><rdf:value rdf:resource="https://server:9443/rm/types/_KktPMcmqEeWt-5UMFpH9Aw#8fb41825-9399-4e68-8977-290dad5f8cb9"></rdf:value><rm:hasAttrDef rdf:resource="https://server:9443/rm/types/_K8TP0cmqEeWt-5UMFpH9Aw"></rm:hasAttrDef></rm:hasAttrVal><rm:hasAttrVal rdf:parseType="Resource"><rdf:value rdf:resource="https://server:9443/rm/types/_KRuo0cmqEeWt-5UMFpH9Aw#3816089d-8455-4d2d-8926-a03ad89a6191"></rdf:value><rm:hasAttrDef rdf:resource="https://server:9443/rm/types/_LjUzkcmqEeWt-5UMFpH9Aw"></rm:hasAttrDef></rm:hasAttrVal><rm:hasAttrVal rdf:parseType="Resource"><rdf:value rdf:datatype="http://www.w3.org/2001/XMLSchema#string">123abc123_xy</rdf:value><rm:hasAttrDef rdf:resource="https://server:9443/rm/types/_StObMcm6EeWw7MAd8gfbhw"></rm:hasAttrDef></rm:hasAttrVal><rm:hasAttrVal rdf:parseType="Resource"><rdf:value rdf:resource="https://server:9443/rm/types/_KF-EwcmqEeWt-5UMFpH9Aw#4629eb0b-487a-4d25-80aa-845e5c48a493"></rdf:value><rm:hasAttrDef rdf:resource="https://server:9443/rm/types/_LNJIMcmqEeWt-5UMFpH9Aw"></rm:hasAttrDef></rm:hasAttrVal><rm:hasAttrVal rdf:parseType="Resource"><rdf:value rdf:parseType="Literal"><div xmlns="http://www.w3.org/1999/xhtml"><h1 id="_1275486053222" dir="ltr">Requirement: Organizations can Apply</h1><h2 id="_1275486053223" dir="ltr">Brief Description</h2><p id="_1275486053184" dir="ltr">Organizations must have the ability to apply for assistance as needed whether a result of a catastrophic event or from some other justification.</p><h2 id="_1275486053224" dir="ltr">Applicable Roles</h2><ul dir="ltr"><li id="_1275486053205"><h3 id="_1275486053228">Primary</h3></li></ul><blockquote dir="ltr"><p id="_1275486053185">The primary role for this event is the<a id="_1298420848514" href="https://server:9443/rm/resources/_29729cc2784c4e268666dbcceccdf009">Beneficiary</a></p></blockquote><ul dir="ltr"><li id="_1275486053206"><h3 id="_1275486053229">Secondary</h3></li></ul><blockquote dir="ltr"><p id="_1275486053186">The secondary role for this event is the<a id="_1298420855022" href="https://server:9443/rm/resources/_1901d5bbd9d34f9f973acf134425d6b6">Back office administrator</a></p></blockquote><h2 id="_1275486053225" dir="ltr">Key Scenarios</h2><ol dir="ltr"><li id="_1275486053207"><p id="_1275486053187"><a id="_1291186412169" href="https://server:9443/rm/resources/_71ff75b59eb44718854cc25e7721164e">Organizations may apply with an initial request</a>using the following request methods:</p><ol><li id="_1275486053208"><p id="_1275486053188">Written request: Email and or letter</p></li><li id="_1275486053209"><p id="_1275486053189">Verbal request: In person or via phone</p></li><li id="_1275486053210"><p id="_1275486053190">Website request: Provide request via Dividends for Cause Website</p></li></ol></li><li id="_1275486053211"><p id="_1275486053191"><a id="_1291186412170" href="https://server:9443/rm/resources/_e4b5abe3fd97407e9ab2394e3424bb34">Organization must provide justification for funds</a></p></li><li id="_1275486053212"><p id="_1275486053192"><a id="_1291186412171" href="https://server:9443/rm/resources/_f36b03d80d5c4e218ce74c98622e7761">Organization must identify how much money is desired</a></p></li><li id="_1275486053213"><p id="_1275486053193">JKE<a id="_1298420869268" href="https://server:9443/rm/resources/_a718ca25a4c84f1d8cc129a24920f422">Charity Coordinator</a>will review and validate request</p></li><li id="_1275486053214"><p id="_1275486053194"><a id="_1291186412172" href="https://server:9443/rm/resources/_aa2f6bdd0ff1488088cf2fb257ca5b14">Charity Coordinator response will trigger email notification</a></p></li><li id="_1275486053215"><p id="_1275486053195">JKE Charity Coordinator will work with JKE Legal team to follow legal procedures required to add Organization to "Dividend for a Cause" website.</p></li><li id="_1275486053216"><p id="_1275486053196">JKE Charity Coordinator will ensure Back office Administrator adds the new Organizations to the Dividends for a Cause website.</p></li></ol><h2 id="_1275486053226" dir="ltr">Related Features</h2><h3 id="_1275486053230" dir="ltr">Business Rules</h3><ol dir="ltr"><li id="_1275486053217"><p id="_1275486053197"><a id="_1291186412173" href="https://server:9443/rm/resources/_717b46ae627f47da8e623600a6fe8b1c">Charity Coordinator Response - Initial Request</a></p></li><li id="_1275486053218"><p id="_1275486053198"><a id="_1291186412174" href="https://server:9443/rm/resources/_f7ca545b02c84e47ada4dec327b3c91a">Organization response requirement</a></p><ol><li id="_1275486053219"><p id="_1275486053199"><a id="_1291186412175" href="https://server:9443/rm/resources/_3a8136efb0c248e78d39d433b1e00736">Organization No Response</a></p></li></ol></li><li id="_1275486053220"><p id="_1275486053200"><a id="_1291186412176" href="https://server:9443/rm/resources/_de7980c3181e4fbf838a18a363b6da6c">Organization does not meet charity criteria</a></p></li><li id="_1275486053221"><p id="_1275486053201"><span class="markedForLink">Organization falsifies information</span></p></li></ol><h2 id="_1275486053227" dir="ltr"><span>Additional Information</span></h2><p id="_1275486053202" dir="ltr"><span style="color:rgb(26, 26, 26)"><i><<Include, or provide references to, any additional information required to clarify/elaborate this requirement. this could include sketches, storyboards, screenflows, high level process flow and examples or any thing else you fancy.>></i></span></p></div></rdf:value><rm:hasAttrDef rdf:resource="https://server:9443/rm/types/_lScSkcmpEeWt-5UMFpH9Aw"></rm:hasAttrDef></rm:hasAttrVal><rm:hasAttrVal rdf:parseType="Resource"><rdf:value>Organizations can apply</rdf:value><rm:hasAttrDef rdf:resource="https://server:9443/rm/types/_lT0LkcmpEeWt-5UMFpH9Aw"></rm:hasAttrDef></rm:hasAttrVal><rm:hasAttrVal rdf:parseType="Resource"><rdf:value rdf:resource="https://server:9443/rm/types/_KF-EwcmqEeWt-5UMFpH9Aw#99f14384-948b-4c7c-8c63-59d56cfe92a1"></rdf:value><rm:hasAttrDef rdf:resource="https://server:9443/rm/types/_LaLeocmqEeWt-5UMFpH9Aw"></rm:hasAttrDef></rm:hasAttrVal><rm:ofType rdf:resource="https://server:9443/rm/types/_OPxywcmqEeWt-5UMFpH9Aw"></rm:ofType><rm:processArea rdf:resource="https://server:9443/rm/process/project-areas/_i3_pYMmpEeWt-5UMFpH9Aw"></rm:processArea></rm:Artifact></rdf:RDF> |
Accepted answer
![]()
Hi, I suggest to use OSLC specification when making request to RDNG, following article describes how to make request to RDNG OSLC service provider:
https://jazz.net/library/article/1197 Kurtulus YILDIRIM selected this answer as the correct answer
Comments Hi Gabriel,
1
Starting from the rootservices document, the oslc consumer can find the right URI's to discover the data: For instance the catalog is :
|
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.