TrustRadius: an HG Insights company

WSO2 Enterprise Integrator Reviews & Insights

Score10 out of 10

1 Reviews and Ratings

Get a Demo

Community insights

TrustRadius Insights for WSO2 Enterprise Integrator are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.

Pros

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.

WSO2 Enterprise Integrator Reviews

1 Review

Integration in easy way

Rating: 10 out of 10

Use Cases and Deployment Scope

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.

Pros

  • 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

Cons

  • View deploy artifact in date time order
  • Easy way to map data
  • Easy way to manage payload

Likelihood to Recommend

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.
VU
Verified User
Technician in Research & Development (11-50 employees)
Vetted Review
WSO2 Enterprise Integrator
10 years of experience