1. Current release
This page collects the resources for Domibus version 4.0.1, released in December 2018.
We are happy to announce the bug fix release of the production-ready Domibus 4.0.1 sample implementation of the eDelivery Access Point.
Domibus 4.0.1 version includes a number of bug fixes and a couple of improvements concerning:
Add possibility to exclude a protocol from the CRL list
WebLogic cluster: fixed the PMode and truststore refresh with the WebLogic cluster
Fixed submitting of messages via the Default JMS Plugin in Multitenancy mode
Improved logging for Multitenancy
Add email alert support for super user login failure and account disabled
Fix the retry issue for restored messages
Increase to 5 minutes the transaction timeout of ListPendingMessages operation in the Default WS Plugin
Add configurable property for AS4 transport profile in the dynamic discovery process
Fixed the Peppol dynamic discovery
Allow empty "ConversationID" in the message sent by C1
Support ofr LDAP CRLs
Fix the Unique Particle Attribution violations in the Default WS Plugin
Domibus 4.0.1 is backwards compatible with 4.0 and 3.3.x and the upgrade is not mandatory.
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.
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.
The purpose of this document is to outline the JMS Data Format Exchange to be used as part of the default JMS backend plugin.
This document describes the WSDL and the observable behaviour of the interface provided in the default WS plugin.
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.
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.
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.
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.
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.
Documentation on the REST services.
European Union Public Licence.
Migration from 4.0 to 4.0.1
In order to upgrade to Domibus 4.0.1 it is necessary to run the SQL migration script, which depends on the DB vendor used. For Multitenancy mode, please use the provided SQL script to update the general database schema.
Afterwards please update the domibus.properties file, install the domibus.war and replace the plugin(s) jar(s) into \domibus\conf\domibus\plugins\lib".
For a more detailed description of the Domibus upgrade procedure click here.
Please find below the list of improvements and fixed bugs.
[EDELIVERY-3768] - Alerts management for super users
[EDELIVERY-3921] - JTA transaction timeout for more than 7900 messages in the pending messages queue
[EDELIVERY-3926] - PMode and Truststore update not working properly on a WebLogic cluster
[EDELIVERY-3930] - SQL script error on MySQL 5.6 and lower
[EDELIVERY-3938] - Fix - Segregate the Domibus logs per domain
[EDELIVERY-3940] - Messages are not displayed when originalSender and finalRecipient are not present in the message
[EDELIVERY-3942] - Allow empty "ConversationID" in the message sent by C1
[EDELIVERY-3953] - Message stuck in WAITING_FOR_RETRY state
[EDELIVERY-3983] - Imminent certificate alert send on each job execution
[EDELIVERY-3984] - RetrieveMessage displays the full file path of payload in PartInfo
[EDELIVERY-3988] - Alert stuck in SEND_ENQUEUED state
[EDELIVERY-4032] - Tomcat with Oracle DB: Default JMS Plugin is not working in multi-tenancy
[EDELIVERY-4058] - Possibility to exclude a protocol from the CRL list
[EDELIVERY-4061] - Unable to change log level on a specific tenant
[EDELIVERY-4081] - Delete-db and multi-tenancy-rights are not present in the distribution
[EDELIVERY-4119] - Binary token missused when validating sender certificate
[EDELIVERY-4123] - Transport profile should be configurable for the dynamic discovery peppol client
[EDELIVERY-4136] - Alerts emails sending fails with "invalid email address configured for the alert module" errors
[EDELIVERY-4173] - Fixed the parsing of service and action values in case of Peppol dynamic discovery
[EDELIVERY-3925] - More information on Alerts email
Known issues and limitations
[EDELIVERY-2608] - Unable to use Admin Console in IE (not EDGE)
[EDELIVERY-3210] - Max retry limit may be exceeded on Wildfly 9
[EDELIVERY-3335] - Messages page: performance decrease when certain filters are applied on millions of messages
[EDELIVERY-3575] - UI admin console: user is logged out when logging-in in another tab
[EDELIVERY-3634] - Issue starting Tomcat/WildFly cluster the first time with an empty MySQL schema