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.

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.

The Lightweight and High Performance ESB, Free and Open Source!

Quick Introduction

Integrate different systems both within an organization and beyond

The UltraESB is a Free and Open Source Enterprise Service Bus [ESB] that facilitates the integration of different systems; both within an organization and beyond. Integration is facilitated via "messages" which maybe HTTP/S messages (such as SOAP, REST, JSON, XML, Hessian, AS2, HTML, Binary, Text etc) or messages over many other transports such as JMS, Email, TCP, MLLP/S etc, or Files FTP/S, SFTP etc. Messages may carry different types of payloads such as SOAP, XML, Text, CSV, EDI, HL7, JSON, Maps etc., and the UltraESB can accept messages over one transport in one format, and forward it to another system over another transport and another format. Messages passing through the UltraESB can be “mediated” via fragments of Java code or JSR 223 Scripting   languages   such   as   Ruby,   Groovy,   Javascript   and   many   many   others   as   listed   at https://scripting.dev.java.net/ Thus the “mediation” logic could be easily written from within a Java IDE the user is familiar with, and
test, execute and debug the configuration all from within the IDE and utilizing the IDE features such as step through debugging.

This article explains how the UltraESB could be used as a HTTP/S or SOAP Security gateway, to front internally deployed services of an organization in a SOA. The UltraESB allows SSL termination, WS-Security validation/termination, HTTP Basic/Digest authentication enforcement, Client SSL certificate validation etc, from a security point of view. Additionally it provides validation and transformation capabilities - and supports secure XML processing which safeguards the infrastructure from XML based attacks.

This document describes the UltraESB public API for mediating messages, and the configuration of the various transports, WS-Security and AS2 options