Skip to main content

WSO2 ESB 5.0.0 Beta Released

WSO2 team is happy to announce the beta release of the latest WSO2 ESB 5.0.0. This version of the ESB has major improvements to the usability aspects of the ESB in real production deployments as well as development environments. Here are the main features of the ESB 5.0.0 version.
Mediation debugger provides the capability to debug mediation flows from WSO2 developer studio tooling platform. It allows the users to view/edit/delete properties and the payload of the messages passing through each and every mediator.
You can find more information about this feature at below post.
How to Debug WSO2 ESB Mediation Flow
INTRODUCTION WSO2 Enterprise Service Bus is a lightweight, high performance, and comprehensive ESB. 100% open source…nuwanpallewela.wordpress.com
Data mapper is the most awaited data transformation tool for WSO2 ESB. It allows users to load input/output message formats through xml files, json schemas or create them from the data mapper user interface itself. In addition to mapping data from input to output directly, users can apply different functions like split, aggregate, uppercase, lowercase while doing the mapping.
You can find more information about data mapper from below post.
How to Use WSO2 Data Mapping Mediator in ESB
INTRODUCTION WSO2 data mapper is a data mapping solution that convert and transform one format of data to a different…nuwanpallewela.wordpress.com
Comprehensive Statistics/Tracing with analytics for ESB distribution. With ESB 5.0.0 onwards, WSO2 ESB comes as a complete solution with runtime + tooling + analytics. Analytics for ESB is part of this solution and it comes with a pre installed features/ dashboards for ESB specific analytics. You will get a fully fledged analytics dashboard to visualize statistics about your services and more fine grained information about internal ESB components (Proxy, API, Endpoints, Sequence, Mediators). It also allows you to trace the messages throughout the mediation flows and detect any failure messages and go through each and every mediator which the message has been passed through.
JMS 2.0 support is coming with this release. JMS has been used in many enterprise integration scenarios and it has gone through a major revamp with JMS 2.0 in terms of features and developer APIs. WSO2 ESB becomes one of the early adopters of this JMS version.
You can find more information about this feature at below blog post.
Ravindra Ranwala's Blog
JMS is a messaging API implemented to communicate between two or more java clients using an enterprise messaging system…ravindraranwala.blogspot.com
Websocket can be opened with WSO2 ESB. You are no longer restricted to the capabilities of HTTP 1.1 version with WSO2 ESB. We have provided the support for the high performing websocket protocol for HTTP communication.
JMS distributed (XA) transactions will be supported with this version of WSO2 ESB 5.0.0. Now you can communicate with multiple distributed JMS endpoints and make the end to end message processing in a transactional manner.
In addition to the above mentioned features, we have added many more features, improvements and bug fixes with this release. You can download the completed solution from below mentioned links.
Runtime for WSO2 ESB 5.0.0 (Beta) — https://github.com/wso2/product-esb/releases/tag/v5.0.0-BETA
Tooling for WSO2 ESB 5.0.0 (Beta) — https://github.com/wso2/devstudio-tooling-esb/releases/tag/v5.0.0-beta
Analytics for WSO2 ESB 5.0.0 (Beta) — https://github.com/wso2/analytics-esb/releases/tag/v1.0.0-beta
Labels:

Comments

Post a Comment

Popular posts from this blog

How to protect your APIs with self contained access token (JWT) using WSO2 API Manager and WSO2 Identity Server

In a typical enterprise information system, there is a high chance that people will use different types of systems built by different vendors to implement certain types of functionalities. The APIs might be hosted in an API Manager developed by vendor A and the user management can be implemented using a different vendor (vendor B). In this type of a situation, one system will not be able to directly contact the other system but they want to use both systems in tandem. Self-contained access tokens are used in these types of situations where applications can get the token from one system and use that in another system to access protected resources. In this scenario, the second system does not need to make a contact to the first system over the network to validate the user information since the token is self-contained and it has relevant details about the user. This will improve the token processing time significantly since it completely removes the network interaction. The below fig...
1 comment
Read more

WSO2 ESB creating a response for a "GET" request

When you are creating REST APIs with WSO2 ESB, you may need to send some response message back to the user when something goes wrong. In this kind of scenario, you can create a payload inside the ESB and send it back. For doing this, you can use the below configuration. <api xmlns=" http://ws.apache.org/ ns/synapse " name="LoopBackProxy" context="/loopback">    <resource methods="POST GET">       <inSequence>          <property name="NO_ENTITY_BODY" scope="axis2" action="remove"></property>          <log level="full"></log>          <payloadFactory media-type="xml">             <format>                <m:messageBeforeLoopBack xmlns:m=" http://services...
Post a Comment
Read more

How to configure timeouts in WSO2 ESB to get rid of client timeout errors

WSO2 ESB has defined some configuration parameters which controls the timeout of a particular request which is going out of ESB. In a particular  scneario, your client sends a request to ESB, and then ESB sends a request to another endpoint to serve the request. CLIENT->WSO2 ESB->BACKEND The reason for clients getting timeout is that ESB timeout is larger than client's timeout. This can be solved by either increasing the timeout at client side or by decreasing the timeout in ESB side. In any of the case, you can control the timeout in ESB using the below properties. 1) Global timeout defined in synapse.properties (ESB_HOME\repository\conf\) file. This will decide the maximum time that a callback is waiting in the ESB for a response for a particular request. If ESB does not get any response from Back End, it will drop the message and clears out the call back. This is a global level parameter which affects all the endpoints configured in ESB. synapse.global_timeout_inte...
6 comments
Read more