Domibus 5.1.1
Description
We are happy to announce the release of Domibus 5.1.1 sample implementation of the eDelivery Access Point.
The Domibus 5.1.1 release includes a number of new features, improvements, and bug fixes, including:
- Removed the SQL scripts from the full distributions of Tomcat and Wildfly. The archive with these scripts can be downloaded separately
- Removed property domibus.fourcornermodel.enabled and add properties domibus.ui.pages.messageLogs.landingPage.enabled
- Updated all the domibus.UI.title.name domain property names to domibus.ui.title.name
- Updated all the property names prefixed with domibus.metrics.sl4j to domibus.metrics.slf4j
- Fixed the dynamic discovery mechanism for a high concurrency scenario
- Dynamically discovered certificates are deleted after their retention period expire
- Possibility to change the second level cache provider, choosing between Infinispan (default) and Ehcache
- Maximum number of upload file size is global
- Improve performance of the Messages page
- eArchiving batches are deleted immediately after being archived
- Fix OWASP vulnerabilities
Domibus 5.1.1 is backward compatible with 5.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 (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. |
Migration from 5.1 to 5.1.1
In order to upgrade to Domibus 5.1.1, please follow the steps:
Replace the Domibus war and the default plugin(s) config file(s), property file(s) and jar(s)
Replace the default dss extension jar into "/domibus/conf/domibus/extensions/lib"
Run the appropriate DB upgrade script (mysql-5.1-to-5.1.1-upgrade.ddl for MySQL or oracle-5.1-to-5.1.1-upgrade.ddl for Oracle)
Remove property domibus.fourcornermodel.enabled if configured
In all eDeliveryAS4Policy xml files, the hardcoded algorithm suite name defined in AsymmetricBinding/Policy/AlgorithSuite/ (e.g Basic128GCMSha256MgfSha256) was replaced with the placeholder: ${algorithmSuitePlaceholder} which will be automatically replaced in code according to the security setup
Replace/update all policy files that have the AsymmetricBinding/Policy/AlgorithSuite tag defined(e.g. eDeliveryAS4Policy.xml, eDeliveryAS4Policy_BST.xml, eDeliveryAS4Policy_BST_PKIP.xml,eDeliveryAS4Policy_IS.xml, signOnly.xml etc.) to accomodate this change
The policy xml config files can be found in the Domibus distribution inside the file domibus-msh-distribution-5.1.1-application_server_name-configuration.zip under the folder /policies or inside the file domibus-msh-distribution-5.1.1-application_server_name-full.zip under the folder domibus/conf/domibus/policies
Update all the domibus.UI.title.name domain property names to domibus.ui.title.name
Update all the property names prefixed with domibus.metrics.sl4j to domibus.metrics.slf4j
For a more detailed description of the Domibus upgrade, procedure click here.
Release notes
Please find below the list of new features, improvements, and solved bugs.
Improvements
[EDELIVERY-12049] Improve performance of the Messages page
[EDELIVERY-12051] Modify the admin console search
[EDELIVERY-11903] FinalRecipient cache mechanism used for dynamic discovery should be updated
[EDELIVERY-12066] Dynamic discovery: discovered parties should be saved in database
[EDELIVERY-12064] Dynamic discovery: discovered parties should be cleaned up based on a retention period
[EDELIVERY-12190] Batch is deleted immediately after being archived.
Fixed bugs
[EDELIVERY-11568] Domibus 5.0.5 sql-scripts are overlaping 5.1 scripts
[EDELIVERY-11825] Domibus parties mixing between separate domains/tenants
[EDELIVERY-11853] Payload submission is working only when compression is not active in the Pmode
[EDELIVERY-12013] Errors are generated in the logs when exchanging successfully messages.
[EDELIVERY-12194] Backward compatibility issue for Domibus 5.1.1 with 5.0 default plugins.
[EDELIVERY-12203] User is not getting created.
[EDELIVERY-12210] WS push notifications: issue with DELETED and DELETED_BATCH notifications.
[EDELIVERY-11322] [EOONBOARDING] - EBMS error description to be redefined
[EDELIVERY-11748] Dynamic discovery cache is too long
[EDELIVERY-11782] Domibus unable to send messages via fsplugin after a disabled domain is re-enabled again.
[EDELIVERY-11848] Fix performance issue when S&J job is activated
[EDELIVERY-11916] Tomcat data source configuration set minimumIdle as milliseconds
[EDELIVERY-11927] The maximum number of upload file size is global
[EDELIVERY-12045] DSS custom list not verified
[EDELIVERY-12054] Domibus application denies to save setup changes from web console
[EDELIVERY-11781] Remove SQL scripts from the full distributions
[EDELIVERY-12055] Authentication errors in console should be logged with WARN instead of INFO
[EDELIVERY-11799] Update mysql:mysql-connector-java to com.mysql:mysql-connector-j
[EDELIVERY-11887] Error in the upgrade procedure from 5.0.6 to 5.1
[EDELIVERY-12155] Update Ws Plugin Client
[EDELIVERY-11898] listPendingMessages shows also the downloaded message
[EDELIVERY-12081] Retention - Keep the newest partition instead of the oldest one
[EDELIVERY-12098] Fix performance issue for eachiving related to file digest
[EDELIVERY-12100] Add primary keys on tables missing the primary keys
[EDELIVERY-12115] Errors shown in the logs when starting Domibus
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
For more information, please contact us via our portal or by e-mail: EC-EDELIVERY-SUPPORT@ec.europa.eu