Difference between revisions of "Notification pattern communication diagram"

From DE4A
Jump to navigation Jump to search
(Created blank page)
 
 
(17 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 +
[[File:Comm diag it2 ALL v3.6-Notification.drawio.png|alt=|center|thumb|945x945px]]
  
 +
== 1. Make notification ==
 +
'''Request'''
 +
*''Description'': The Data Owner sends a message to the Connector DT with the notification. In the message payload, Data Evaluator and Data Owner identify both components.
 +
 +
* ''Message type'': Specified in ‘[https://wiki.de4a.eu/index.php/Data_Dictionary Data Dictionary]’.
 +
'''Response'''
 +
 +
* Description: The asynchronous message will have a response with the result of this communication.
 +
* Message type: [https://wiki.de4a.eu/index.php/Data_Dictionary#ResponseErrorType ResponseErrorType]. Specified in [https://wiki.de4a.eu/index.php/Data_Dictionary Data Dictionary].
 +
 +
'''Error handling'''
 +
 +
* If the Connector DT cannot be reached there will be a connection error. [[https://wiki.de4a.eu/index.php/DE4A_Logs_and_error_messages_it2#Data_Owner DOE01]]
 +
 +
== 2. SMP addressing ==
 +
* ''Description:'' The Connector DT sends a request to the SML to get the SMP address. Detailed information is available in ‘[https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eDelivery+SMP+-+1.10 eDelivery SMP]’ documentation.
 +
 +
* ''Message type:'' Detailed in ‘eDelivery usage in DE4A’ document.
 +
 +
== 3. Node information ==
 +
'''Request'''
 +
* ''Description:'' The Connector DT sends a request to the SMP to get gateway information. Multi evidence approach is available in ‘[https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eDelivery+SMP+-+1.10 eDelivery SMP]’ documentation.
 +
 +
* ''Message type:'' Detailed in ‘eDelivery usage in DE4A’ document.
 +
'''Response'''
 +
*''Description:'' The SMP sends a response to the Connector DT providing the gateway information. The destination endpoint and the certificate will be provided in the response.
 +
 +
*''Message type:'' Detailed in ‘eDelivery usage in DE4A’ document.
 +
'''Error handling'''
 +
* If the SMP cannot be reached there will be a connection error. [[https://wiki.de4a.eu/index.php/DE4A_Logs_and_error_messages_it2#Data_Transferor DTE01]]
 +
* Mandatory fields must be present in the request. [[https://wiki.de4a.eu/index.php/DE4A_Logs_and_error_messages_it2#Data_Transferor DTE05]]
 +
* If request information does not obtain results, there will be a no data found error. [[https://wiki.de4a.eu/index.php/DE4A_Logs_and_error_messages_it2#Data_Transferor DTE02]].
 +
Detailed information is available in ‘[https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eDelivery+BDXL+1.6 eDelivery BDXL]’ documentation.
 +
 +
== 4. Send notification ==
 +
 +
* ''Description:'' The Connector DT sends a message to the Connector DR with the notification.
 +
 +
* ''Message type:'' Specified in ‘[https://wiki.de4a.eu/index.php/Data_Dictionary Data Dictionary]’.
 +
 +
'''Error handling'''  
 +
 +
* If the Connector DR cannot be reached there will be a connection error. [[https://wiki.de4a.eu/index.php/DE4A_Logs_and_error_messages_it2#Data_Transferor DTE01]]
 +
 +
== 5. Forward notification ==
 +
'''Request'''
 +
*''Description:'' The Connector DR sends a message to the Data Evaluator with the notification.
 +
 +
* ''Message type:''  Specified in ‘[https://wiki.de4a.eu/index.php/Data_Dictionary Data Dictionary]’.
 +
'''Response'''
 +
* Description: The asynchronous message will have a response with the result of this communication.
 +
* Message type: [https://wiki.de4a.eu/index.php/Data_Dictionary#ResponseErrorType ResponseErrorType]. Specified in [https://wiki.de4a.eu/index.php/Data_Dictionary Data Dictionary].
 +
 +
'''Error handling'''  
 +
 +
* If Data Evaluator cannot be reached there will be a connection error. [[https://wiki.de4a.eu/index.php/DE4A_Logs_and_error_messages_it2#Data_Requestor DRE01]]

Latest revision as of 12:01, 12 August 2022

1. Make notification

Request

  • Description: The Data Owner sends a message to the Connector DT with the notification. In the message payload, Data Evaluator and Data Owner identify both components.

Response

  • Description: The asynchronous message will have a response with the result of this communication.
  • Message type: ResponseErrorType. Specified in Data Dictionary.

Error handling

  • If the Connector DT cannot be reached there will be a connection error. [DOE01]

2. SMP addressing

  • Description: The Connector DT sends a request to the SML to get the SMP address. Detailed information is available in ‘eDelivery SMP’ documentation.
  • Message type: Detailed in ‘eDelivery usage in DE4A’ document.

3. Node information

Request

  • Description: The Connector DT sends a request to the SMP to get gateway information. Multi evidence approach is available in ‘eDelivery SMP’ documentation.
  • Message type: Detailed in ‘eDelivery usage in DE4A’ document.

Response

  • Description: The SMP sends a response to the Connector DT providing the gateway information. The destination endpoint and the certificate will be provided in the response.
  • Message type: Detailed in ‘eDelivery usage in DE4A’ document.

Error handling

  • If the SMP cannot be reached there will be a connection error. [DTE01]
  • Mandatory fields must be present in the request. [DTE05]
  • If request information does not obtain results, there will be a no data found error. [DTE02].

Detailed information is available in ‘eDelivery BDXL’ documentation.

4. Send notification

  • Description: The Connector DT sends a message to the Connector DR with the notification.

Error handling  

  • If the Connector DR cannot be reached there will be a connection error. [DTE01]

5. Forward notification

Request

  • Description: The Connector DR sends a message to the Data Evaluator with the notification.

Response

  • Description: The asynchronous message will have a response with the result of this communication.
  • Message type: ResponseErrorType. Specified in Data Dictionary.

Error handling  

  • If Data Evaluator cannot be reached there will be a connection error. [DRE01]