e-SENS interoperability tests succesful

By | News | No Comments

During the summer of 2015 we participated in the interoperability tests for the EU e-SENS program. We ran tests against AS4 implementations by IBM, Flame, Axway and Domibus. Holodeck B2B completed all succesfully.
During the tests, Holodeck B2B showed that it supports all features of the e-SENS AS4 profile, including the AES-128 GCM encryption algorithm.

Features tested included:

  • AS4 reception awareness
  • Non-repudiation of receipt
  • Signing
  • Encryption using the AES-128 GCM algorithm
  • AS4 compression

Holodeck B2B and AS4 proved capable of processing large files up tot 2GB. Further tests of sending large files are planned for later this year.
If you would like to run tests yourself, you can request the release candidate of Holodeck B2B.

Holodeck B2B 2, beta 3 featuring AS4 security

By | News | No Comments

The latest beta of the Holodeck B2B AS4 message service handler is now available on request. Most important new features are encryption and signing based on WS-Security, making Holodeck B2B now fully AS4 compliant.


Holodeck B2B supports end-to-end message encryption in a point to point exchange. The Holodeck B2B security module uses your system’s default crypto provider to encrypt the message. By changing the crypto engine you can configure the supported algorithms.


With signing of messages implemented, Holodeck B2B now offers

  • Authorization of pull requests based on the X.509 certificate.
  • Authentication of push and pull messages including non-repudiation receipts.


The AS4 specification defines three conformance profiles: ebHandler, Light and Minimal Client. Holodeck B2B complies with all three. We have a full overview under the Detailed feature list.

With the addition of message authentication and encryption the Holodeck B2B open source messaging solution is ready to support Superstream and Entsog AS4 profiles.


Beta 3 is available on request.
We’d like to know more about why you are considering using Holodeck B2B. Which features are most important to you, looking at the current features as well as things you’d like to see in Holodeck B2B in the future?
If you would like to try the new version, please contact us using the form below.

*edit: As Holodeck B2B 2.0 is out of beta per april 2016, you can find the latest version on the Download page.*

Beta 2.2 is out – and we’ve moved!

By | News | No Comments

Today we released Holodeck B2B 2.0 beta 2.2. This version includes a fix to prevent duplicate Content-id’s for the MIME parts included in the message.

And there’s more news. A few weeks ago, we moved the project from Sourceforge to Github! Among other advantages, Github makes it a lot easier for others to contribute to Holodeck B2B. The old project account on Sourceforge will no longer be updated.

You will find the newest version on the Download page.

Holodeck B2B 2.0 beta 2 is available

By | News | No Comments

We have just released beta 2 of Holodeck B2B version 2.0!

New in this beta:

  • Improved error handling. We have added better error generation and configurable reporting.
  • Support for asynchronous receipts. You can now also specify the callback reply pattern for receipts and specify a URL to send them to.
  • Support for the MPC sub-channel feature. With this feature, you can define multiple parties within one P-Mode that can pull a user message from one MPC. Each party is assigned its own sub channel but all will pull the message from the main MPC messages are submitted to. When pull authorization is added in a future version each sub channel will also have its own authorization.
  • AS4 compression. When exchanging large payloads you can compress them before sending using the compression feature. This reduces the amount of data to transfer and when security is used, the amount of data to sign and/or encrypt.
  • Configurable and extensible message delivery. The way received messages should be delivered to the business application can now be configured in the P-Mode. Included with Holodeck B2B are deliverers that write the message info to file (using different formats). It is also possible to add your own message deliverers.