It's all about the answers!

Ask a question

DNG 7.0.2 doesn't report modules without "MD" prefix


Mazen Sadek (111) | asked Feb 24 '21, 5:13 p.m.
edited Feb 24 '21, 5:13 p.m.
I've an integration with DNG using REST APIs and I recently upgraded the server from 6.0.6 server to 7.0.2.
I get the module URIs with no prefix, however on the server itself it has "MD" prefix

These are the APIs that I use, 
  1. https://<server>:<port>/rm/publish/modules?moduleURI=_rSjy0doOEemYiLSc2gGwzQ
  2. https://<server>:<port>/rm/publish/resources?moduleURI=_rSjy0doOEemYiLSc2gGwzQ
The first one works but the second gives bad request:
com.ibm.rdm.fronting.server.exception.InternalServerErrorException: Propagated exception; original message [IllegalArgumentException: Storage service must not be supplied with a null configuration]

The second API works properly if I add the prefix "MD" like the following:
  1. https://<server>:<port>/rm/publish/resources?moduleURI=MD_rSjy0doOEemYiLSc2gGwzQ
Please note that this isn't the case when modules are filtered by local configuration (i.e. using vvc.configuration parameter) Also, the prefix isn't needed with Collections as well, so the 2 API would works fine (moduleURI= is replaced by collectionURI). It would also work fine if I added the prefix "CO"


Any help or indication about what I'm doing wrong?

One answer



permanent link
Subramanya Prasad Pilar (4.5k14) | answered Feb 25 '21, 12:01 a.m.

Share Link To Artifact is not showing the correct artifact ID after upgrading DNG. There is a defect created and you can find details in the following WorkItem:

For the time being, you can prefix MD to the UUID (as workaround).


Comments
Mazen Sadek commented Feb 25 '21, 5:10 a.m.

Thank you for reply, but the workItem is marked resolved with "Works as designed" because it's related to the shared UUID. As per the last comment, it's a problem with the REST API itself.


Do you have any idea about another defect regarding the API or should I just add another comment in the defect you provided?

I'm doing the workaround you mentioned for now, but I'm still supporting 6.0.6, so it's a bit annoying to check for the version and add the prefix instead of doing 2 api requests.

Your answer


Register or to post your answer.