Using OSLC API for RRC/DOORS Next Generation
![]()
Hi,
I have few questions about API for RRC.
How can I copy an artifact with API?
How can I create an artifact with these formats : simple flow diagram, User Interface Sketch, User Interface Part, Business Process Diagram, Use-Case Diagram etc. I can create artifacts only for text format.
How can I change the access control (Team ownership) of an artifact with API?
Is there any easy way to see xml content link RTC have, like ;
When I open this link I can see the xml content of workitem : https://server:port/jazz/oslc/workitems/97070.xml
Does RRC have the same feature ?
OSLC has only one documentation, and is there any other documentation ? There is one workitem for this subject, created in 2009..
https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/87510 And http://open-services.net/ is closed.. Is there any other website about OSLC ? |
One answer
![]()
Rosa Naranjo (2.9k●1●17●23)
| answered Sep 11 '14, 11:06 a.m.
FORUM MODERATOR / JAZZ DEVELOPER edited Sep 11 '14, 5:46 p.m.
Mustafa
You discuss several topics here and you jump around between RTC and RRC / Doors Next Gen (DNG). I will try to address one at a time. Question #1 - Is it possible to copy an artifact from RTC or RRC/DNG? Yes. OSLC provides creation factories which we discuss in the OSLC workshop, https://jazz.net/library/article/635. Artifacts all have an XML representation that can be retrieved via a GET operation. So, at a high level, I can say that one could save the XML from one artifact and use it to create another similar artifact via the creation factory. Question #2 - Is it possible to create artifacts of other formats? Again, the creation factory and what can be created is discoverable as I think we show in the workshop via something called InstanceShape. If you find the InstanceShape resource for a specific artifact type, then you can ask the creation factory to create an artifact of that type. There is also an OSLC wrapper API called Eclipse Lyo. Have you looked into it? There is one Jazz.net library article I found that has an intro: https://jazz.net/library/article/1382 and Eclipse Lyo 2.1 is now available The same author of article 1382 also authored https://jazz.net/library/article/1197 Question #3: open-services net is not closed. Specification work has moved to OASIS. We’re moving our specification work to OASIS! Question 4: I don't think access control of a RRC/DNG artifact can be modified by API. For RTC, there are some things that can be done via the Plain Java client API. See rsjazz.wordpress.com for many samples and discussion on this API. There is also a Jazz.net Extensions workshop https://jazz.net/library/article/1000 Question 5: I don't follow the question on xml of content link. I also recommend searching the Jazz.net library for oslc articles: https://jazz.net/library/#tag=OSLC or https://jazz.net/library/#tag=oslc Comments ![]() FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Note that as of 5.0, RRC and DNG is the same thing (the underlying technology of RRC and DNG was always the same, and now there is just a single product ... DNG).
Hi Rosa, thanks for your answers. #Q1 - I saw your comment yesterday on this workitem : https://jazz.net/jazz03/web/projects/Requirements%20Management#action=com.ibm.team.workitem.viewWorkItem&id=77688 this can be the way of copy an artifact. #Q2 - I will do some research about InstanceShape, thanks. And you suggested Lyo. For example, now I can't add internal links (copy to/copy from, linked to/linked from etc.) to an artifact with OSLC. OSLC supports only "Validated By, Implemented By, Tracked by and Affected By" link types. So I can't do the same operation with Lyo, right? Because it based on OSLC, if OSLC can't do, Lyo can't too. That's why I asked for more documentation for OSLC.
#Q3 - Thank you for information. #Q4 - I am planning to open an RFE for this case too. If I can do some operation for RTC, then I should be able to do same thing for RRC/DNG or RQM too. Am I wrong ?
![]() FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
WRT Q4, you cannot in general assume that anything you can do for RTC, you can do for DNG and RQM, but you certainly can request an enhancement request for that functionality.
@gmclemm I created RFE for Q4. Still waiting answer for Q5 and Q2 ![]() FORUM MODERATOR / JAZZ DEVELOPER
You will have to clarify or elaborate more since I didn't understand what you wanted with Q5 on XLM content link. On Q2, did you mean, if you cannot use OSLC to add internal links then what other API is there? If so, I would suggest looking in this blog http://rsjazz.wordpress.com for information on using the Plain Java Client API library:
@rnaranjo for Q2, yes. I have also looked for that. https://jazz.net/library/article/1197 here, in the comments
- Note that internal links can not be modified, added or removed via OSLC. The - request will not fail nor give any hint that this are not supported; the unmodifiable elements are just ignored and you still get a 200 OK response.
Only OSLC links are supported.
- OSLC can be used to create links defined in the OSLC Spec ( http://open-services.net/bin/view/Main/RmSpecificationV2 )
Custom links like : Parent, Child, Link To, Link From can not be created using OSLC
So , I can't move forward as I want.
@rnaranjo for Q2, yes. I have also looked for that. https://jazz.net/library/article/1197 here, in the comments
- Note that internal links can not be modified, added or removed via OSLC. The - request will not fail nor give any hint that this are not supported; the unmodifiable elements are just ignored and you still get a 200 OK response.
Only OSLC links are supported.
- OSLC can be used to create links defined in the OSLC Spec ( http://open-services.net/bin/view/Main/RmSpecificationV2 )
Custom links like : Parent, Child, Link To, Link From can not be created using OSLC
So , I can't move forward as I want.
showing 5 of 7
show 2 more comments
|
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.