Difference between revisions of "Subscription pattern communication diagram"
Jump to navigation
Jump to search
Hugo.berdon (talk | contribs) |
Hugo.berdon (talk | contribs) |
||
| Line 13: | Line 13: | ||
'''Error handling''' | '''Error handling''' | ||
| − | If Data Evaluator cannot be reached there will be a communication error. [10603] | + | If Data Evaluator cannot be reached there will be a communication error. [[https://wiki.de4a.eu/index.php/DE4A_Logs_and_error_messages_it2#Connector 10603]] |
Mandatory fields must be present in the request. [40602] <blockquote><nowiki>*</nowiki> The interfaces are the same as the IAL, that’s why we refer to that document. | Mandatory fields must be present in the request. [40602] <blockquote><nowiki>*</nowiki> The interfaces are the same as the IAL, that’s why we refer to that document. | ||
| Line 29: | Line 29: | ||
*''Message type:'' '''[https://wiki.de4a.eu/index.php/Data_Dictionary#ResponseLookupRoutingInformationType ResponseLookupRoutingInformation]'''. Detailed in the ‘[https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/IAL%20design%20(2nd%20iteration)&fileid=1144261 IAL Technical Design]’. | *''Message type:'' '''[https://wiki.de4a.eu/index.php/Data_Dictionary#ResponseLookupRoutingInformationType ResponseLookupRoutingInformation]'''. Detailed in the ‘[https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/IAL%20design%20(2nd%20iteration)&fileid=1144261 IAL Technical Design]’. | ||
'''Error handling''' | '''Error handling''' | ||
| − | *If IDK cannot be reached there will be a communication error. [10303] | + | *If IDK cannot be reached there will be a communication error. [[https://wiki.de4a.eu/index.php/DE4A_Logs_and_error_messages_it2#Connector 10303]] |
*Mandatory fields must be present in the request. [40302] | *Mandatory fields must be present in the request. [40302] | ||
*If request information does not obtain results, there will be a no data found error. [40306] | *If request information does not obtain results, there will be a no data found error. [40306] | ||
| Line 42: | Line 42: | ||
*''Message type:'' '''[https://wiki.de4a.eu/index.php/Data_Dictionary#RequestEventSubscriptionType RequestEventSubscriptionType]'''. Specified in [https://wiki.de4a.eu/index.php/Data_Dictionary Data Dictionary]. | *''Message type:'' '''[https://wiki.de4a.eu/index.php/Data_Dictionary#RequestEventSubscriptionType RequestEventSubscriptionType]'''. Specified in [https://wiki.de4a.eu/index.php/Data_Dictionary Data Dictionary]. | ||
'''Error handling''' | '''Error handling''' | ||
| − | *If Connector DR cannot be reached there will be a communication error. [10603] | + | *If Connector DR cannot be reached there will be a communication error. [[https://wiki.de4a.eu/index.php/DE4A_Logs_and_error_messages_it2#Connector 10603]] |
*Mandatory fields must be present in the request. [40602] | *Mandatory fields must be present in the request. [40602] | ||
| Line 59: | Line 59: | ||
*''Message type:'' Detailed in ‘eDelivery usage in DE4A’ Document. * | *''Message type:'' Detailed in ‘eDelivery usage in DE4A’ Document. * | ||
'''Error handling''' | '''Error handling''' | ||
| − | *If SMP cannot be reached there will be a communication error. [10303] | + | *If SMP cannot be reached there will be a communication error. [[https://wiki.de4a.eu/index.php/DE4A_Logs_and_error_messages_it2#Connector 10303]] |
*Mandatory fields must be present in the request. [40302] | *Mandatory fields must be present in the request. [40302] | ||
*If request information does not obtain results, there will be a no data found error. [40306] Detailed information is available in ‘[https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eDelivery+BDXL+1.6 eDelivery BDXL]’ Document. | *If request information does not obtain results, there will be a no data found error. [40306] Detailed information is available in ‘[https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eDelivery+BDXL+1.6 eDelivery BDXL]’ Document. | ||
| Line 68: | Line 68: | ||
*''Message type:'' '''[https://wiki.de4a.eu/index.php/Data_Dictionary#RequestEventSubscriptionType RequestEventSubscriptionType]'''. Specified in ‘[https://wiki.de4a.eu/index.php/Data_Dictionary Data Dictionary]’. | *''Message type:'' '''[https://wiki.de4a.eu/index.php/Data_Dictionary#RequestEventSubscriptionType RequestEventSubscriptionType]'''. Specified in ‘[https://wiki.de4a.eu/index.php/Data_Dictionary Data Dictionary]’. | ||
'''Error handling''' | '''Error handling''' | ||
| − | *If Connector DT cannot be reached there will be a communication error. [10303] | + | *If Connector DT cannot be reached there will be a communication error. [[https://wiki.de4a.eu/index.php/DE4A_Logs_and_error_messages_it2#Connector 10303]] |
*Mandatory fields must be present in the request. [40302] | *Mandatory fields must be present in the request. [40302] | ||
| Line 87: | Line 87: | ||
'''Error handling''' | '''Error handling''' | ||
| − | * If Connector DT cannot be reached there will be a communication error. [10503] | + | * If Connector DT cannot be reached there will be a communication error. [[https://wiki.de4a.eu/index.php/DE4A_Logs_and_error_messages_it2#Connector 10503]] |
* Mandatory fields must be present in the request. [40502] | * Mandatory fields must be present in the request. [40502] | ||
| Line 109: | Line 109: | ||
'''Error handling''' | '''Error handling''' | ||
| − | *If SMP cannot be reached there will be a communication error. [10403] | + | *If SMP cannot be reached there will be a communication error. [[https://wiki.de4a.eu/index.php/DE4A_Logs_and_error_messages_it2#Connector 10403]] |
*Mandatory fields must be present in the request. [40402] | *Mandatory fields must be present in the request. [40402] | ||
*If request information does not obtain results, there will be a no data found error. [40406] | *If request information does not obtain results, there will be a no data found error. [40406] | ||
| Line 122: | Line 122: | ||
'''Error handling''' | '''Error handling''' | ||
| − | *If Connector DR cannot be reached there will be a communication error. [10403] | + | *If Connector DR cannot be reached there will be a communication error. [[https://wiki.de4a.eu/index.php/DE4A_Logs_and_error_messages_it2#Connector 10403]] |
*Mandatory fields must be present in the request. [40402] | *Mandatory fields must be present in the request. [40402] | ||
| Line 133: | Line 133: | ||
'''Error handling''' | '''Error handling''' | ||
| − | *If Data Evaluator cannot be reached there will be a communication error. [10303] | + | *If Data Evaluator cannot be reached there will be a communication error. [[https://wiki.de4a.eu/index.php/DE4A_Logs_and_error_messages_it2#Connector 10303]] |
*Mandatory fields must be present in the request. [40302] <br /> | *Mandatory fields must be present in the request. [40302] <br /> | ||
Revision as of 12:49, 17 May 2022
1. Lookup routing information
Request
- Description: Data Evaluator sends a request to the Connector DR.
- Message type: Detailed in the ‘IAL Technical Design’.
Response
- Description: Connector DR sends a response to Data Evaluator.
- Message type: ResponseLookupRoutingInformation. Detailed in the ‘IAL Technical Design’.
Error handling
If Data Evaluator cannot be reached there will be a communication error. [10603]
Mandatory fields must be present in the request. [40602]
* The interfaces are the same as the IAL, that’s why we refer to that document.
2. Lookup routing information
Request
- Description: Connector DR sends a request to the IDK to get routing information.
- Message type: Detailed in the ‘IAL Technical Design’.
Response
- Description: IDK sends a response to Connector DR providing the routing information.
- Message type: ResponseLookupRoutingInformation. Detailed in the ‘IAL Technical Design’.
Error handling
- If IDK cannot be reached there will be a communication error. [10303]
- Mandatory fields must be present in the request. [40302]
- If request information does not obtain results, there will be a no data found error. [40306]
* The interfaces are the same as the IAL, that’s why we refer to that document.
3. Subscription request
- Description: Data Evaluator sends a subscription request to the Connector DR. Data Evaluator and Data Owner identify both components.
- Message type: RequestEventSubscriptionType. Specified in Data Dictionary.
Error handling
- If Connector DR cannot be reached there will be a communication error. [10603]
- Mandatory fields must be present in the request. [40602]
4. SMP addressing
- Description: Connector DR sends a request to the SML to get the SMP address. Data Owner identifier will be sent as the participant identifier.
- Message type: Detailed information is available in ‘eDelivery SMP’.
5. Node information
Request
- Description: Connector DR sends a request to the SMP to get gateway information. Multi evidence approach is available in ‘SMP query process in DE4A’ Document.
- Message type: Detailed in ‘eDelivery usage in DE4A’ Document. *
Response
- Description: SMP sends a response to Connector DR providing the gateway information. The destination endpoint and the certificate will be provided.
- Message type: Detailed in ‘eDelivery usage in DE4A’ Document. *
Error handling
- If SMP cannot be reached there will be a communication error. [10303]
- Mandatory fields must be present in the request. [40302]
- If request information does not obtain results, there will be a no data found error. [40306] Detailed information is available in ‘eDelivery BDXL’ Document.
6. Subscription request
- Description: Connector DR sends a request to Connector DT to get the evidence.
- Message type: RequestEventSubscriptionType. Specified in ‘Data Dictionary’.
Error handling
- If Connector DT cannot be reached there will be a communication error. [10303]
- Mandatory fields must be present in the request. [40302]
7. Subscription request
- Description: Connector DT sends a subscription request to Data Owner.
- Message type: RequestEventSubscriptionType. Specified in ‘Data Dictionary’.
Error handling
- If Connector DT cannot be reached there will be a communication error. [10303]
- Mandatory fields must be present in the request. [40402]
8. Subscription response
- Description: Data Owner sends a response to Connector DT confirming the subscription.
- Message type: Specified in ‘Data Dictionary’.
Error handling
- If Connector DT cannot be reached there will be a communication error. [10503]
- Mandatory fields must be present in the request. [40502]
9. SMP addressing
- Description: Connector DT sends a request to the SML to get the SMP address. Data Evaluator identifier will be sent as the participant identifier. Detailed information is available in ‘eDelivery SMP’ Document.
10. Node information
Request
- Description: Connector DT sends a request to the SMP to get gateway information. Multi evidence approach is available in ‘SMP query process in DE4A’ Document.
- Message type: Detailed in ‘eDelivery usage in DE4A’ Document. *
Response
- Description: SMP sends a response to Connector DT providing the gateway information. The destination endpoint and the certificate will be provided.
- Message type: Detailed in ‘eDelivery usage in DE4A’ Document. *
Error handling
- If SMP cannot be reached there will be a communication error. [10403]
- Mandatory fields must be present in the request. [40402]
- If request information does not obtain results, there will be a no data found error. [40406]
Detailed information is available in ‘eDelivery BDXL’ Document.3
11. Subscription response
- Description: Connector DT sends a response to Connector DR with the subscription.
- Message Type: ResponseEventSubscriptionType. Specified in ‘Data Dictionary’.
Error handling
- If Connector DR cannot be reached there will be a communication error. [10403]
- Mandatory fields must be present in the request. [40402]
12. Subscription response
- Description: Connector DR sends a response to Data Evaluator with the subscription.
- Message Type: ResponseEventSubscriptionType. Specified in ‘Data Dictionary’.
Error handling
- If Data Evaluator cannot be reached there will be a communication error. [10303]
- Mandatory fields must be present in the request. [40302]
* Document is under construction.