Domibus 5.0.2
Description
We are happy to announce that the release of Domibus 5.0.2 is available. Domibus is the sample implementation of an eDelivery Access Point maintained by the European Commission.
Domibus 5.0.2 includes a number of improvements and bug fixes, among which:
- Possibility to have a separate logs containing all errors
- Fixed issue related to wrong final recipient used when using dynamic discovery in a cluster environment
- Fixed issue with partitions with failed messages not dropped when eArchiving is enabled
- Authorisation headers added for WS push plugin notifications
- Timer added in order to load drop wizard queue metrics after application initialisation
- Fixed broken functionality of message prioritisation on Weblogic and Tomcat
- Default value of domibus.metrics.monitor.jms.queues.refresh.period changed to 10
- Fixed the disabling of a domain added at runtime
- PUSH notifications type RECEIVE_FAIL and SEND_FAILURE are not working
- Fixed migration scripts for ongoing messages between 5.0 and 5.0.1 for Split & Join
- Fixed Oracle delete script inconsistent with table structure
- Analysed and fixed OWASP reported security vulnerabilities
Important note: there is a known issue on the Domibus 5.0.2 version with the reload keystore functionality: due to a caching issue in the reload keystore functionality, Domibus requires restart when changing the keystore.
The steps to replace the keystore are:
- change the keystore file on the disk
- press ReloadKeystore in Domibus Admin Console - the new keystore will be visible in the UI but not used for exchanging messages
- restart Domibus (to be fixed in next hotfix release)
Domibus 5.0.2 is backward compatible with 5.0.1and the upgrade is not mandatory, but it is highly recommended.
Supported platforms:
- Application servers:
- WildFly 26.1.x
- WebLogic 12.2.1.4 (tested version, future versions might work)
- Apache Tomcat 9.0.x
- Database:
- MySQL 8 (future versions might work)
- Oracle 12c R2 and Oracle 19c
- Java 8 features / compile with Oracle JDK 8: tested to run correctly with:
- Oracle JDK 8/ WebLogic
- OpenJDK 11/ WildFly + Tomcat (tested with AdoptOpenJDK 11 version 11.0.9.1+1)
Security Note: To ensure their system’s security, users installing any of the Domibus packages labelled as “Full Distribution” have the responsibility to update the application servers to the latest version after the installation.
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 (new) WS plugin (pdf) | This document describes the WSDL and the observable behaviour of the interface provided in the default WS plugin. |
Interface Control Document of the default (old) WS plugin (pdf) | This document describes the WSDL and the observable behaviour of the interface provided in the default WS plugin. |
Interface Control Document of the File System plugin (pdf) | The purpose of this document is to outline the file system messages exchange as part of the default File System (FS) backend integration solution for the Domibus Access Point. |
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. |
File System Plugin Administration Guide (pdf) | The purpose of this guide is to provide detailed information on how to configure and deploy the File System Plugin available in Domibus 3.3 and later versions. |
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. |
Extension cookbook (pdf) | This document details the technical specifications of Domibus extension mechanism. It lays out applicable guidelines to support the technical implementation of an extension. |
Validation extension cookbook (pdf) | This document details the technical specifications of Domibus Validation Extension mechanism. Its scope are the functional aspects of the extension mechanism and the technical and operational aspects of the extension mechanism. |
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. |
Domibus REST services documentation | Documentation on the Domibus REST services. |
Domibus eArchiving REST services documentation | Documentation on the Domibus eArchiving REST services. |
Licence (pdf) | European Union Public Licence. |
Domibus upgrade and downgrade procedure | The purpose of this document is to describe the details of making a backup of Domibus and restore Domibus previous version if it is needed. |
Migration from 5.0.1 to 5.0.2
For a detailed description of the Domibus upgrade procedure, click here.
Release notes
Please find below the list of new features, improvements, solved bugs and known limitations.
Improvements
- [EDELIVERY-9218] - Domibus 5.0-RC1 PUSH notification type SEND_FAILURE not working
Fixed bugs
- [EDELIVERY-10187] - Possibility to have a separate log containing all errors
- [EDELIVERY-10221] - Wrong final recipient is used when using dynamic discovery in a cluster environment
- [EDELIVERY-10295] - Domibus 5.0.1 data migration errors from 4.2.11
- [EDELIVERY-10308] - Port the drop wizard fix into Domibus 5.0.2
- [EDELIVERY-10309] - Partitions with failed messages are not dropped, when earchiving is enabled
- [EDELIVERY-10187] - Missing authorization headers for WS push plugin notifications
- [EDELIVERY-9773] - Fix OWASP vulnerabilities
- [EDELIVERY-10337] - Message Prioritization Functionality Broken in v5.0.1 for Weblogic and Tomcat
- [EDELIVERY-10227] - Performance issue when setting the domain on the context
- [EDELIVERY-10339] - PUSH notifications type RECEIVE_FAIL and SEND_FAILURE are not working
- [EDELIVERY-9458] - Fix migration scripts ongoing messages between 5.0 and 5.0.1 for Split & Join
- [EDELIVERY-10232] - Oracle delete script inconsistent with table structure
- [EDELIVERY-10396] - Monitoring option is always enabled for the different sender and receiver party
Known issues and limitations
- [EDELIVERY-10460] - Reload key issue: due to a caching issue in the reload keystore functionality, Domibus requires restart when changing the keystore.
- [EDELIVERY-12591] - When running the partitions scripts on Oracle 19.19 and higher, error is encountered and partitions are not created
For more information, please contact us via our portal or by e-mail: EC-EDELIVERY-SUPPORT@ec.europa.eu