Difference between revisions of "Notification Back-end"
Jump to navigation
Jump to search
| Line 30: | Line 30: | ||
|- | |- | ||
| Manual Event Dispatch | | Manual Event Dispatch | ||
| − | | | + | | A service for resending a previously sent notification. It requires a manual action at the DT based on logs. |
| [[Subscription and Notification Pattern|S&N]] | | [[Subscription and Notification Pattern|S&N]] | ||
|- | |- | ||
| − | | | + | |Subscription Mismatch Log |
| − | | | + | |If the participant id cannot be resolved, manual intervention is needed. The DE needs to be informed and appropriate measures taken. This serves handles this. |
| − | | | + | |[[Subscription and Notification Pattern|S&N]] |
|- | |- | ||
|} | |} | ||
Revision as of 11:29, 4 June 2021
| Item | Description |
|---|---|
| name | Notification Back-end |
| description | Application component serving the front-end and connecting with event handling. |
| pattern(s) | S&N |
| application collaboration | Cross-border Subscriptions |
| Application Service | Description | Pattern |
|---|---|---|
| Manual Event Dispatch | A service for resending a previously sent notification. It requires a manual action at the DT based on logs. | S&N |
| Subscription Mismatch Log | If the participant id cannot be resolved, manual intervention is needed. The DE needs to be informed and appropriate measures taken. This serves handles this. | 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. |