Difference between revisions of "Intermediation pattern communication diagram"
Jump to navigation
Jump to search
Hugo.berdon (talk | contribs) |
Hugo.berdon (talk | contribs) |
||
| Line 12: | Line 12: | ||
'''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. [<nowiki/>[[DE4A Logs and error messages it2|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. [<nowiki/>[[DE4A Logs and error messages it2|40602]]] <blockquote><nowiki>*</nowiki> The interfaces are the same as the IAL, that’s why we refer to that document. |
</blockquote> | </blockquote> | ||
| Line 28: | Line 28: | ||
* ''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. [<nowiki/>[[DE4A Logs and error messages it2|10303]]] |
| − | * Mandatory fields must be present in the request. [40302] | + | * Mandatory fields must be present in the request. [<nowiki/>[[DE4A Logs and error messages it2|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. [<nowiki/>[[DE4A Logs and error messages it2|40306]]] |
<blockquote><nowiki>*</nowiki> The interfaces are the same as the IAL, that’s why we refer to that document. | <blockquote><nowiki>*</nowiki> The interfaces are the same as the IAL, that’s why we refer to that document. | ||
Revision as of 11:43, 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. Request evidence
- Description: Data Evaluator sends a request to the Connector DR to get the evidence. Data Evaluator and Data Owner identify both components.
- Message type: RequestExtractMultiEvidenceIMType. 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]
* The interfaces are the same as the IAL, that’s why we refer to that document.
4. SMP addressing
- Description: Connector DR sends a request to the SML to get the SMP address. Detailed information is available in ‘eDelivery SMP’ Document.
- Message type: Detailed in ‘eDelivery usage in DE4A’ Document.*
5. Node information
Request
- Description: Connector DR sends a request to the SMP to get gateway information. Multi evidence approach is available in ‘eDelivery SMP’ 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. Request evidence
- Description: Connector DR sends a request to Connector DT to get the evidence.
- Message type: RequestExtractMultiEvidenceIMType. 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. Extract multi-evidence request
- Description: Connector DT sends a request to Data Owner to get the evidence.
- Message type: RequestExtractMultiEvidenceIMType. Specified in ‘Data Dictionary’.
Error handling
- If Data Owner 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]
8. Extract multi-evidence response
- Description: Data Owner sends a response to Connector DT with the evidence.
- Message type: ResponseExtractMultiEvidenceType. 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’.
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.
11. Evidence response
- Description: Connector DT sends a response to Connector DR with the evidence.
- Message Type: ResponseExtractMultiEvidenceType. 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. Forward evidence
- Description: Connector DR sends a response to Data Evaluator with the evidence.
- Message Type: ResponseExtractMultiEvidenceType. 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.