Domibus v3.2.3
This page collects the resources for Domibus version 3.2.3, released in March 2017.
Access the Domibus eLearnings
Description
We are happy to announce the bug fix release of the production-ready Domibus 3.2.3 sample implementation of the eDelivery Access Point.
Domibus 3.2.3 includes a number of bug fixes and a couple of improvements concerning:
JMS monitoring improved for clustered installations
Default WS plugin: listPendingMessages and download operations behave correctly in case of a clustered installation
The MSH WS endpoint returns 200 for the GET operation
During the interoperability tests with 5 other AS4 solutions, in the context of the e-SENS eDelivery task force, it was found an issue with the security policy named eSensPolicy that is distributed in Domibus releases.
The issue is that the security policy did not indicate that the (always empty) body of the AS4 message must be signed.
4 out of 5 other AS4 solutions accepted this behavior, but there were issues with one AS4 solution that would reject the incoming message for this reason.
As from Domibus 3.2.3 this has been corrected (only a configuration change, no code change required) and
- will always sign the (empty) body of the AS4 message when sending a message
- will always expect the (empty) body of the AS4 message to be signed when receiving a message. If the body is not signed, the message is not accepted and an error will be returned.
This has the implication that when an Access Point in a network is upgrading its security policy to the new policy, all the participants in the network must upgrade as well.
Otherwise the Access Point will not be able to receive messages from other participants that did not yet upgrade.
Therefore we recommend all the business domains that are not yet in production to use the latest eSensPolicy 2.0 in case other AS4 solutions join their domain in the future. The new eSensPolicy 2.0 can also be used with Domibus 3.2.2
Domibus 3.2.3 is backward compatible with 3.2.x and 3.1.x and the upgrade is not mandatory.
Documentation
Quick Start Guide (pdf) | This guide allows the user to quickly get started with Domibus. After completing this document, you will have a local Domibus instance up and running locally on a Tomcat/MySQL environment. |
Testing guide (pdf) | This document is intended for developers that want to perform a set of checks on their Domibus installation and testers that want to have a starting point to create their own test cases. |
Interface Control Document of the default JMS (pdf) | The purpose of this document is to outline the JMS Data Format Exchange to be used as part of the default JMS backend plugin |
Interface Control Document of the default WS plugin (pdf) | This document describes the WSDL and the observable behaviour of the interface provided in the default WS plugin |
Administration Guide (pdf) | The purpose of this guide is to provide detailed information on how to deploy and configure Domibus on WebLogic, Tomcat and WildFly with MySQL and Oracle. It also provides detailed descriptions of related Security Configurations (Policies, Certificates, TLS Configuration), Message Filtering, PMode Configuration, Application Monitoring, Registration of custom plugins and Troubleshooting. |
Plugin cookbook (implementation manual) (pdf) | After reading this document the reader should be aware of the capabilities provided by the Domibus plugin system. Additionally a developer familiar with the AS4 protocol will be able to implement a plugin integrating an existing back office application into Domibus |
Domibus Software Architecture Document (pdf) | This document provides a comprehensive architectural overview of the system, using a number of different architectural views to depict individual aspects of the system. It is intended to capture and convey the significant architectural decisions that have been made on the system |
Licence (pdf) | European Union Public Licence |
Migration from 3.2.2 to 3.2.3
In order to upgrade to Domibus 3.2.3 replace the domibus.war in the appropriate deployment folder and the plugin(s) jar(s) into \domibus\conf\domibus\plugins\lib". Since the installation of the plugin(s) has been simplified and it is straightforward just copy the jar in the plugin folder.
For more about the Domibus configuration updates click here.
PS: for upgrades from other releases please refer to previous release notes and in case case to the updated upgrade-info.txt file.
Release note
Please find below the list of the solved bugs and improvements.
Bugs
[EDELIVERY-1763] - Domibus-MSH-3.2.X - Standalone Single Server Installation on Tomcat: Missing domibus-plugins.xml file
[EDELIVERY-1802] - listPendingMessages does not return the entire list of pending messages in a cluster (Weblogic) environment
[EDELIVERY-1992] - Domibus Core - Specify persistence unit name for entity manager and refactor persistence unit configuration
[EDELIVERY-2018] - The MSH web service endpoint should respond with 200 for the GET method
[EDELIVERY-2021] - Domibus does not sign the empty AS4 body
[EDELIVERY-2039] - ListPendingMessagesRequest return only messages from one queue
[EDELIVERY-2055] - The file setenv.sh from Tomcat full distribution contains windows line cariages
Known issues and limitations
[EDELIVERY-1375] - RedeliveryPolicy is not taken into account in ActiveMQ
[EDELIVERY-1547] - MessageID: special characters handling
[EDELIVERY-1548] - Download Message special characters
[EDELIVERY-1554] - Message ID case sensitivity
[EDELIVERY-1555] - Message parameters case sensitivity
[EDELIVERY-1561] - domibus-backend.xsd violates Unique Particle Attribution
[EDELIVERY-2082] - Error when trying to download a message with an empty payload
[EDELIVERY-2085] - Backwards compatibility is broken for the Default WS plugin
[EDLIVERY-973] Sending a message to yourself is forbidden
For more information, please contact us via our portal or by e-mail: CEF-EDELIVERY-SUPPORT@ec.europa.eu