Domibus

Domibus (Domain Interoperability Bus) is an eDelivery AS4 profile Access Point sample implementation maintained by the European Commission. This sample implementation may be used to test other implementations of the technical specifications or as a working solution.

The users of the sample implementation remain fully responsible for the integration with back-end systems, its deployment and operation. The support and maintenance of the sample implementation, as well as any other auxiliary services, are provided according to the terms and conditions defined in the Master Service Arrangement.

You can submit change requests via the eGovernance space page. You must be a member of the eDelivery community to submit change requests. If you are not a member, request access by contacting us through the eGovernance space page. Once you are a member, you can proceed to submit your change request.

Domibus log levels can be defined in the configuration files. For details, refer to the Domibus documentation.

Yes, Domibus is released under the European Union Public Licence 1.2, allowing free use for professional purposes.

WildFly support in Domibus will be phased out by Q2 2027. After Domibus 5.2, the supported application servers will be Apache Tomcat and WebLogic.

Comparison of the two, highlighting elements that are more relevant for a Domibus installation:

We advise you to choose Apache Tomcat or WebLogic depending on your circumstances and requirements.

The eDelivery AS4, SMP, BDXL and ebCore Party Id 2.0 were adopted on 4 December 2024. This adoption affects the sample implementation software as follows:

1. Support for new specifications:
   • eDelivery Building Block plans to incorporate the new specifications in upcoming sample software releases.
   • All sample software will support both old and new specifications.
   • Users can configure which specification version to use: old specifications, new specifications or a mixed approach.
2. Timeline and planning for 2025 and beyond: Support plans may be adjusted based on factors such as budget allocation in the DEP Work Program 2025-2027.
3. Backwards compatibility:
   • Different solution providers may adopt varying approaches to backwards compatibility.
   • It is recommended to contact other solution providers directly to understand their compatibility strategies.
4. Ecosystem impact:
   • Ecosystem owners should assess the impact based on the combination of products used within their environments.
   • Proper planning is essential to ensure seamless integration and functionality.

Upgrading to the latest version of Domibus is not mandatory but is recommended to benefit from the latest features and security enhancements.

Key considerations:

• Custom plugins: Ensure that custom plugins are updated to remain compatible with the new Domibus version.
• Support periods:
  • Standard releases: Supported for at least one year from the release date of their minor version.
  • Long-Term Support (LTS) releases: Supported for at least two years from the release date of their minor version.

Additional information:

• Support expiration dates: Refer to Domibus releases and Support arrangement for exact expiration dates of the support periods.
• LTS identification: Releases under Long-Term Support are clearly identified in Domibus releases to assist in your upgrade planning.

By staying updated, you ensure that your Domibus installation remains secure, supported and equipped with the latest functionalities.

You can download Domibus, an open-source eDelivery sample implementation of an AS4 Access Point, for free from the Domibus release page.

Domibus currently supports Tomcat, WebLogic and WildFly. However, WildFly support will be phased out from Domibus 6.0 onwards. If you are using WildFly, please consider migrating to Tomcat or WebLogic to ensure continued support and security patches. Consult the Domibus releases for specific timelines and migration guidance.

Domibus is developed in Java, making it compatible with any platform that supports Oracle Java JRE/JDK 8. It has been successfully deployed and tested on Windows and Linux. For more information on supported platforms for specific Domibus versions, please check the Domibus release page.

According to the current plan, Domibus will begin supporting Elliptic Curve certificates starting from Version 6.0. For detailed information about this release and future updates, please refer to the Domibus Release Roadmap.

To use Dynamic Discovery with Domibus in eDelivery, you can follow our recorded webinar that guides you through each step. The recording covers how to register participants, configure necessary settings, send and receive AS4 messages and manage both successful and failed message exchanges.

You can check your Domibus installation by following these steps:

1. Check the installation directory to ensure all necessary files and folders are present.
2. Verify the configuration files are set up correctly.
3. Test the database connection to confirm Domibus can communicate with its database.
4. Access the Admin Console through a web browser and try to log in.
5. Review the Domibus log files for any error messages or warnings.
6. Send and receive a test message to verify the core functionality.
7. Ensure the security settings, including certificates and authentication methods, are correctly configured.
8. If using plugins, make sure they are properly installed and functioning.

Domibus performance depends on hardware, network, configuration and setup (single node or clustered). Below are examples of performance results:

1. Single node setup

   1. Hardware specs: 4 CPUs, 16GB memory, 30GB SSD disk.
   2. Performance: Sent 10KB messages at 55 messages per second.

2. Clustered setup

   1. Hardware specs:
      1. 4 nodes (each with 8 CPUs, 32GB RAM, SSD disks).
      2. Includes F5 Load Balancer, Oracle Database and Blue Coat proxy.
   2. Performance: Sent and received 30KB messages at 135 messages per second each, totalling 270 messages per second.

3. Domibus 5.0 (advanced setup)

   1. Hardware specs: 4-node cluster using Oracle WebLogic Server and Oracle Database.
   2. Performance:
      1. Handles over 1000 messages per second with 5KB message size.
      2. Configured to send 1000 messages per second and receive 500 messages per second.

Note: Performance can vary depending on factors like database size, message size, RAM and disk speed. Ensure you scale and test Domibus according to your specific requirements.

Yes. Domibus, an open-source Access Point sample implementation, follows eDelivery AS4 specifications, so it can interoperate with other conformant products in your ecosystem.