Domibus v3.3.2 (bug fix)
This page collects the resources for Domibus version 3.3.2, released in March 2018.Description
We are happy to announce the bug fix release of the production-ready Domibus 3.3.2 sample implementation of the eDelivery Access Point.
The Domibus 3.3.2 includes a number of bug fixes and a couple of improvements concerning:
- Message log improvements
- Fixed a bug related to the missing metadata when receiving messages using the FS Plugin
- Added an SQL script for deleting Domibus messages
- Tomcat: fixed a bug in the WS Plugin listPendingMessages operation when having more than 400 messages in the queue
Domibus 3.3.2 is backwards compatible with 3.3.1 and 3.2.x and the upgrade is not mandatory.
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. |
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. |
Licence (pdf) | European Union Public Licence. |
Migration from 3.3.1 to 3.3.2
In order to upgrade to Domibus 3.3.2 it is necessary to run the SQL migration script, which depends on the DB vendor used.
Several properties need to be added in the domibus.properties configuration file and the logback configuration needs to be adapted.
Afterwards 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.
Release note
Please find below the list of improvements, new features and solved bugs.
Improvements
- [EDELIVERY-2315] - Deletion Script for Domibus database
- [EDELIVERY-2828] - Log a warning when the certificate of the sender and receiver is about to expire
- [EDELIVERY-2995] - Log every message status change
- [EDELIVERY-2996] - Log the unsuccessful login attempts
- [EDELIVERY-2997] - Log the size of the payloads
- [EDELIVERY-3071] - Message log improvement: the message ID should be present for all status changes
- [EDELIVERY-3072] - Message log improvement: when message is being acknowledged, the message ID in log entry is different than ID of send message
- [EDELIVERY-3075] - Message log improvement: there are less log entries for BUS-048 than log entries for BUS-063
Fixed Bugs
- [EDELIVERY-2908] - Metadata not available/received when using FS Plugin
- [EDELIVERY-3010] - Remove fs plugin files prevents domibus from starting.
- [EDELIVERY-3076] - Two BUS-048 entries in logs for deleting the message
- [EDELIVERY-3089] - After 400+ message sent next message can't be retrieved
- [EDELIVERY-3091] - [ LOGGED_MARKER ] string injected in business.log
- [EDELIVERY-3108] - Messages retry mechanism (retryWorkerJob) not working properly when DB sysdate is in the past
- [EDELIVERY-3124] - Not all bussiness.log entries contains information about message ID
- [EDELIVERY-3125] - Duplication of logs for wildfly business.log
- [EDELIVERY-3208] - WildFly: The Send and the Pull queues should be configured with no retry
Known issues and limitations
- [EDELIVERY-3213] - Case sensitivity different between pmode dao implementations
- [EDELIVERY-1548] - Download Message special characters
- [EDELIVERY-2608] - Unable to use Admin Console in IE (not EDGE)
- [EDELIVERY-2760] - LDAP CRLs are not supported
- [EDELIVERY-1561] - domibus-backend.xsd violates Unique Particle Attribution
- [EDELIVERY-973] - Sending a message to yourself is forbidden
- [EDELIVERY-3213] - Case sensitivity different between pmode dao implementations
- [EDELIVERY-3210] - Max retry limit may be exceeded on Wildfly 9.
- [EDELIVERY-3374] - Empty Lines in Oracle SQL Upgrade Script causes script failure
For more information, please contact us via our portal or by e-mail: CEF-EDELIVERY-SUPPORT@ec.europa.eu