Difference between revisions of "DE4A Connector it2"
| Line 7: | Line 7: | ||
The security and integrity of messages, as well as the unique identification of the participants involved, are the cornerstones of the Connector component. | The security and integrity of messages, as well as the unique identification of the participants involved, are the cornerstones of the Connector component. | ||
| − | Follow the link to the [[Installation and configuration guide|Installation and configuration]] guide of the DE4a Connector. | + | Follow the link to the [[Installation and configuration guide of the DE4A Connector it2|Installation and configuration]] guide of the DE4a Connector. |
[[File:De4a-schema-it1.png|Conceptual schema of the target DE4A system for the first iteration|alt=|center|frame]] | [[File:De4a-schema-it1.png|Conceptual schema of the target DE4A system for the first iteration|alt=|center|frame]] | ||
Revision as of 09:09, 10 November 2022
The DE4A Connector is a technical proxy that allows the final participants (DE or DO) to send requests for evidence or responses to other final participants over an eDelivery communication environment. In addition, to handle the message exchange process, the Connector is responsible for obtaining the message routing information, by exchanging information with external components such as the IDK, the SML/DNS or the SMP.
To do so, it provides a common interface to DEs and DOs, making the complexity of the system transparent to the final participants and integration easier.
The Connector component provides the AS4 Gateway functionality, so it can assume both the role of Data Requestor and Data Transferor. This first approach makes the Connector a stand-alone web application that can be deployed on any suitable application server.
The security and integrity of messages, as well as the unique identification of the participants involved, are the cornerstones of the Connector component.
Follow the link to the Installation and configuration guide of the DE4a Connector.
