...
Flow Step | Short description | Message Details | Notes | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Bulk Get Request |
| Define new get operation "getResourceDataForCmHandles" into ncmp.yml | |||||||||||
2 | Ack Client Request |
| ||||||||||||
3 | DMI Bulk Request |
| The DMI PLugin should be told (included in request) the client topic so that NCMP does not have to 'remember' to relation between request id and client topic! | |||||||||||
4 | Ack Client Request |
| ||||||||||||
5 | Kafka Messages from DMI to NCMP |
| ||||||||||||
6 | Kafka Message(s) from NCMP to Client Table |
| ||||||||||||
7 | Alternative for 4/5 → Non responding DMI. NCMP will have to create error message detailing cm-handles | See decision # 8 and 9 | ||||||||||||
8 | Response message structure ? (Flow no. 5) Non responding DMI- pluginplugin |
| ||||||||||||
9 | Response message structure ? (Flow no. 5) Non existing cm handles |
| TBD |
| ||||||||||
109 | URL pattern for DMI-Plugin bulk endpoints | Existing DMI endpoints are : /v1/ch/{cmHandle}/data/ds/{datastore-name} datastore-name:
...&topic=topicParamInQuery CPS Proposed : /v1/ch/batch/data/ds/{datastore-name} ...&topic=topicParamInQuery cm handle ids and requestid into body |
...