Domibus v3.2
This page collects the resources for Domibus version 3.2, released in October 2016
Access the Domibus eLearnings
Description
We are happy to announce the release of the production-ready Domibus 3.2 sample implementation of the eDelivery Access Point.
As with previous releases, the Domibus 3.2 sample implementation has been achieved only by close collaboration between different EU policy projects' IT delivery teams and CEF eDelivery.
The Domibus 3.2 new release includes a number of improvements (some contained also in the Domibus 3.2 Release Candidate 1), including:
- PMode file validation during the upload
- Security on the default plugins
- Improved JMS management with Dead Letter Queues
- Added support for JMS monitoring
- Harmonisation of the plugin registration across the supported application servers (Weblogic 12c, Tomcat 8, Wildfly 9)
- Additional quality controls on the default web service plugin
- Facilitation of adding new participants thanks to the upload of the truststore from the administration console
- Implementation of CRL (Certificate Revocation List) checks
- Support for JDK 8
In addition, since the latest stable release Domibus 3.2 RC1, debugging and issue-solving has taken place.
However, Domibus 3.2 is backwards compatible with 3.1.x and the upgrade is not mandatory. PMode configuration files that were designed for Domibus 3.1.x can also be used in Domibus 3.2.
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 |
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. |
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.1.1 to 3.2
In order to upgrade to Domibus 3.2 it is necessary, first of all, to run the right migration script, which depends on the DB vendor used.
Afterwards, replace the domibus.war in the appropriate deployment folder and the plugin(s) jar(s) into \domibus\conf\domibus\plugins\lib". Since the installation of the plugin(s) has been simplified and it is straightforward (just copy the jar in the plugin folder), it is not necessary to modify the war anymore (this was the case only for WebLogic and for WildFly) .
For Tomcat installations only, the activemq.xml has to be replaced and re-configured according to your environment (transportConnector uri, authenticationUser, redeliveryPolicy).
If the samples keystores are being used, mind that they have been changed because the old ones included in 3.1.1 expire on the 26th of October 2016.
For more about the Domibus configuration updates click here.
PMode updates
1. Now the PMode is validated during the upload. Warning messages will be displayed and you are encouraged to fix the issues (in your PMode file).
2. This configuration <process name="tc1Process" agreement="agreementEmpty"… > will not be supported anymore in the next releases.
Please check your PMode file and whenever you don't use any agreementRef value in your messages, just remove the agreement attribute or leave it blank.
Please check the new PMode samples for the appropriate configuration.
Release note
Please find below the list of the improvements and new features implemented and the solved bugs.
Improvements
- [EDELIVERY-985] - Remove the generated jaxb classes of the domibus-ws-plugin
- [EDELIVERY-1077] - Remove generic data type <T> in MessageSubmitter / MessageRetriever
- [EDELIVERY-1121] - Distribute the WebLogic/WildFly plugin configuration for the default WS/JMS plugin
- [EDELIVERY-1133] - Adding new participants should be easier - upload certificates
- [EDELIVERY-1172] - Add the Weblogic WSLT scripts to the weblogic-configuration.zip
- [EDELIVERY-1177] - Integration tests should be run by the failsafe plugin in the integration-tests phase
- [EDELIVERY-1183] - Harmonize the plugin management on Tomcat/WebLogic/WildFly
- [EDELIVERY-1264] - When receving the AS4 message add the possibility to perform a validation
- [EDELIVERY-958] - Security on the default plugins
- [EDELIVERY-1431] - Do not block the PMode upload if it is not valid against the XSD due to whitespaces
- [EDELIVERY-1528] - All JMS listeners(core and plugins) should not catch exceptions
New Features
[EDELIVERY-807] - There should be some XSD validation.
- [EDELIVERY-1132] - Implement CRL & OCSP checks
- [EDELIVERY-1142] - Improvement of the monitoring with Dead Letter Queues
- [EDELIVERY-1189] - Display the version number of Domibus
- [EDELIVERY-1212] - Etrustex plugin: adapt the plugin in order to send/receive the conversation Id to/from Etrustex
- [EDELIVERY-1409] - Test recommended eSens policy with 3.2 RC1 on both sides
Bugs
- [EDELIVERY-965] - Unsupported parameter: javax.crypto.spec.IvParameterSpec
- [EDELIVERY-974] - Sending a message with the receiver both in the From and To
- [EDELIVERY-976] - Duplicating required elements in the request does not generate an error
- [EDELIVERY-977] - Adding irrelevant attributes to required elements does not generate an error and the values are ignored
- [EDELIVERY-978] - Public key encryption algorithm
- [EDELIVERY-988] - Encryption is not working on Java 8
- [EDELIVERY-1136] - Default Plugin Webservice - MTOM
- [EDELIVERY-1142] - Improvement of the monitoring with Dead Letter Queues
- [EDELIVERY-1148] - Wildfly with Oracle issues.
- [EDELIVERY-1174] - Backwards compatibility issue between 3.1.1 and 3.2-SNAPSHOT
- [EDELIVERY-1198] - Missing sequence on Oracle db
- [EDELIVERY-1211] - Etrustex-plugin: if the XSD validation fails do not submit the wrapper/bundle
- [EDELIVERY-1240] - DB deadlocks and QueryTimeoutExceptions duing tests with eDelivery gateway
- [EDELIVERY-1269] - Message download retention_downloaded.
- [EDELIVERY-1320] - "Not found" insead of "too long" error message for Submit message values.
- [EDELIVERY-1323] - Submit Message with service element not present returns generic error.
- [EDELIVERY-1337] - Keep displaying a warning if the sample config files are used
- [EDELIVERY-1406] - In the "tomcat full" distribution package, the war file is not present.
- [EDELIVERY-1407] - No Candidate for Leg Found in domibus-MSH-3.2-SNAPSHOT-tomcat-full
- [EDELIVERY-1426] - Upload truststore does not store the content as expected
- [EDELIVERY-1438] - Remove the "Installation_Instructions.pdf" from the release
- [EDELIVERY-1115] - MySql tables are case sensitive on Linux (table domibus.QRTZ_TRIGGERS is missing)
- [EDELIVERY-1143] - Create client and standalone application for the default plugins
- [EDELIVERY-1358] - Error message for duplicate parameters is not precise.
- [EDELIVERY-1370] - "Download message" response is not a soap response.
- [EDELIVERY-1430] - 'An error has occured' in error Log page of admin console
- [EDELIVERY-1435] - Store the acknowledgement
- [EDELIVERY-1440] - Retention undownloaded value is zero in the sample PModes
- [EDELIVERY-1446] - Filtering is not working in the Message Log section from the Admin page
- [EDELIVERY-1454] - Etrustex plugin: the roles are not correctly set
- [EDELIVERY-1472] - standalone.conf.bat file error in domibus wildfly
- [EDELIVERY-1517] - The message delete datetime is not set correctly + MessageRetentionService fails to clear messages data
- [EDELIVERY-1518] - Authentication error when Message Filter is JMS
- [EDELIVERY-1537] - The plugins are distributed in the wildfly-configuration.zip and weblogic-configuration.zip
- [EDELIVERY-1558] - The web context root is not fixed on WildFly
Documentation
- [EDELIVERY-1193] - DOMIBUS Plugin Cookbook
- [EDELIVERY-1175] - Review the Security Controls and Recommendations for the CEF eDelivery DSI
- [EDELIVERY-1194] - Publish the javadoc API
- [EDELIVERY-1022] - DOMIBUS - Component Software Architecture Document
- [EDELIVERY-1305] - Update the administration guide for 3.2
Known issues and limitations
- [EDELIVERY-1375] - RedeliveryPolicy is not taken into account in ActiveMQ
- [EDELIVERY-1547] - MessageID: special characters handling
- [EDELIVERY-1548] - Download Message special characters
- [EDELIVERY-1554] - Message ID case sensitivity
- [EDELIVERY-1555] - Message parameters case sensitivity
- [EDELIVERY-1561] - domibus-backend.xsd violates Unique Particle Attribution
- [EDELIVERY-1542] - Add message DOWNLOADED status to API and MSH
- Sending a message to yourself is forbidden
For more information, please contact us via our portal or by e-mail: CEF-EDELIVERY-SUPPORT@ec.europa.eu