A typical use case for WSO2 Enterprise Integrator is when I am in an interoperability environment with healthcare facilities and I have to put together a lot of applications that share some HL7 messages or FHIR service. This is the environment.
Learn what your peers think about WSO2 Enterprise Integrator. Get advice and tips from experienced pros sharing their opinions. Updated: December 2025.
Director at a tech services company with 1-10 employees
Real User
Feb 16, 2023
I use the solution for two purposes. One is to build microservices to enable exposure of APIs, and the second is for implementing communication with backend systems. It helps in integrating business systems with business applications.
We basically use the solution for the connectors. There are some legacy platforms and the WSO2 provides a good amount of connectors. I'm able to integrate this quickly with those third-party platforms. There are some big mediations that are also required.
Our primary use for this product is solution core integration. We recently used this for a project in the financial sector, where we were integrating different legacy systems and internal systems. This was a proof of concept project that has now been completed. We have also used this solution for other elements, such as presenting management systems and as an API gateway host. We are using the on-premise deployment model.
WSO2 Enterprise Integrator, core to the WSO2 Integration Agile Platform, is an open source Integration product for cloud native and container-native projects. It enables enterprise integration experts to build, scale, and secure sophisticated integration solutions to achieve digital agility. Unlike other integration products, WSO2 Enterprise Integrator already contains integration runtimes, message brokering, business process modeling, analytics and visual tooling capabilities.
A typical use case for WSO2 Enterprise Integrator is when I am in an interoperability environment with healthcare facilities and I have to put together a lot of applications that share some HL7 messages or FHIR service. This is the environment.
The banks and government entities use this solution.
My company has a very minimal in-house software development team to develop some mobile applications and workflow integrations.
I use the solution to transfer data from different formats, like XML to JSON, and orchestrate the solution and put it in a message block.
We use WSO2 Enterprise Integrator in our center.
I was using the solution for integration purposes.
We use the solution as an integration platform.
I use the solution for two purposes. One is to build microservices to enable exposure of APIs, and the second is for implementing communication with backend systems. It helps in integrating business systems with business applications.
We primarily use the solution to access external services or expose our internal services to outside entities.
Our primary use case for this solution is building APIs to integrate with other systems.
Our needs are mainly focused on the ESB side. We use the product to fill our enterprise service bus scenarios or needs.
We are using it for our enterprise customers.
We basically use the solution for the connectors. There are some legacy platforms and the WSO2 provides a good amount of connectors. I'm able to integrate this quickly with those third-party platforms. There are some big mediations that are also required.
Our primary use for this product is solution core integration. We recently used this for a project in the financial sector, where we were integrating different legacy systems and internal systems. This was a proof of concept project that has now been completed. We have also used this solution for other elements, such as presenting management systems and as an API gateway host. We are using the on-premise deployment model.
We primarily use the solution for integration between core banking and other systems.