WSO2 Enterprise Integrator Reviews

The connectors have been the most impactful features for handling integrations. I can use these connectors when I need specific connectivity with a third party, like a core banking system in BFSI. I don't need to do all the development. I take the specific connector, put in the IP address and password, and it takes care of everything.

For example, there's a messaging connector for connecting to mail or SMS utilities. I just specify the server IP address, port, username, and password, and the connector has the relevant details. This helps with easy integration. My developer saves time as they don't need to write the whole module. Using the connector makes development faster.

The tool also provides a web-based tool, making it a no-code solution. I can use the WSO2 Enterprise Integrator GUI to design. I can specify which systems I'm using and define IP addresses and other details. It writes the code on the backend and handles the connectivity, simplifying the entire integration process.

I find the transformation and mediation capabilities useful. The basic transformation and mediation features are also available in the API manager. Most of the time, people need REST to SOAP and SOAP to REST conversions, which are available in the API manager.

We use the tool for more complex mediations. It's helpful for handling images or multipart transfers, like transferring large files or PDFs. However, in some cases, we've handled large file transfers differently. Instead of using multipart through it, we share the file as a link. The user clicks the link, and the big file opens in a different browser window.

It is only required for very complex setups when the use case can't be met with the normal API manager. That's when we go with advanced transformation and mediation.

WSO2 Enterprise Integrator has influenced cost savings and efficiency in my customers' projects. It decreases the development timeframe, which is the most important factor. Implementing things in a timely manner reduces costs on the implementation and project management side.

While we have to factor in some additional costs for subscription and support, the product gives us good advantages. The developers are more comfortable and able to do things faster with WSO2 Enterprise Integrator. However, it really depends on the business requirements. If the requirements are complex enough to need the tool, then we use it. We don't need WSO2 Enterprise Integrator for simple mediation and transformation requirements - we can use API Manager and some open-source code.

The product is necessary for very complex banking requirements or heavy requirements where a lot of these features are used. In most of our implementations, we've mainly used REST APIs provided by the customer. If there's a lot of SOAP involved, then some WSO2 Enterprise Integrator is definitely required.

I'm very satisfied with the performance. It's a very high-performance system. It requires very few cores and the license cost is reasonable. It's a very high-performing product. You can easily reach up to 1000 TPS with just a single or two-core license.

The main issue with the product is pricing. It uses core-based pricing for WSO2 Enterprise Integrator and API Manager. It would be best if you had APIM by default. It provides many connectors for easy integration with third-party systems.

Often, customers decide to develop using open-source tools like Spring Boot if there aren't many connectors required to avoid increasing costs. They'll develop this way and then deploy using APIM, the bare minimum needed.

It is mainly required for very complicated setups with many connectors. In the implementations I've seen, people often used open-source tools because there weren't many third-party systems involved—just their organization's own systems.

From WSO2 Enterprise Integrator, I expect them to bring up more and more connectors in the future. That's the main expectation. Having more connectors in various areas will help us when discussing new requirements. I don't have any specific use case right now, so I can't name a particular connector.

But, as new technologies emerge, the relevant connectors should be there for those. WSO2 Enterprise Integrator mainly helps with the integration part, which can be simplified only if you have relevant connectors for whatever you're doing.

We use it for creating web service applications and MQs in various projects such as OberDx, digital importing, and the banking sector. I also use MQs and the administrator application for various tasks.

The solution has two main parts: integration and transformation. It's very user-friendly and easy to understand for everyone. When we talk about MQ, we can save any type of message, such as a string or JSON, in the memory. 

The second thing is the compute node, which is useful for security purposes as it allows us to transform into other languages or call specific functions. It's very helpful for us.

Our needs are mainly focused on the ESB side. We use the product to fill our enterprise service bus scenarios or needs.

The usage has been very good. It's more than sufficient. 

It's a stable product.

My company has a very minimal in-house software development team to develop some mobile applications and workflow integrations.

WSO2 API Manager can be described as one of the valuable features that is attached to WSO2 Enterprise Integrator.

Our company requires every feature in the product. The IDE, the development-related areas, some of the integrations with multiple applications, reporting, dashboards, APIs, and security are some of the areas in the product that are valuable for my company. Customers mostly want an end-to-end API-related solution. The customer wants the product to offer open-source protocols. I believe that WSO2 Enterprise Integrator is a part of an open-source community.

It is used for orchestrating APIs and exposing arrays. For instance, let's say they have some self-service down screens where they need to fetch multiple data from multiple servers and present it to our server in a uniform JSON format. That's the main purpose for which they use it. I am currently working with a telco.

In the telco industry, for example, when someone wants to know their balance, they first check if the user exists and then retrieve the user's current balance. These are two separate endpoints from where this information is obtained. So, they use WSO2 Enterprise Integrator to perform the necessary checks in their database to determine if the user exists and then fetch the data. It involves orchestrating various endpoints and presenting the data uniformly to the caller or the client.

Currently, I find the configuration part quite valuable, where you can easily configure things. Additionally, the integration studio has significantly improved since we first used it. So, the integration studio is good, and the rest of the features are quite similar. I don't think it's very different from any other ESB or EAI.

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. 

Since we have already built all the systems, WSO2 helps us to make the software compatible with each other. WSO2 makes those systems work together like a team. This has allowed us to consult the data and endpoints, reach out to the message and transform it. 

We use WSO2 Enterprise Integrator in our center.

I am a consultant specializing in integrating Peoplesoft and SAP HAP with Eyebox using WSO2 Enterprise Integrator. I have written articles about this technology on my LinkedIn profile.

The banks and government entities use this solution.

WSO2 Enterprise Integrator facilitates the integration of different systems and the exposure of services within an IT ecosystem. It has functionalities such as service exposure and consumption from other entities.

WSO2's analytics capability is good, considering the ELC support they provide. They have an offering for the cloud. Mostly, ELC serves the right purpose.