Difference between revisions of "Usage of third party specifications and components"
| Line 18: | Line 18: | ||
The task of a Service Metadata Publisher (SMP) is to create the link between the technical identifiers and the effective endpoint URL to exchange messages with. Additionally, it provides X.509 certificates that will be used to encrypt messages for a specific recipient. Each participant has a list of so called “Endpoints” that are uniquely identified by a combination of a document type identifier, a process identifier and a transport profile. An SMP makes it possible for two parties in the domain to exchange documents with dynamic discovery and utilizing the 4 Corner Model used for eDelivery within the DE4A project. | The task of a Service Metadata Publisher (SMP) is to create the link between the technical identifiers and the effective endpoint URL to exchange messages with. Additionally, it provides X.509 certificates that will be used to encrypt messages for a specific recipient. Each participant has a list of so called “Endpoints” that are uniquely identified by a combination of a document type identifier, a process identifier and a transport profile. An SMP makes it possible for two parties in the domain to exchange documents with dynamic discovery and utilizing the 4 Corner Model used for eDelivery within the DE4A project. | ||
| − | The | + | The information has been structured as follows, based on the SMP schemas outlines: |
| − | |||
{| class="wikitable" | {| class="wikitable" | ||
| − | + | ! SMP filed name | |
| + | ! DE4A parameter | ||
| + | ! Description | ||
| + | ! Example | ||
|- | |- | ||
| − | |iso6523-actorid-upis | + | |ParticipantIdentifier |
| + | |Participant ID | ||
| + | |Unique identifier assigned to each entity involved (DE's/DO's) | ||
| + | |Scheme: iso6523-actorid-upis - Value: 9999:egov | ||
|- | |- | ||
| − | | | + | |DocumentIdentifier |
| + | |Canonical Evidence Type | ||
| + | |Type of canonical evidence | ||
| + | |Scheme: urn:de4a-eu:CanonicalEvidenceType - Value: CompanyRegistration | ||
|- | |- | ||
| − | | | + | |ProcessIdentifier |
| + | |Message Type | ||
| + | |Action type (request/response) for a message | ||
| + | |Scheme: urn:de4a-eu:MessageType - Value: request | ||
|- | |- | ||
| − | | | + | |EndpointURI |
| − | + | |AS4 endpoint | |
| − | + | |Endpoint where the AS4 message will be sent for a certain participant | |
| − | + | |https://de4a-dev-connector.egovlab.eu/phase4 | |
| − | |||
| − | |||
| − | |||
| − | | | ||
| − | | | ||
| − | | | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
|} | |} | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
==RegRep== | ==RegRep== | ||
Revision as of 14:42, 20 August 2021
Overview
eDelivery
The CEF eDelivery Building Block helps users to exchange electronic data and documents with one another in a reliable and trusted way.
The CEF eDelivery solution is based on a distributed model called the “4-corner model”. In this model, the back-end systems of the users don't exchange data directly with each other but do this through Access Points. These Access Points are conformant to the same technical specifications and therefore capable of communicating with each other.
As a result of this, users adopting CEF eDelivery can easily and safely exchange data even if their IT systems were developed independently from each other.
SML
The Service Metadata Locator (SML) is a singleton instance in the DE4A network. It is operated by CEF, a key facility of the European Commission, and provided to the DE4A project at no cost. DE4A is currently operating on the test instance of the SML, called "SMK", and was assigned the DNS zone de4a.acc.edelivery.tech.ec.europa.eu. for the project.
Additionally, CEF provided the project 10 test SMP X.509 certificates based on the "DE4A_TEST_SMP_CA" which is based on CEFs "Connectivity Test Component CA". Only certificates issued by the "DE4A_TEST_SMP_CA" are allowed to register in the DE4A SML DNS zone.
Every SMP (see below) that wants to join the DE4A network needs to register once at the SML using the specific DNS zone and a certificate based on the "DE4A_TEST_SMP_CA".ç
SMP
The task of a Service Metadata Publisher (SMP) is to create the link between the technical identifiers and the effective endpoint URL to exchange messages with. Additionally, it provides X.509 certificates that will be used to encrypt messages for a specific recipient. Each participant has a list of so called “Endpoints” that are uniquely identified by a combination of a document type identifier, a process identifier and a transport profile. An SMP makes it possible for two parties in the domain to exchange documents with dynamic discovery and utilizing the 4 Corner Model used for eDelivery within the DE4A project.
The information has been structured as follows, based on the SMP schemas outlines:
| SMP filed name | DE4A parameter | Description | Example |
|---|---|---|---|
| ParticipantIdentifier | Participant ID | Unique identifier assigned to each entity involved (DE's/DO's) | Scheme: iso6523-actorid-upis - Value: 9999:egov |
| DocumentIdentifier | Canonical Evidence Type | Type of canonical evidence | Scheme: urn:de4a-eu:CanonicalEvidenceType - Value: CompanyRegistration |
| ProcessIdentifier | Message Type | Action type (request/response) for a message | Scheme: urn:de4a-eu:MessageType - Value: request |
| EndpointURI | AS4 endpoint | Endpoint where the AS4 message will be sent for a certain participant | https://de4a-dev-connector.egovlab.eu/phase4 |
RegRep
Kafka
References
<references />