Iridium flare .... WSO2 ESB 3.0.0 Released!

The WSO2 ESB team is pleased to announce the release Open Source Enterprise Service Bus (ESB) 3.0.0 - Iridium.


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 3.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.

You can download this distribution from http://wso2.org/downloads/esb and give it a try.

New Features of WSO2 ESB 3.0.0
  • Priority based mediation through priority executors
  • WS-Discovery support and dynamic endpoint discovery
  • Message Relay for efficient pass through of messages
  • Component manager to install and uninstall features (provisioning support)
  • Common Internet File System (CIFS) support through the VFS transport
  • File locking functionality in the VFS transport to support concurrent polling
  • Smooks mediator for efficient message transformation
  • Enrich mediator for smart message manipulation
  • OAuth mediator for 2-legged OAuth support
  • Default endpoint UI
  • Hot deploy and hot update configuration elements (sequences, endpoints, proxy services etc)
  • Transport level statistics collection and monitoring
  • POX security support
  • Dependency detection and alerting for mediation configuration elements
  • Mediation statistics API and custom mediation statistics consumers
  • Multiple certificate/identity support in the NHTTP transport sender
  • Improved logging capabilities for the NHTTP transport
  • Templates based proxy service development in the UI
  • Dashboard to monitor server environment and runtime
  • Easy creation and management capabilities for dynamic sequences and endpoints
  • Pagination to service management, endpoint management and sequence management UIs
  • Obtaining resources like WSDL's through web proxy servers

Key Features of WSO2 ESB
  • Proxy services - facilitating synchronous/asynchronous transport, interface (WSDL/Schema/Policy), message format (SOAP 1.1/1.2, POX/REST, Text, Binary), QoS (WS-Addressing/WS-Security/WS-RM) and optimization switching (MTOM/SwA).
  • Non-blocking HTTP/S transports based on Apache HttpCore-NIO for ultrafast execution and support for thousands of connections at high concurreny with constant memory usage.
  • Built in Registry/Repository, facilitating dynamic updating and reloading of the configuration and associated resources (e.g. XSLTs, XSD, WSDL, Policies, JS configurations ..)
  • Easily extendable via custom Java classes (mediator and command)/Spring configurations, or BSF Scripting languages (Javascript, Ruby, Groovy, etc.)
  • Built in support for scheduling tasks using the Quartz scheduler.
  • Load-balancing (with or without sticky sessions)/Fail-over, and clustered Throttling and Caching support
  • WS-Security, WS-Reliable Messaging, Caching & Throttling configurable via (message/operation/service level) WS-Policies
  • Lightweight, XML and Web services centric messaging model
  • Support for industrial standards (Hessian binary web service protocol/ Financial Information eXchange protocol and optional Health Level-7 protocol)
  • Enhanced support for the VFS (File/FTP/SFTP), JMS, Mail transports with optional TCP/UDP transports and transport switching among any of the above transports
  • Support for message splitting & aggregation using the EIP and service callouts
  • Database lookup & store support with DBMediators with reusable database connection pools
  • WS-Eventing support with event sources and event brokering
  • Rule based mediation of the messages using the Drools rule engine
  • Transactions support via the JMS transport and Transaction mediator for database mediators
  • Internationalized GUI management console with user management for configuration development
  • Integrated monitoring support with statistics, configurable logging and tracing
  • JMX monitoring support and JMX management capabilities like, Graceful/Forceful shutdown/restart

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