Skip to main content
WSO2 Enterprise Integrator

WSO2 Enterprise Integrator


What is WSO2 Enterprise Integrator?

WSO2 Enterprise Integrator (WSO2 EI) is an open-source hybrid integration platform providing graphical and CLI tooling, integration runtimes, and monitoring with a variety of deployment options. The integration runtime engine is capable of playing multiple roles in an enterprise architecture.…

Read more
Recent Reviews

TrustRadius Insights

WSO2EI has been praised by users for its ease of configuration and understanding, especially if they have previous experience with WSO2 …
Continue reading

Integration in easy way

10 out of 10
March 16, 2022
Integration is the best word for enterprise service bus[ESB], with ESB is possible to integrate REST, SOAP, JMS, MQTT, SQL artifact. We …
Continue reading
Read all reviews
Return to navigation

Product Details

What is WSO2 Enterprise Integrator?

WSO2 Enterprise Integrator Technical Details

Deployment TypesOn-premise, Software as a Service (SaaS), Cloud, or Web-Based
Operating Systems,
Mobile ApplicationNo
Return to navigation


View all alternatives
Return to navigation

Reviews and Ratings


Community Insights

TrustRadius Insights are summaries of user sentiment data from TrustRadius reviews and, when necessary, 3rd-party data sources. Have feedback on this content? Let us know!

WSO2EI has been praised by users for its ease of configuration and understanding, especially if they have previous experience with WSO2 Enterprise Service Bus. The software is versatile and performant, allowing it to work well with other WSO2 products like the API Manager, Identity Server, and Stream Processor. It can be run locally, on a server, or in the cloud.

The primary use case of WSO2EI is integration, enabling users to integrate different REST endpoints. While the editor in WSO2EI can be challenging at times, leading to a development cycle of progress, frustration, and then breakthrough moments. Despite this, the potential of BPMN in EI is often not fully utilized.

Users who have worked with WSO2 products for several years have had an overall positive experience with WSO2EI. It has been used successfully to integrate legacy ERP systems with automatic warehouse systems, Pick to Light systems, CRM, and configurators. While the EI and BPS tools in WSO2EI perform well, there is a learning curve that can be a hindrance for new users. The documentation for BPS needs improvement to make it more user-friendly. The new version of Integration Studio provides helpful information and support for XPath in BPMN would be beneficial.

WSO2EI has been implemented effectively as a core integration backbone and for enabling API development, providing good value for money. For example, at Whirlpool, it was used to improve integration between partners, marketplaces, and SAP systems resulting in faster integrations and reduced API latency. Users highly regard WSO2EI and instill confidence in implementing it for integration purposes.

The software has been praised for its ability to integrate various protocols and artifacts such as REST, SOAP, JMS, MQTT, and SQL. Users have utilized WSO2EI for message transformation, service chaining, and message forwarding allowing them to compose new messages and call multiple backend services. Overall, WSO2EI offers a reliable integration solution with a wide range of use cases and positive user experiences.

Reusability of Building Blocks: Many users have praised the reusability feature of WSO2 EI as it allows for faster delivery by reusing sequences and endpoints across multiple integration flows. This capability enables businesses to save time and effort in building integrations from scratch.

Great Value for Money: Several reviewers have mentioned that WSO2 EI provides exceptional value for the price paid. Customers feel that they are getting more than what they expected, making it a cost-effective solution for enterprise integration needs.

Prompt and Supportive Support Team: The support team of WSO2 has received high praise from customers due to their promptness, supportive nature, and focus on addressing customer queries and reported issues. Users appreciate having a responsive support team that is dedicated to ensuring smooth operations and resolving any challenges faced during implementation or usage of the software.


  1. Graphical representation of integration flows: Some users have found the graphical representation of integration flows impractical due to the large size of the mediators, making it difficult to navigate and understand the overall flow.
  2. Reliance on XML: Several users have mentioned that the software heavily relies on XML, which can be cumbersome for some users who are not familiar with this technology, leading to potential difficulties in working with the software.
  3. Outdated core components and steep learning curve: Users have expressed concerns about the outdated core components of the software and the lengthy learning process required to master it, indicating that there is room for improvement in terms of keeping up with industry standards and reducing complexity for new users.


(1-1 of 1)
Companies can't remove reviews or game the system. Here's why
Score 10 out of 10
Vetted Review
Verified User
Integration is the best word for enterprise service bus[ESB], with ESB is possible to integrate REST, SOAP, JMS, MQTT, SQL artifact. We used ESB to transform message in and message out. We implement a service chain, during a service call we call more than one service and we compose a new message as a message out. The new message contains fields from the all services response. We also used ESB to implement message and forward, we persist message in a JMS queue, and using message processor we analyze the message and call more than one backend service.
  • Service chain pattern
  • Message transformation
  • Call more than one backend service
  • Call service with different protocoll as the client use
  • Use file as input
  • Use mail as input
  • View deploy artifact in date time order
  • Easy way to map data
  • Easy way to manage payload
The best-suited scenario is the service chain pattern or all patterns used in online mode. The less appropriate scenario is a batch service the duration time of the service is more than 10minutes because it is necessary to increase the HTTP timeout.
  • protocollo transfomation
  • service configurazion and not developed
  • clustering
Data Source Connection (2)
Connect to traditional data sources
Connecto to Big Data and NoSQL
Data Transformations (2)
Simple transformations
Complex transformations
Data Modeling (5)
Data model creation
Metadata management
Business rules and workflow
Testing and debugging
Data Governance (2)
Integration with data quality tools
Integration with MDM tools
  • Reduce development time to the service integration
  • We can use junior developer
  • Clustered in easy way
We can start with the community version and then when we moved into production we can buy the supported version. The supported and community version have the same code so we can do every test before deciding to buy the supported version.
Return to navigation