This sample demonstrates the use of the UltraESB to poll an email account, and forward the message payloads to a web service, and respond back via email with the response from the Web Service.

The HTTP protocol supports transport level request authentication, and the most common schemes are: Basic Authentication and the more secure Digest Authentication scheme. With large scale use of the Amazon S3 infrastructure, the AWS S3 authentication over REST is also being used in many systems connecting with the Amazon S3 infrastructure. This article explains these three authentication schemes, and describes how Proxy services deployed on the UltraESB could use Basic or Digest authentication to secure backend services, and also shows how Basic, Digest or AWS S3 secured services can be accessed through the UltraESB - by allowing the ESB to perform transparent authentication on behalf of the client. Each of these schemes maybe used over HTTPS as well.

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.

The UltraESB uses its own high performance and asynchronous HTTP/S transports using Java NIO, Zero-Copy and Memory mapped file IO; and thus a JEE application server deployment will not yield anything by the use of the application servers' servlet container support. However, the use of an application server JTA transaction manager, Datasources and JMS resources is still a valid and common use-case, while accessing EJB's during mediation is another. Some users also prefer to deploy all applications over Tomcat or another JEE server for administrative or operational reasons.

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.

Traditionally the Apache web server has been used to proxy requests to Tomcat servers using mod_jk or mod_proxy etc. This usually entails configuring multiple configuration files at different locations after making the necessary modules available to Apache. This articles describes how the UltraESB can be used to load balance and fail-over requests to Tomcat servers, and compares with a similar configuration with Apache2 using mod_jk.