release Archives - Holodeck B2B

Holodeck B2B 5.3.1

By | News | No Comments

This release fixes the Log4J vulnerability.

Some notable new features:
– You now have the possibility to use message properties in P-Mode matching. This is useful on for example the “finalRecipient” property used in the  EPREL and EUDAMED networks.
– Worker pool management by the core, including ‘on the fly’ reconfiguration.
– Improved logging.
– Receiving of messages with over 30 signed attachments is now possible.
– A new message processing state was added to the options in the API for outgoing messages that encounter an internal error. These can now be processed again without having to be resubmitted by the back end.
– Support for Apache Commons Daemon, which adds another option for running Holodeck B2B as a Windows service.

Important fixes in this version are:
– an upgrade to Log4J 2.15.0 to fix the Log4Shell vulnerability.
– Improved support for a 2-Way Message Exchange Pattern: Push & Push.

For a full overview of all changes, please consult the Changelog in the download.

Holodeck B2B 4.1: Selective pulling

By | News | No Comments

The latest release of Holodeck B2B sees the the addition of support for sending a selective pull request. We’ve also added enhancements in the message processing event mechanism and improvements in the P-Mode finding algorithm. Together with some smaller adjustments these improve the interoperability with other AS4 gateways used for implementation of the ENTSOG and ATO SBR ebMS profiles.

Selective Pulling

Holodeck B2B already featured support for Pull messaging scenarios. With support for sending selective pull requests using simple selection items as described in section 5.1 of the ebMS 3 Part 2 specification, you now have more ways of configuring how and when you want your gateway to send a pull request. 
Another big change is that the back end system can now trigger a pull request, instead of having to use the default interval defined in the gateway itself.
In this release, the support is limited to sending of selective pull requests with “simple selection items” as described in the specification. Selection criteria are not used when processing received pull requests.
To use these new features, you will need to add the Holodeck B2B Pull Request Trigger extension to your gateway. 

New Pull Request Trigger extension

In addition to the new version of Holodeck B2B, we’ve also released a new extension which you will need to install to use the new selective pulling functionality.
This extension allows the Consumer application (your back end application) to control when a Pull Request is sent by Holodeck B2B instead of using the default fixed intervals. It is also where you configure the criteria for your selective pull requests.

More message processing events

But wait, there’s more! 😉 We’ve also added more message processing events around message submission, processing and header validation. These give you even more hooks to add custom functionality to your solution. And of course we’ve fixed a few bugs along the way. You’ll find the full overview of additions in the Change Log.

Get your Holodeck B2B gateway

Download Holodeck B2B now!
And get the Pull Request Trigger extension here.

Looking for support on your AS4 gateway? Chasquis, the creators and maintainers of Holodeck B2B are available to provide support contracts and consultancy services. We can help you get your gateway up and running, or optimise your existing gateway.
We also offer fixed-price packages for installed on-premises gateways that include profile specific extensions, for example for PEPPOL, ENTSOG and ATO Single Touch Payroll (STP), as well as full service hosted gateways.
Get in touch and let us know how we can help you.