Domibus v3.2.2
This page collects the resources for Domibus version 3.2.2, released in February 2017.
Access the Domibus eLearnings
Description
We are happy to announce the bug fix release of the production-ready Domibus 3.2.2 sample implementation of the eDelivery Access Point.
Domibus 3.2.2 new release includes a number of bug fixes and a couple of improvements concerning:
Notifications sent by the JMS plugin
JMS monitoring messages search
Configuration properties (ConnectionTimeout and ReceiveTimeout) to fine tune access points' conduit.
Possibility to configure the limit of downloaded/not-downloaded messages of the Domibus Retention Worker
- CXF attachment temporary files are now correctly cleaned. This is very important for BE systems exchanging large payloads messages.
- Implementation of AS4 access point dynamic discovery.
Domibus 3.2.2 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.1 to 3.2.2
In order to upgrade to Domibus 3.2.2 it is necessary, first of all, to run the right migration script, which depends on the DB vendor used.
Afterwards, 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.
To use the Dynamic Discovery drop conf/domibus/policies/eDeliveryPolicy_CA.xml into conf/domibus/policies configuration folder.
For more about the Domibus configuration updates click here.
PS: for upgrades from other releases please refer to previouses 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-1493] - Error while deleting messages in the MessageRetentionService
[EDELIVERY-1684] - JMS plugin: the message Id should always be present in the messages sent
[EDELIVERY-1686] - The message receive failure notifications are not sent
[EDELIVERY-1687] - Modify the default JMX password used in the WLST API scripts
[EDELIVERY-1706] - [Domibus] JMS Monitoring: messages are not displayed
[EDELIVERY-1731] - CXF attachment temporary files leakage
[EDELIVERY-1855] - Retention time issue
[EDELIVERY-1858] - "pModeProvider" value for Dynamic discovery.
[EDELIVERY-1925] - Downloading message fails when the file storage and retention time=0 is used
Improvements
[EDELIVERY-1721] - HTTPClientPolicy: the connection and the receive timeout are hard coded
[EDELIVERY-1737] - Fix Domibus integration with SMP/SML
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-1542] - Add message DOWNLOADED status to API and MSH
[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