It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Follow this question
Question details

×5,819

question asked: Jul 06 '17, 3:40 a.m.
question was seen: 1,543 times
last updated: Dec 16 '21, 12:32 a.m.

Related questions

FAQ - How this Forum works

how to get list of streams and artifacts in RM Project area using OSLC?

0
Asha Faldu (11●10) | asked Jul 06 '17, 3:40 a.m.
Hello All,

For Example I have a RM Project JKE Banking(Requirement Management)  and 2 streams in this Project Area

1. JKE Banking(Requirement Management) Initial Stream
2.  JKE Banking(Requirement Management) Final Stream
and there is 3 artifacts in JKE Banking(Requirement Management) Final Stream. I need to access this 3 artifacts using OSLC API.

I am using OSLC Version 2.0

Is it possible to get this information using OSLC API?

Please Help.

3 answers

Most liked answers|Newest answers|Oldest answers ↑

0
permanent link
Bartosz Chrabski (3.4k●1●27●49) | answered Aug 25 '21, 10:49 a.m.

 Hi Asha,


Request URL:

https://server/rm/cm/component/_ft0CYJtZEeu1Bb7mvc1TIQ/configurations

Parameters:

<component identifier> - _ft0CYJtZEeu1Bb7mvc1TIQ

Method: GET

Headings:

·       Accept - application/xml <o:p> </o:p>

·       Content-Type - application/xml <o:p> </o:p>

·       OSLC-Core-Version – 2.0 <o:p> </o:p>

· 

0
permanent link
Ian Barnard (1.9k●6●13) | answered Aug 25 '21, 12:45 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

The 'proper' way to do this is through discovery (without hardcoding further URLs) start from /rm/rootservices, following a chain of urls on specific rdf tags, on the basis that even if the rm implementation changes those rdf tags won't change and if you do the discovery properly it will continue to work as DOORS Next develops.


There's an example of this discovery from rootservices to components/configurations in my answer here: https://jazz.net/forum/questions/266334/dng-oslcfetch-components-from-project-area

Comments
1
Bartosz Chrabski commented Aug 25 '21, 12:53 p.m.

Ian,


No one was sugesting hardcoding urls. You should get list of components and project first.

0
permanent link
John Martelli (11●1) | answered Aug 27 '21, 12:38 a.m.
edited Aug 27 '21, 11:43 p.m.
 The 'proper' way to do this is through discovery (without hardcoding further URLs) start from /rm/rootservices, following a chain of urls on specific rdf tags, on the basis that even if the rm implementation changes those rdf tags won't change and if you do the discovery properly it will continue to work as DOORS Next develops.

There's an example of this discovery from rootservices to components/configurations in my answer here: https://jazz.net/forum/questions/266334/dng-oslcfetch-components-from-project-area
My Balance Now

Hello,

Thanks for the update and quick reply. I'll be sure to keep an eye on this thread. Looking for the same issue. 

Your answer

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