Repository navigation
Profile Nemhandel
Underlying specifications: https://rep.erst.dk/git/openebusiness/common/-/tree/master/guidelines/specification (Danish Business Authority, Erhvervsstyrelsen). A copy of the versions used is stored in the docs folder of the submodule phase4-profile-nemhandel.
This profile is available since v4.8.2. See #408.
This submodule comes with one profile only:
- ID
nemhandel
Nemhandel eDelivery is based on the Peppol AS4 profile 2.0.2 (plus Peppol SML 1.2.0, SMP 1.3.0, SBDH 2.0.1 and the Peppol policies for identifiers and transport security). The Nemhandel specifications do not define any AS4 or PMode level deviation. Therefore this submodule has no logic of its own:
-
NemhandelPMode.createNemhandelPModedelegates toPeppolPMode.createPeppolPMode -
NemhandelCompatibilityValidatorextendsPeppolCompatibilityValidatorwithout any change - The profile is registered via SPI (
AS4NemhandelProfileRegistarSPI) with the IDnemhandel, the nameNemhandeland the dynamic PMode ID provider
For all AS4 details (one-way push, signing, encryption, compression, ...) see Profile Peppol.
<dependency>
<groupId>com.helger.phase4</groupId>
<artifactId>phase4-profile-nemhandel</artifactId>
<version>x.y.z</version>
</dependency>The module depends on phase4-lib and phase4-profile-peppol.
The class CNemhandel contains the Nemhandel specific values, taken from the Nemhandel eDelivery Network Specification 1.2.0:
| Constant | Value | Meaning |
|---|---|---|
TRANSPORT_PROFILE_ID_NEMHANDEL_AS4_V2 |
nemhandel-transport-as4-v2_0 |
SMP transport profile (Peppol uses peppol-transport-as4-v2_0) |
SML_URL |
https://sml.erst.dk/nemhandel-sml/ |
URL of the Nemhandel SML (SML DK) |
SBDH_SCOPE_TYPE_SIGNATURE |
NEMHANDEL_EDELIVERY_SIGNATURE |
SBDH business scope type that carries the XAdES document signature |
SBDH_SCOPE_IDENTIFIER_SIGNATURE |
nemhandel-edelivery-1.2 |
SBDH business scope identifier that accompanies the signature |
There is no Nemhandel specific client or servlet submodule. Use the Peppol ones:
- Sending:
phase4-peppol-client(Phase4PeppolSender), see Profile Peppol - Receiving:
phase4-peppol-servlet, see Profile Peppol
Because Nemhandel Access Points do not have a Peppol seat ID, the Peppol seat ID pattern P[A-Z]{2}[0-9]{6} must be switched off:
- Incoming: set the configuration property
phase4.peppol.inbound.check-seat-id=false(defaulttrue). The pattern is then no longer enforced forPartyInfo/From/PartyIdandPartyInfo/To/PartyId. - Outgoing: call
performSeatIDCheck (false)on thePhase4PeppolSenderbuilder.
| Topic | Nemhandel | Status in phase4 |
|---|---|---|
| AP certificates | MitID system certificates (FOCES3) with the CVR number in the subject; no Peppol seat ID | Not checked by this module. Make sure that the trust configuration of your sender and servlet matches your Nemhandel environment |
| Payload signature | Detached XAdES-BASELINE-B in StandardBusinessDocumentHeader/BusinessScope/Scope of type NEMHANDEL_EDELIVERY_SIGNATURE
|
Not supported; only the constants exist |
| Validation | XSD error: synchronous rejection; Schematron error: asynchronous MLR/AR | Asynchronous responses are not supported |
| Error codes |
E-APR21xxx list (Error Code List 1.1.0) |
Not supported |
| Logging, uptime, payload size | 5 years, 99.65 %, 100 MB | Operational requirements, not enforced |
Open points in the Nemhandel sources themselves: the Network specification requires error code list 1.2.0, but only 1.1.0 is published, and that version still refers to ASiC-E / transfer delegation, which the Network specification no longer uses.
My personal Coding Styleguide | It is appreciated if you star the GitHub project if you like it.
