how to obtain the oslc url of a DNG artifact
I have 3 artifacts in a project, in DOORSNG version 6.0.5, under a folder.
No modules in the project, yet I also have a collection which includes them.
Working with the OSLC API, I am going from the rm/rootservices, to the rm/oslc_rm/catalog, but I cannot find where next to inquire for these artifacts.
Thanks.
Here is the services RDF I got. Sorry it is not quoted
I used my browser to get it: https://shani.net:9443/rm/oslc_rm/_VCaiEExSEeym6YphhHScpA/services.xml
So - no special headers specified. The results were saved to a file for further work.
<oslc_rm:ServiceDescriptor xmlns:oslc_rm="http://open-services.net/xmlns/rm/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" rdf:about="https://shani.net:9443/rm/oslc_rm/_VCaiEExSEeym6YphhHScpA/services.xml">
<oslc_rm:links>
<oslc_rm:LinkCreationServices>
<oslc_rm:validatedByLinkFactory rdf:resource="https://shani.net:9443/rm/links/oslc/validatedByLinks"/>
<oslc_rm:implementedByLinkFactory rdf:resource="https://shani.net:9443/rm/links/oslc/implementedByLinks"/>
</oslc_rm:LinkCreationServices>
</oslc_rm:links>
<oslc_rm:collections>
<oslc_rm:CollectionSelectionDialog>
<oslc_rm:heightHint>550px</oslc_rm:heightHint>
<oslc_rm:widthHint>800px</oslc_rm:widthHint>
<oslc_rm:widget rdf:resource="https://shani.net:9443/rm/pickers/com.ibm.rdm.web.CollectionPicker?projectURL=https%3A%2F%2Fshani.net%3A9443%2Frm%2Frm-projects%2F_VCaiEExSEeym6YphhHScpA"/>
<dc:title xmlns:dc="http://purl.org/dc/terms/">Collection Selection</dc:title>
</oslc_rm:CollectionSelectionDialog>
</oslc_rm:collections>
<oslc_rm:requirements>
<oslc_rm:SelectionDialog>
<oslc_rm:heightHint>550px</oslc_rm:heightHint>
<oslc_rm:widthHint>800px</oslc_rm:widthHint>
<oslc_rm:widget rdf:resource="https://shani.net:9443/rm/pickers/com.ibm.rdm.web.RRCPicker?projectURL=https%3A%2F%2Fshani.net%3A9443%2Frm%2Frm-projects%2F_VCaiEExSEeym6YphhHScpA"/>
<dc:title xmlns:dc="http://purl.org/dc/terms/">Requirement Selection</dc:title>
</oslc_rm:SelectionDialog>
</oslc_rm:requirements>
<dc:description xmlns:dc="http://purl.org/dc/terms/">Service Descriptor for Project: OSLC with OPCloud (Requirements)</dc:description>
<dc:title xmlns:dc="http://purl.org/dc/terms/">OSLC with OPCloud (Requirements)</dc:title>
</oslc_rm:ServiceDescriptor>
|
3 answers
David Honey (1.8k●1●7)
| answered Nov 29 '21, 4:56 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER Look for service providers -> services -> queryCapabilities.
Comments I indeed tried that sequence. I obtained the services report by following rootservices -> catalog -> services, but there is no query capability in there.
I have several artifacts, some are collected into a collection, and two of them are also in one module.
The widgets in the services RDF data indeed work, but these are not the OSLC URLs that I need.
I will post my services RDF to this topic.
|
Ian Barnard (2.0k●6●13)
| answered Nov 29 '21, 9:01 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER Hi
See my answer here for a detailed example of discovering configurations and components, including query capabilities https://jazz.net/forum/questions/266334/dng-oslcfetch-components-from-project-area/266667 - that was for 6.0.6.1
DOORS Next 7.0.2 now has four project-specific query capabilities, older versions don't have reqif and view queries:
If you simply use the relevant query base URL, with the configuration, you'll get results for all the resources - be wary that this query is an expensive operation so you should try to make it more focussed to minimise the server load.
HTH
Ian
Comments Hi Ian,
I saw a youtube made by Ian back in 2015... Is that you? anyway, the Ian in that demo used to work with me on an EU7 project back than. I indeed wonder if that is you.
Nope. Thanks Ian. I looked up the detailed answer you referred me to and it will take me some time to follow up. AFAI see, my responses still do not provide a query capability yet. But I will keep trying before giving up. |
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.