How to update DOORS requirements using REST/OSLC API ?
4 answers
if you want to update DOORS requirement via OSLC API, then you're probably encounter with the authentication issue. The DOORS/DWA OAuth is kindof different than other jazz based product, you may need to contact DOORS developers for details
Comments
Hi Prasun,
The codes for update the link is align with OSLC RM specification, if you want to update the Requirement with validateBy link, you need to first get the requirement, then add the validateBy property to the requirement and then make an update call. The logic is straight forward, but as Chong Yuan mentioned above, before running into this logic, you need to first write a client to pass the OAuth, which might take some additional effort.
If you don't need to stick to the RQM 4.0, the recommendation here is upgrade to 4.0.1 (not release yet, but RC builds are aviable now, you can have a try) and use the new repair link feature mentioned by Bing Dong, by using it you are able to detect and repair the missing links in RQM UI.
Hope this helps,
Scarlett
Comments
Any source code example please ? / can you tell me what is the resource URI for requirement in DOORS?
I don't see an option to attach any files here, to provide any XML file sample. Resource URI for requirement is the URL of the object itself. For example -
Can we use mozilla poster for getting XML data of the requirements using this URL ?..
I tried using poster, but there was an error. please suggest.
I use RESTClient. Haven't tried poster for this.
Yea I have configured DWA also.. I did not get OAuth.. I simply using this URL to get XML of the requirement. I am still not sure whether poster can be used or not..
The error is 401 Unauthorised
https://MyHost:8445/dwa/rm/discovery/service/urn:rational:ers-4fd997ed38995647:4fd997ed38995647-O-1-00000022
I am able to authenticate using OAuth and have an authorized access_token, but now the problem I am facing is that when I try to do a GET on the Requirements URL https://DOORSServer:8445/dwa/rm/urn:rational::1-4ffe24e04da657d1-O-2-00000020
Can't see anything obviously wrong..
Prasun, have you gotten past this? If not, I recommend you to raise a PMR wiht Support, since this will need to be investigated in a structured way. Support can possibly have a remote session with you to identify the problem.