...
- asynchronous message processing model
- parent-child concept that allows to divide main message into more child messages and process them separately
- obsolete messages checking when messages impact same data
- funnel component is for filtering concurrent messages at specific integration point. This filtering ensures that only one message at one moment will be processed, even in guaranteed order (optional choice).
- guaranteed message processing order
- algorithm is configurable
- synchronous response that input request is saved in queue and asynchronous confirmation with processing result
- monitoring of processing in Admin GUI and via JMX
- throttling - functionality that checks count of input requests to integration platform and if this count exceeds defined limit then new requests are restricted
- extended error handling with many new Camel events
- tracking external systems communication - storing requests and responses
- web administration console
- searching in asynchronous messages
- message details with requests/responses overview
- searching in logs
- manual cancel of next message processing
- restart failed messages
- error codes catalogue
- exposed WSDLs overview
endpoints overview
- extended logging allows to group logs together of one request/message or process
- direct call console allows to send custom requests to external system
- stopping mode is useful function for correctly CleverBus OpenHub shutdown
- extensions allow to encapsulate new OpenHub framework functionality
- support for cluster (in progress at this moment)