Extending RDNG functionalities
To achieve the goal, we need to have development environment as same as IBM provides for RTC extension but unfortunately we couldn’t find much on this.
This would be great if we get any kind of development environment setup guide to proceed with this.
Any help in this regard would be highly appreciated. Thanks
2 answers
As far as I know, RDNG does not ship an SDK. You can not enhance RDNG like you can enhance RTC. I would suggest to create an enhancement request for what extensions you need and one to be able to contribute custom extensions.
Comments
Thanks @Ralph for the quick answer,
Please refer to the following page:
https://jazz.net/wiki/bin/view/Main/DNGReportableRestAPI
In addition, I Googled "ibm.com rdng api" and got several results. Please try searching with the same text."
PMRs will only be accepted for product defects. Neither RQM, nor DOORS Next ever advertized or had planned a Software Development Kit, that would allow customization at a level RTC allows it.
Ways to integrate with DNG that are available:
-
RRC Reportable API - creating custom reports to be run from DNG or RPE, read only.
-
OSLC RM V2 API - the open standard way to programmatically integrate with DOORS Next Generation, there is an elaborate workshop to get you started here OSLC Workshop article. These programs can be from any language that support HTTP REST calls, e.g. Java, C# etc. Hence these are more flexible to run and can read and update DNG data, as part of a web server, or standalone, but have some limitations set by the current OSLC standard, for example module support.
- TRS 2.0 - the OSLC Tracked Resource Set open standard REST API to hook into the stream of low level changes done to resources in the DNG application (and other Jazz apps as well); read only.
- and additionally, there is the so called client extension capability, these are Javascript extension that generally added as widgets you can run from the dashboard, and can be used to view and edit DNG data. It's more tailored to DNG, so has better module support, but is limited to run in a browser/javascript environment.
And then there is the private API of REST services DNG uses internally, but that one isn't documented and supported, usage on your own risk.
Comments
Thanks @Bas, RRC and TRS Apis are just to read the data and OSLC APIs are to read/write on data level.
I thought you could just use the workflow, but then realized that auto-transition is not yet supported.
https://jazz.net/forum/questions/222220/auto-state-triggering-in-rdng-workflow
@Rick
No, don't think that's achievable yet with the OSLC API. You would need to mix the OSLC API with requests to the private DNG API to get there. That will require time to investigate and reverse engineer the API watching the requests that the DNG web UI does.