Difference between revisions of "Cross-border Event Handler"
Jump to navigation
Jump to search
| Line 31: | Line 31: | ||
|- | |- | ||
| Cross-border Event Filter | | Cross-border Event Filter | ||
| − | | | + | | The Data Owner evaluates all events identified in the register and identifies events that are potentially relevant for cross-border notifications. |
| + | Note that the DO must have a mapping of it's own business events to the list of DE4A business events. | ||
| [[Subscription and Notification Pattern|S&N]] | | [[Subscription and Notification Pattern|S&N]] | ||
|- | |- | ||
| Notification Message and Subscriber List Preparation | | Notification Message and Subscriber List Preparation | ||
| − | | | + | | Make a list of the subscribers to notify in terms of cross-border participant identifiers and create the payload of the notification, mainly the DE4A event name and subject identifer and the timestamp the event took place. |
| [[Subscription and Notification Pattern|S&N]] | | [[Subscription and Notification Pattern|S&N]] | ||
|- | |- | ||
Revision as of 11:10, 4 June 2021
| Item | Description |
|---|---|
| name | Cross-border Event Handler |
| description | Application component handling the cross-border events. It filters all national events for relevant cross-border events and takes care of preparing a notification message and compiling a subscribers list to which the notification must be send.
The component makes use of an interface toaccess the base registry. |
| pattern(s) | S&N |
| application collaboration | Cross-border Subscriptions |
| Application Service | Description | Pattern |
|---|---|---|
| Cross-border Event Filter | The Data Owner evaluates all events identified in the register and identifies events that are potentially relevant for cross-border notifications.
Note that the DO must have a mapping of it's own business events to the list of DE4A business events. |
S&N |
| Notification Message and Subscriber List Preparation | Make a list of the subscribers to notify in terms of cross-border participant identifiers and create the payload of the notification, mainly the DE4A event name and subject identifer and the timestamp the event took place. | S&N |
| Component | Source | UC | Description |
|---|---|---|---|
| xyz | descr xyz | [[]] | Lorem ipsum dolor sit amet, consectetur adipiscing elit. Proin suscipit mauris eu dui aliquet, feugiat porttitor eros placerat. |
| abc | descr abc | [[]] | Lorem ipsum dolor sit amet, consectetur adipiscing elit. Proin suscipit mauris eu dui aliquet, feugiat porttitor eros placerat. |