This article demonstrates the ease of handling both JTA and non-JTA (i.e. local) transactions - or both at the same time - with the UltraESB. In addition to the ease of use, the power to suspend and resume transactions, or to operate with multiple transactions within a message flow allows any requirement to be met much more easily. Compare the ease of use and the features - by reference with articles describing a subset of this functionality with the JBoss ESB and the WSO2 ESB.

This article demonstrates the capability of the UltraESB to split messages and aggregate responses, and in particular highlights the capability to stream chunks of responses aggregated as-soon-as-they-become-available; while handling premature timeouts thus preventing the remote client from receiving a partial response on a timeout.

Note: This is an advanced example solving a complex scenario, and was driven by a user request for a proof-of-concept.

This article describes how one could use the XQuery support introduced since 1.0-beta-3-b2, to generate mock REST services. It also describes how ETags could be set and checked against requests.

This article describes how the UltraESB can be used as a high performance WS-Security gateway in an enterprise deployment. The example demonstrates how the UltraESB verifies the timestamp and the signature and performs decryption of an encrypted SOAP message, and forwards a valid request to a backend service after removing the security headers. The response is signed and encrypted, and then returned back to the client.

This example introduces XSD schema validation of XML payloads with the UltraESB. Additionally it shows how the UltraESB performs error handling and recovery - and how a sequence defines another sequence as its error handler.

This example shows a Proxy service capable of mediating a Jax-WS service, and additionally accepting FastInfoset requests and forwarding them to non-FastInfoset compatible backend services by converting the requests to regular XML. The responses from the backend services are converted again to FastInfoset requests, and sent back to the clients.