A closer look at WSO2 ESB 4.0.0

WSO2 ESB v4.0.0 Released - 13th June 2011

WSO2 ESB is a fast, lightweight and user friendly open source Enterprise Service Bus (ESB) distributed under the Apache Software License v2.0. WSO2 ESB allows system administrators and developers to easily configure message routing, intermediation, transformation, logging, task scheduling, fail over routing and load balancing. It also supports transport switching, eventing, rule based mediation and priority based mediation for advanced integration requirements. The ESB runtime is designed to be completely asynchronous, non-blocking and streaming based on the Apache Synapse mediation engine.

WSO2 ESB 4.0.0 is developed on top of the revolutionary WSO2 Carbon platform (Middleware a' la carte), an OSGi based framework that provides seamless modularity to your SOA via componentization. This release also contains many new features and a range of optional components (add-ons) that can be installed to customize the behavior of the ESB. Further, any existing features of the ESB which are not required to your environment can be easily removed using the underlying provisioning framework of Carbon. In brief, WSO2 ESB can be fully customized and tailored to meet your exact SOA needs.

New Features

  • HTTP relay transport - Pure streaming HTTP transport based on Java NIO for ultra fast HTTP routing
  • Deployment synchronizer - Easily synchronize the configuration across a cluster of Carbon Servers
  • Message stores and processors - For advanced enterprise messaging and QoS enforcement (eg: in-order delivery, exactly once delivery)
  • Mediation templates - The concept of reusable functions to the ESB configuration language
  • Message broker - Built-in JMS provider/broker powered by Apache Qpid
  • FTPS support via file transport - Transfer files over SSH connections
  • Conditional router mediator - Implement advanced and complex routing logic at ease
  • URL rewrite mediator - Rewrite URLs and URL fragments efficiently
  • Custom XPath extensions - User defined custom XPath extensions support
  • New HL7 transport (optional) - Send and receive HL7 messages over MLLP and other transports
  • New eventing implementation - A powerful event broker with extensive support for WS-Eventing and topic management
  • Event mediator - Publish events to topics defined in the built-in event broker
  • LDAP user store - Built-in LDAP service based on Apache Directory Server
  • Dynamic registry keys and endpoint URL support - Construct registry lookup keys and endpoint URLs dynamically at mediation time

Enhancements

  • Improved Smooks mediator
  • Enhanced support for service chaining with the receiving sequence support in the send mediator
  • Improved weighted round robin algorithm for the load balance endpoint
  • Improvements to caching
  • Automatic schema imports from the WSDLs added to the registry (for proxy services)
  • Automatic schema imports from the schema files added to the registry (for validate mediator)
  • Support for setting properties at the endpoint level
  • Enhanced Enrich Mediator
  • Improved support for batch transfers in FIX transport
  • Validation support for the ESB configuration editor (source view)
  • Proxy service UI enhancements
  • Enhanced menu layouts
  • Local transport for fast in-VM service calls



Comentários

Postar um comentário

Postagens mais visitadas deste blog

Understanding Reactor Pattern with Java NIO

Imagem
Why non-blocking IO A typical server application, such as a web server, needs to process thousands of request concurrently. Therefore, the modern web server needs to meet the following requirements. Handling of thousands of connections simultaneously (significant number of connections may be in idle state as well) Handling high latency connections Request/response handling needs to be decoupled Minimize latency, maximize throughput and avoiding unnecessary CPU cycles Hence, to cater to such requirements, there can be several possibilities in the server application architecture. Having a pool of sockets for each client, and periodically polling them: This is the most straightforward approach; however, it is more or less impractical without non-blocking sockets. This is extremely inefficient and never scales with the increasing number of connections. Thread per socket: This is the conventional approach and was initially used in some applications and this is the only practical solution wi...
Leia mais

A new journey.. A new working place.. WSO2 Inc.

Imagem
I guess switching blogs is less riskier than switching jobs. Anyway I had to take that risk of switching jobs in last month (12/2009) as I've joined WSO2 as a Senior Software Engineer. My very first job lasted only one and half years owing to various issues I had with the type of work I got during my first employment. However it was a good experience on some rare technologies like Search Engines and Indexing.. and not forgetting C++. Now.. the context has changed.. technologies has changed.. environment has changed... So I believe it's a whole new experience to me to work for WSO2 , which is a renowned Open Source SOA Company. These are my first few steps in the world of SOA and Web Services...
Leia mais