Services
Domibus 4.1.5
Description
We are happy to announce the release of Domibus 4.1.5 sample implementation of the eDelivery Access Point.
The Domibus 4.1.5 contains a number of bug fixes, including:
Filtering by JMS selector using JMSTimestamp property as string should throw error
Nothing appears in the logs when filtering JMS messages in JMS Monitoring page
Domibus: print payload=false doesn't strip payload for retrieveMessage operation
Domibus - JMS Plugin in Dynamic Scenario
User field data gets overwritten on Audit page in case of Message resend event
Proxy does not work when password is encrypted
Issue on MySQL script: Columns from TB_CERTIFICATE and TB_SEND_ATTEMPT tables are TIMESTAMP instead of DATETIME
Domibus 4.1.2 and 4.1.3 does not use BouncyCastle provider in WebLogic
Domibus prints the message id in the logs after message is not being used
Domibus sends password expired alerts for plugin users despite password expiration is disabled
Multiple clients concurrently requesting messages from the Default WS Plugin leads to duplicate messages
Mapping several legs to an mpc failing when the leg does not have payload profile
Domibus does not log hibernate messages on Weblogic and Wildfly server if Hibernate loggers are set to 'debug' or 'trace' level
JMS event in DLQ
Logging more information for EbMS3Exception
Encrypted proxy password
Quartz triggers sometimes get blocked
Add a maxSize limit when setting property values at runtime
Domibus 4.1.5 is backwards compatible with 4.1.x and the upgrade is not mandatory.
Please use FS Plugin 4.1.3 instead of 4.1.5.
Supported platforms:
Application servers:
WildFly 12
WebLogic 12.1.3 and 12.2.1.3 (tested version, future versions might work)
Apache Tomcat 8.5.xDatabase:
MySQL 5.6 or above
Oracle 12c (tested version, future versions might work)JAVA:
Oracle JRE8
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. |
REST services documentation | Documentation on the REST services. |
Licence (pdf) | European Union Public Licence. |
Migration from 4.1.3 to 4.1.5
In order to upgrade to Domibus 4.1.5 please execute the SQL migration script, which depends on the DB flavor used. For multi-tenancy 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.
Release note
Please find below the list of improvements and fixed bugs.
Fixed Bugs
[EDELIVERY-5563] - Filtering by JMS selector using JMSTimestamp property as string should throw error
[EDELIVERY-5564] - Nothing appears in the logs when filtering JMS messages in JMS Monitoring page
[EDELIVERY-6200] - Domibus: print payload=false doesn't strip payload for retrieveMessage operation
[EDELIVERY-6305] - Domibus - JMS Plugin in Dynamic Scenario
[EDELIVERY-6338] - User field data gets overwritten on Audit page in case of Message resend event
[EDELIVERY-6345] - Proxy does not work when password is encrypted
[EDELIVERY-6377] - Issue on MySQL script: Columns from TB_CERTIFICATE and TB_SEND_ATTEMPT tables are TIMESTAMP instead of DATETIME
[EDELIVERY-6380] - Domibus 4.1.2 and 4.1.3 does not use BouncyCastle provider in WebLogic
[EDELIVERY-6395] - Domibus prints the message id in the logs after message is not being used
[EDELIVERY-6401] - Domibus sends password expired alerts for plugin users despite password expiration is disabled
[EDELIVERY-6403] - Multiple clients concurrently requesting messages from the Default WS Plugin leads to duplicate messages
[EDELIVERY-6413] - Mapping several legs to an mpc failing when the leg does not have payload profile
[EDELIVERY-6482] - Domibus does not log hibernate messages on Weblogic and Wildfly server if Hibernate loggers are set to 'debug' or 'trace' level
[EDELIVERY-6490] - JMS event in DLQ
[EDELIVERY-6523] - EbMS3Exception: logging more information
[EDELIVERY-6739] - Encrypted proxy password.
[EDELIVERY-6930] - Quartz triggers sometimes gets blocked
[EDELIVERY-6746] - Add a maxSize limit when setting property values at runtime
Improvements
[EDELIVERY-6856] - Increase size limit for AS4 message properties, and document default limits
Known issues and limitations
[EDELIVERY-2608] - Unable to use Admin Console in IE (not EDGE)
[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
[EDELIVERY-3250] - Improve sending a message to the same Access Point
For more information, please contact us via our portal or by e-mail: CEF-EDELIVERY-SUPPORT@ec.europa.eu