Difference between revisions of "Cross-border Subscriptions"
		
		
		
		
		
		Jump to navigation
		Jump to search
		
				
		
		
	
| Line 1: | Line 1: | ||
| − | The Cross-border Subscriptions application collaboration consists of various co-operating application components implementing multiple application services used by both Notification Process Realization (DP) and Subscription Process Realization (DP). | + | The Cross-border Subscriptions application collaboration consists of various co-operating application components implementing multiple application services used by both Notification Process Realization (DP) and Subscription Process Realization (DP). It implements: | 
| − | |||
| − | It implements:   | ||
| * the full life cycle of subscriptions (CRUD) and offers functionality to validate and confirm subscriptions. | * the full life cycle of subscriptions (CRUD) and offers functionality to validate and confirm subscriptions. | ||
| * event handling, i.e. filtering local (national) events for relevant cross-border events and creating the notifications messages and preparing the list of subscribers for particular cross-border events that need to be dispatched. | * event handling, i.e. filtering local (national) events for relevant cross-border events and creating the notifications messages and preparing the list of subscribers for particular cross-border events that need to be dispatched. | ||
| * notifications of events | * notifications of events | ||
| − | + | It uses interfaces to communicate with the Base Registry of companies in the MS.<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"> | ||
| File:Cross-border_Subscriptions_(S&N).png|alt=Graphic representation of the Cross-border Subscriptions application collaboration in the Subscription & Notification Pattern|[[Subscription and Notification Pattern|S&N]] | File:Cross-border_Subscriptions_(S&N).png|alt=Graphic representation of the Cross-border Subscriptions application collaboration in the Subscription & Notification Pattern|[[Subscription and Notification Pattern|S&N]] | ||
| </gallery> | </gallery> | ||
Revision as of 10:19, 4 June 2021
The Cross-border Subscriptions application collaboration consists of various co-operating application components implementing multiple application services used by both Notification Process Realization (DP) and Subscription Process Realization (DP). It implements:
- the full life cycle of subscriptions (CRUD) and offers functionality to validate and confirm subscriptions.
- event handling, i.e. filtering local (national) events for relevant cross-border events and creating the notifications messages and preparing the list of subscribers for particular cross-border events that need to be dispatched.
- notifications of events
It uses interfaces to communicate with the Base Registry of companies in the MS.
- Graphic representations of the Cross-border Subscriptions application collaboration
- 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 | 
