EMSWe RIM Sender Integration – Access Point Setup Guide

Reference document
This document is a concise technical overview for senders.
For authoritative requirements, detailed field definitions, validation rules, certificate policies, and legal references, always refer to:
Finland EMSWe Domibus Sender Integration Guide.pdf

Purpose

This document provides quick, practical guidance for senders integrating with a Member State backend through the Reporting Interface Module (RIM) using AS4 (Domibus) within the European Maritime Single Window environment (EMSWe).

It focuses on:

• Sender-side architecture and responsibilities
• AS4 Access Point (C2) setup and ownership
• Message preparation and metadata expectations
• Security, certificates, and authentication prerequisites

This guidance applies to both:

• Declarants (DECL)
• Data Service Providers (DSP)

as defined by EMSWe and the RIM architecture.

Architecture Overview (Four-Corner Model)

flowchart LR
        C1["Sender Backend (C1)"]
        C2["Sender AS4 Access Point – Domibus (C2)"]
        C3["Member State RIM – Domibus (C3)"]
        C4["Member State MNSW Backend (C4)"]
        C1 -->|ASiC-E payload| C2
        C2 -->|AS4 UserMessage| C3
        C3 -->|Validated payload| C4
    

The sender fully controls C1 and C2 only. All communication beyond C2 takes place via secure AS4 exchange.

AS4 Access Point Requirement (Key Rule)

There is NO shared or Member State–provided AS4 Access Point.

• The Member State does not provide an AS4 Access Point for senders
• All AS4 Access Points (C2) are self-hosted
• Responsibility for setting up, configuring, and operating C2 lies entirely with the sender side

The Domibus AS4 Access Point software is publicly available and can be downloaded from the EU DIGIT eDelivery website. Each sender must install and operate its own Domibus instance and configure communication between:

• its backend system (C1), and
• its AS4 Access Point (C2)

This applies regardless of whether the sender submits messages directly or via a service provider.

Role of Data Service Providers (DSP)

A Data Service Provider (DSP) can be characterized as a technical service that:

• Operates an AS4 Access Point (C2) on behalf of one or more Declarants (DECL)
• Provides connectivity, AS4 messaging, and security configuration as a service
• Integrates multiple Declarant backends (C1) with its own Access Point (C2)

Important clarifications:

• DSPs are not provided by the Member State
• DSPs are not central or national shared services
• Use of a DSP is a commercial or contractual arrangement between senders and the DSP

From the RIM and Member State perspective:

• Both DECL and DSP are treated as senders
• Both must be registered in URAM
• Both are responsible (directly or indirectly) for operating a compliant C2 (AS4 Access Point)

Message Preparation (Sender Backend – C1)

Before transmission, the sender backend must create an ASiC-E container that includes:

• EMSWe formality XML
• META-INF/signatures.p7b (CAdES signature)
• manifest.xml
• mimetype = application/vnd.etsi.asic-e+zip
• Optional signed attachments (PDF, XML, jpg or png)

Signature requirements:

• eIDAS Qualified or Advanced Electronic Signature (QES / AdES)
• Hash algorithm: SHA-256

The ASiC-E container is handed over to the Access Point unchanged.

AS4 Message Mapping (Access Point – C2)

The Access Point (Domibus) wraps the ASiC-E container into an AS4 UserMessage.

Mandatory header metadata includes:

Critical requirement: The EORI value must exactly match the value registered in URAM, otherwise the message is rejected.

Certificates and Security

Minimum cryptographic requirements:

• RSA ≥ 2048 bits or ECDSA ≥ 256 bits
• SHA-256

Registration and Authentication (URAM)

Before sending any messages:

• The sender must be registered in URAM by Member State
• Registration includes:
  • EORI
  • Sender type (DECL or DSP)
  • Country subdomain
  • Certificate fingerprint

The RIM validates every incoming AS4 message against URAM.

Configure Domibus PMode

After the Access Point, certificates and network connectivity have been prepared, configure Domibus with an EMSWe RIM-compatible PMode. The PMode binds the parties, endpoints, service, actions, payload profile, security policy, reliability settings and message retention into an executable AS4 process.

Open Domibus PMode Configuration Guide →

Access Point Configuration and Changes

A bilateral AS4 agreement between the sender and the Member State defines:

• AS4 endpoints
• Party identifiers
• Certificates
• PMode configuration
• Security policy

Any change (certificate, endpoint, key) requires:

• Advance notification
• Certificate exchange
• PMode update
• Staging tests
• Production activation
• Versioned documentation