DE4A Playground joining stages for the first iteration

Overview

the initial situation of the Playground for the first iteration of the DE4A project and the joining stages foreseen for the joining process of the pilot partners to the Playground. It also defines the information that each pilot partner needs to provide to WP5 in order to include that information in the appropriate components of the Playground so that the pilot partner can send messages via the Playground components.

DE4A Playground: initial stage

The DE4A Playground is the main element of the DE4A testing infrastructure. It simulates a real scenario where the User can request data (evidence) about a subject (citizen or company).

At its current development status, the Playground supports the complete message exchange process based on the Intermediation (IM) and User-Supported Intermediation (USI) patterns.

The following diagram depicts the initial deployment status of the Playground:

Schema of the initial scenario of the Playground

Description of the components:

• Mocked DE. It simulates the role of a Data Evaluator (DE). It is composed of a Web page to send IAL lookup messages to the mocked IDK and evidence request messages to the eGovlab Data Requestor (DR) and to display the responses. It also implements the software interface of a DE to receive responses from the eGovlab Data Requestor when the communication is based on the USI pattern. It is also able to redirect the User to the preview portal of the corresponding DO when using the USI pattern. It is deployed on eGovlab premises (Sweden).
  • https://de4a-dev-mock.egovlab.eu/public/locale-en_US/menuitem-de

• eGovlab Data Requestor. Latest version of the DE4A Connector, taking the role of a DR. As an AS4 Gateway, it uses the phase4 gateway integrated in it. It is deployed on eGovlab premises (Sweden).
  • https://de4a-dev-connector.egovlab.eu/

• SML/DNS. External component provided the Commission, part of the eDelivery infrastructure. It allows discovering the SMP of a DE4A final participant (DE or DO).
• eGovlab SMP. Component of the eDelivery infrastructure that allows discovering the routing information of a DE4A final participant (DE or DO). To do so, it is populated with the routing information of the fake partners of the examples stored in the mocked DO. There is only one SMP deployed, which is shared by eGovlab and SGAD. It is deployed on eGovlab premises (Sweden).
  • https://de4a-smp.egovlab.eu/

• Mocked IDK. REST service that implements the Issuing Authority Locator (IAL) API defined by WP3 [1]. It is populated with the generic information of the real and fake pilot participants required for the IAL functionality to work. It is deployed on eGovlab premises (Sweden).
  • https://de4a-dev-idk.egovlab.eu/

• SGAD Data Transferor. Latest version of the DE4A Connector, taking the role of a DT. As an AS4 Gateway, it uses the Domibus server deployed in SGAD. It is deployed on SGAD premises (Spain).
  • https://pre-as4gw-dt-de4a.redsara.es/de4a-connector/

• SGAD Domibus. European Commission’s reference AS4 Gateway, deployed in SGAD premises (Spain).

• Mocked DO. It simulates the role of a Data Owner. It implements the software interface of a DO to receive evidence request messages from the SGAD Data Transferor and to send back the responses. It handles a database consisting of testing datasets [2] made up of examples of canonical evidences of each pilot and each canonical evidence type. It also implements a user interface to preview evidences and to accept or reject them when the communication is based on the USI pattern. It is deployed on SGAD premises (Spain).
  • https://pre-smp-dr-de4a.redsara.es/de4a-mock-connector/

In order to differentiate between pilot partners who has already deployed their own final participants and the fake participants of the mocked DO, the latter use “9999” as a schema.

• eGovlab Kafka server. Kafka server that receives messages sent by the DE4A Connectors connected to it. The messages are displayed by the Package Tracker component. Both components are deployed on eGovlab premises (Sweden).
  • Tracker: https://de4a-dev-pt.egovlab.eu/#!detail
  • TCP service: de4a-dev-kafka.egovlab.eu:9092
  • HTTP service: https://de4a-dev-kafka.egovlab.eu

When a pilot partner properly connects a final participant (DE or DO) to the Playground, it will be able to immediately send evidence request messages to the mocked DO and receive evidence response messages from it, in case it is a DE. In case the deployed final participant is a DO, it will be able to receive evidence request messages from the mocked DE and send evidence response messages to it.

As soon as another final participant successfully joins the Playground, both pilot partners will be able to exchange messages between their final participants (provided that one of them is a DE and the other a DO).