This documentation is for WSO2 ESB version 4.5.1. View documentation for the latest release.

Skip to end of metadata
Go to start of metadata

WSO2 Enterprise Service Bus

The WSO2 Enterprise Service Bus (ESB) is a fast, lightweight, 100% open source and user-friendly open source ESB, distributed under the Apache Software License v2.0. WSO2 ESB allows system administrators and developers to conveniently configure message routing, mediation, transformation, logging, task scheduling, fail over routing, load balancing and more. 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 is developed on top of the revolutionary WSO2 Carbon platform, 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.

Getting Started

This is the official, released WSO2 Enterprise Service Bus Documentation, hosted at: The purpose of this documentation is to provide you with information for setting up, configuring and implementing the WSO2 ESB  

If you are a first time user, the following sections will introduce the ESB and help you get started quickly.

About ESB   Installation Guide   Quick Start Guide   Samples   

If you have a specific question regarding the ESB, refer to the FAQ.

This documentation is structured by topics most frequently searched for in an ESB. Therefore, for a more comprehensive coverage of the entire ESB, its important subject areas, and the advanced configurations, we recommend that you spend some time with the documentation structure before digging into the content. You can get a high-level view of the main topics covered by going through the left navigation panel of the online documentation or the table of contents in a printed version.

  • No labels