Domibus 5.1.2
Description
We are happy to announce the release of Domibus 5.1.2 sample implementation of the eDelivery Access Point.
The Domibus 5.1.2 release includes a number of new features, improvements, and bug fixes:
- Optimise HQL queries by eliminating unnecessary cross joins, resulting in enhanced overall performance.
- Users can now update the truststore with varying types and passwords, increasing adaptability.
- Enhancements in the dynamic discovery process contribute to a more stable and reliable operation
- Added support for dynamic discovery wildcard search
- Relaxed the restriction of service and action values validation in message filter creation
- Added properties domibus.pmode.validation.action.pattern and domibus.pmode.validation.service.value.pattern to validate action and service when updating a pMode
- External API to get certificate of the party returns a ResponseEntity of TrustStoreDTO as per the OAS specification
- New worker which reschedules unsent messages stuck in SEND_ENQUEUED and WAITING_FOR_RETRY statuses
- New worker which reschedules eArchive batches stuck in STARTED statuses
- Cache configuration for extensions can be done using default ehcache file *-extension-default-ehcache.xml. The expected location (in a Java project) is: /src/main/resources/config/ehcache/*-extension-default-ehcache.xml which will go to .jar file of the extension into e.g. /config/ehcache/ext1-extension-default-ehcache.xml location
- Cache configuration for extensions can be overridden by a configuration file named *-extension-ehcache.xml (e.g ext1-extension-ehcache.xml) added to /conf/domibus/extensions/config/
- Moved dss-cache in /extensions/config/dss-extension-ehcache.xml
- Removed domibus cache statistics duplicates from JMX consoles
- Upgraded Tomcat 9 to the latest version 9.0.83
- This version includes library upgrades to mitigate known vulnerabilities, enhancing system security.
Domibus 5.1.2 is backward compatible with 5.1.1 and 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 8u291+: tested to run correctly with:
- Oracle JDK 8u291+ for WebLogic, Tomcat and WildFly
- OpenJDK 11.0.11 for WildFly and 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 plugin (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 |
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. |
Upgrade from 5.1.1 to 5.1.2
For a detailed description of the Domibus upgrade procedure, click here.
Release notes
Please find below the list of new features, improvements, and solved bugs.
New features
- [EDELIVERY-12156] Dynamic discovery client wildcard search support
- [EDELIVERY-12069] Dynamic discovery: certificate imminent expiration should not be triggered for certificates added dynamically
Improvements
[EDELIVERY-12099] Domibus upload truststore with different type and/or password
[EDELIVERY-12154] Move the DSS modules outside of Domibus into a dedicated repository
[EDELIVERY-12428] Move SQL scripts outside of Domibus into a dedicated repository with its own versioning scheme
[EDELIVERY-12411] Replace the term migration with upgrade
[EDELIVERY-12517] Activate container scanning for Docker images released in Production
[EDELIVERY-12286] Stop the execution of the SQL migration scripts when an error is encountered
[EDELIVERY-12287] Do not run the migration script if the previous version is not correct
[EDELIVERY-12383] Harmonise Domibus usage of caches
[EDELIVERY-12295] Remove cross joins with dictionary to improve performance
[EDELIVERY-12353] Service and action values in the Message Filter is too restrictive
Fixed bugs
EDELIVERY-12575] Signal message for pulled user message not stored in the database
[EDELIVERY-12154] WS Plugin authenticated push notification
[EDELIVERY-12509] MPC retention_sent query returns duplicate results for the number of messages to delete
[EDELIVERY-12642] Domibus might block when updating the truststore and keystore
[EDELIVERY-10507] Cache the X509CRL response to avoid multiple downloads of the same CRL
[EDELIVERY-12039] PKCS12 keystores broken when using Java 11
[EDELIVERY-12117] Domibus Wildfly Java11 exceptions during startup
[EDELIVERY-12191] Infinispan persistence warnings cause build LOAD Tomcat9(MySQL8)-Wildfly26(MySQL8) to fail
[EDELIVERY-12253] Messages on-the-wire during server shutdown remain in status SEND_ENQUEUEDED
[EDELIVERY-12260] The payload extension for a downloaded sent message is wrong
[EDELIVERY-12394] Add primary keys on tables missing the primary keys
[EDELIVERY-12413] Earchiving batches being generated during server shutdown remain in status STARTED
[EDELIVERY-12548] Error when running upgrade script to 5.0.5/5.0.8
[EDELIVERY-12550] AgreementRef missing type validation
[EDELIVERY-12552] Issue with crl caching feature
[EDELIVERY-12560] "DELETED_BATCH" notification is not pushed to the backend
[EDELIVERY-12582] Expired partition is not dropped
[EDELIVERY-12586] Domibus and DSS 5.1.2 should use only one version of Bouncy Castle
[EDELIVERY-12595] Caching crl by certificate doesn't seem to work
[EDELIVERY-11081] Plugin user appears in CREATED_BY column of table tb_user_message
[EDELIVERY-12196] Remove cross join with message status dictionary to improve performance
[EDELIVERY-12401] Upgrade ActiveMQ to a non vulnerable version
[EDELIVERY-12430] MessageEntityId is not present in the events from Domibus to plugins
[EDELIVERY-12570] NullPointerException when fetching metadata with an empty certificate value
- [EDELIVERY-12615] Basic128GCMSha256 algorithm suite in policy XML files
[EDELIVERY-12638] Test service fails to identify process to be used
[EDELIVERY-12231] Fix NumberFormatException for property domibus.ui.pages.messageLogs.interval.default
[EDELIVERY-12237] Wrong status code when trying to upload a file bigger than maximum size in API
[EDELIVERY-12494] The payload file name is not transmitted from C1 to C4 via JMS plugin
[EDELIVERY-12120] Inaccuracy in readme.md files of ws-plugin and jms-plugin
EDELIVERY-12211] Updating Domibus AG with AMQ clustering
[EDELIVERY-12245] WS Plugin ICD Document update markAsDownloaded
Known issues and limitations
- [EDELIVERY-10985] - Exception shown in Wildfly logs at startup
[EDELIVERY-11290] - Domibus loggers are created only when writing the first log message
[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