Difference between revisions of "Cross-border Subscriptions"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
| − | The Cross-border | + | The Cross-border Subscriptions application collaboration consists of various co-operating application components. |
| + | |||
| + | |||
| + | |||
| + | used by Notification Process Realization - DP | ||
| + | |||
| + | Subscription Process Realization - DP | ||
| + | |||
| + | |||
| + | realizing the functionality needed to complete two processes in the [[Subscription and Notification Pattern]]. | ||
<gallery widths="400" perrow="1" caption="Graphic representations of the Cross-border Subscriptions application collaboration"> | <gallery widths="400" perrow="1" caption="Graphic representations of the Cross-border Subscriptions application collaboration"> | ||
| Line 15: | Line 24: | ||
|[[Subscription System]] | |[[Subscription System]] | ||
|Application component managing the entire life cycle of subscriptions, ie creation and maintaining subscriptions. It also offers functionality for validating subscriptions (...), confirmation of a subscription (...) and error handling. | |Application component managing the entire life cycle of subscriptions, ie creation and maintaining subscriptions. It also offers functionality for validating subscriptions (...), confirmation of a subscription (...) and error handling. | ||
| − | The component | + | The component makes use of an interface to access the base registry. |
|[[Subscription and Notification Pattern|S&N]] | |[[Subscription and Notification Pattern|S&N]] | ||
| Line 21: | Line 30: | ||
|[[Cross-border Event Handler]] | |[[Cross-border Event Handler]] | ||
|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. | |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 | + | The component makes use of an interface toaccess the base registry. |
|[[Subscription and Notification Pattern|S&N]] | |[[Subscription and Notification Pattern|S&N]] | ||
|- | |- | ||
Revision as of 11:06, 4 June 2021
The Cross-border Subscriptions application collaboration consists of various co-operating application components.
used by Notification Process Realization - DP
Subscription Process Realization - DP
realizing the functionality needed to complete two processes in the Subscription and Notification Pattern.
- Graphic representations of the Cross-border Subscriptions application collaboration
.png)
- Subscription
- Notification
| Application Component | Description | Pattern(s) |
|---|---|---|
| Subscription System | Application component managing the entire life cycle of subscriptions, ie creation and maintaining subscriptions. It also offers functionality for validating subscriptions (...), confirmation of a subscription (...) and error handling.
The component makes use of an interface to access the base registry. |
S&N |
| Cross-border Event Handler | 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. |
S&N |
| Notification Back-end | Application component serving the front-end. | S&N |
| Notification Front-end | Application component providing the UI for civil servants in order to dispatch events and consult logging information for trouble shooting. | S&N |