eDelivery Services
Domibus 4.2.2
Description
We are happy to announce the release of Domibus 4.2.2 sample implementation of the eDelivery Access Point.
The Domibus 4.2.2 release includes a number of improvements and bug fixes, including:
REST endpoint for resending failed messages is not stable
Add http timeout for certificate CRL download
Under certain conditions, messages remain in SEND_ENQUEUED status
Fixed an issue in the File System Plugin expired cron expression
Possibility to resend in batch messages stuck in SEND_ENQUEUED status
NullPointer for default delete message mechanism for messages in SEND_FAILURE
Upgraded several libraries
Domibus 4.2.2 is backward compatible with 4.1.x versions.
Supported platforms:
Application servers:
WildFly 20.0.x
WebLogic 12.2.1.4 (tested version, future versions might work)
Apache Tomcat 9.0.xDatabase:
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)
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 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. |
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. |
REST services documentation | Documentation on the REST services. |
Licence (pdf) | European Union Public Licence. |
Migration from 4.2.1 to 4.2.2
In order to upgrade to Domibus 4.2.2, please follow the steps:
execute the SQL migration script, depending on the DB flavor used. For multi-tenancy mode, please use the specific SQL script to update the general database schema.
update the domibus.properties file;
install the domibus.war;
replace the plugins jars into "domibus/conf/domibus/plugins/lib"
For a more detailed description of the Domibus upgrade, procedure click here.
Release note
Please find below the list of new features, improvements, and solved bugs.
Improvements
[EDELIVERY-8031] - REST endpoint implemented to resend a batch of messages stuck in SEND_ENQUEUED status.
Fixed Bugs
[EDELIVERY-7960] - Domibus Parties configuration unstable because PMode had the same content even though the “Parties” section was changed automatically by Domibus
[EDELIVERY-8144] - JMS plugin messageType=submitResponse does not send errors when the wrong final recipient is used
[EDELIVERY-7962] - REST endpoint for resending failed messages is not stable. It depends on environment and number of messages resent
[EDELIVERY-7978] - Signal message is missing from TB_MESSAGING table when message is in status SEND_FAILURE
[EDELIVERY-8000] - Swagger - SEND_FAILURE Messages. The GET operation using urn:oasis:names:tc:ebcore:partyid-type:unregistered:C4 as finalRecipient returns only test messages and no user_messages
[EDELIVERY-8003] - Message remain in SEND_ENQUEUED status
[EDELIVERY-8033] - Long database Object names in Oracle DB
[EDELIVERY-8072] - fsplugin.messages.received.purge.expired does not handle the "empty string" setting (=)
[EDELIVERY-8139] - Warning in upgrade script from 4.2.1 to 4.2.2 (mysql-4.2.1-to-4.2.2-migration.ddl)
Known issues and limitations
[EDELIVERY-2608] - Unable to use Admin Console in Internet Explorer (not EDGE)
[EDELIVERY-3575] - UI admin console issue: user is logged out when logging-in in another tab
[EDELIVERY-3250] - Improve sending a message to the same Access Point
[EDELIVERY-3335] - Performance decreases when some filters are applied to millions of messages
For more information, please contact us via our portal or by e-mail: CEF-EDELIVERY-SUPPORT@ec.europa.eu