TrustRadius: an HG Insights company

WSO2 Enterprise Integrator

Score10 out of 10

1 Reviews and Ratings

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. It can act as an ESB, a streaming data processor, and a microservices integrator. Deployment options include on-premises, cloud, hybrid, or a container orchestration platform of choice.

Top Performing Features

  • Connect to traditional data sources

    Ability to connect to traditional data sources like relational databases, flat files, XML files and packaged applications

    Category average: 8.9

  • Simple transformations

    Simple data transformations are calculations, data type conversions, aggregations and search and replace operations

    Category average: 8.9

  • Testing and debugging

    Tool to debug and tune for optimal performance

    Category average: 7.2

Areas for Improvement

  • Integration with data quality tools

    Integration with tools for cleansing, parsing and normalizing data according to business rules

    Category average: 7.4

  • Integration with MDM tools

    Integration with master data management tools to ensure data consistency across the organization

    Category average: 7.2

  • Connecto to Big Data and NoSQL

    Ability to connect to non-traditional data sources like Hadoop and other big data technologies, and NoSQL databases

    Category average: 7.6

Integration in easy way

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

Most Important Features

  • protocollo transfomation
  • service configurazion and not developed
  • clustering

Return on Investment

  • Reduce development time to the service integration
  • We can use junior developer
  • Clustered in easy way

Alternatives Considered

TIBCO Enterprise Message Service and Mule ESB

Other Software Used

WSO2 API Manager, Avolution ABACUS, ReadyAPI (formerly SoapUI Pro, LoadUI Pro, & ServiceV Pro)