Analysis on Forwarded Event:
- We are using 'NCMPAsynRequestResponse' event schema to consume 'DMIAsynRequestResponse' event and forward to the client.
- NCMPAsynRequestResponse has 2 object properties other than individual properties. The below 2 has the same properties.
- Event
- We are not mapping anything to this property object/type., While mapping properties from 'DMIAsynRequestResponse' to 'NCMPAsynRequestResponse'. We can find the same on the below screenshot.
- Forwarded Event
- While mapping properties from 'DMIAsynRequestResponse' to 'NCMPAsynRequestResponse', We are mapping all the properties to the 'ForwardedEvent'.
- Particularly response-Data from 'DMIAsynRequestResponse' is mapped to additional properties in 'NCMPAsynRequestResponse → ForwardedEvent'
- Event
Clear Explanation with properties:
draw.io
| # | properties | NCMP Headers/ External Props | NCMP Forwaded Event | NCMP Event | DMI Headers/ External Props | DMI Event-Content |
|---|---|---|---|---|---|---|
| 1 | eventId | * | * | * | * | N/A |
| 2 | eventCorrelationId | * | * | * | * | N/A |
| 3 | eventTime | * | * | * | * | N/A |
| 4 | eventTarget | * | * | * | * | N/A |
| 5 | eventType | * | * | * | * | N/A |
| 6 | eventSchema | * | * | * | * | N/A |
| 7 | eventSchemaVersion | * | * | N/A | * | N/A |
| 8 | eventSource | N/A | * | * | * | N/A |
| 9 | response-data-schema | Event/FE | * | * | Event-Content | * |
| 10 | response-status | Event/FE | * | * | Event-Content | * |
| 11 | response-code | Event/FE | * | * | Event-Content | * |
| 12 | forwardedEventData | Fwd Event | * | N/A | N/A | N/A |
| 13 | response-data | Event | N/A | * | Event-Content | * |