Try our new research platform with insights from 80,000+ expert users

WSO2 Enterprise Integrator vs webMethods.io comparison

 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

webMethods.io
Ranking in Enterprise Service Bus (ESB)
3rd
Average Rating
8.0
Reviews Sentiment
6.8
Number of Reviews
91
Ranking in other categories
Business-to-Business Middleware (4th), Managed File Transfer (MFT) (10th), API Management (9th), Cloud Data Integration (8th), Integration Platform as a Service (iPaaS) (5th)
WSO2 Enterprise Integrator
Ranking in Enterprise Service Bus (ESB)
7th
Average Rating
7.6
Reviews Sentiment
7.0
Number of Reviews
19
Ranking in other categories
Data Integration (26th)
 

Featured Reviews

Michele Illiano - PeerSpot reviewer
Can function as an ESB along with the core product, with decent integration of message protocols
I have noticed that webMethods ActiveTransfer has had problems when handling large files. For example, when we receive (and perform operations on) files that are larger than about 16 MB, the software starts losing performance. This is why, for most customers who have to deal with big files, I suggest that they use a product other than ActiveTransfer. I would like to note that this problem mainly concerns large files that undergo extra operations, such assigning, unassigning, or file translation. When these operations take place on large files, ActiveTransfer will use up a lot of resources. Within the product itself, I also believe that there is room for improvement in terms of optimization when it comes to general performance. I suspect that the issues underlying poor optimization are because it is all developed in Java. That is, all the objects and functions that are used need to be better organized, especially when it comes to big files but also overall. webMethods ActiveTransfer was born as an ESB to handle messages, and these messages were typically very short, i.e. small in size. A message is data that you have to send to an application, where it must be received in real-time and possibly processed or acknowledged elsewhere in the system as well. So, because it was initially designed for small messages, it struggles with performance when presented with very large files. All this to say, I suggest that they have an engineer reevaluate the architecture of the product in order to consider cases where large files are sent, and not only small ones. As for new features, compared to other products in the market, I think Software AG should be more up to date when it comes to extra protocol support, especially those protocols that other solutions have included in their products by default. Whenever we need to add an unsupported protocol, we have to go through the effort of custom development in order to work with it. Also, all the banks are obligated to migrate to the new standards, and big companies are all handling translations and operating their libraries with the new protocol formats. But webMethods ActiveTransfer doesn't seem to be keeping up with this evolution. Thus, they should aim to be more compliant in future, along the lines of their competitors such as IBM and Primeur.
Ritesh_Shah - PeerSpot reviewer
Decreases the development timeframe and costs
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.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"Most of the work in our organization can be more easily done using the tool."
"Clients choose webMethods.io API for its intuitive interface, promoting seamless interaction and quick communication between systems."
"webMethods Trading Networks is a good solution for interacting with outside of the organization. We can integrate the solutions with multiple outside the organization."
"The tool supports gRPC."
"Application integration, business process integration, and B2B partner integration are valuable. But among these, I feel B2B partner integration is the most valuable. This module integrates two business partners and exchanges data through electronic data interchange messages in the form of specific standards, without any manual process needed."
"The performance is good."
"It has a good integration server, designer, and a very good API portal."
"The most valuable feature of the webMethods Integration Server is the built-in monitoring, auditing, RETS, and SOAP services."
"The customer service executives are very responsive."
"It's a very complete product. It allows us to network security and add more layers of security to the system."
"The drag-and-drop features for connectors are very valuable."
"I like the user-friendly system and development of the service-oriented architecture."
"WSO2's analytics capability is good, considering the ELC support they provide."
"It's a consolidated product. It works and it does its job pretty well."
"The stability is excellent."
"The productivity is the most valuable feature. It is very easy to write remediations."
 

Cons

"Documentation needs tuning. There is a lot of dependency with SoftwareAG. Even with the documentation at hand, you can struggle to implement scenarios without SAG’s help. By contrast, IBM’s documentation is self-explanatory, in my opinion."
"This product is for larger companies. Compared to TIBCO I think webMethods is better in terms of ease of use and support."
"It could be more user-friendly."
"The market webMethods Integration Server falls under is a very crowded market, so for the product to stand out, Software AG would need to get traction in the open source community by releasing a new version or a base version and open source it, so people can create new custom components and add it to the portfolio."
"The price should be reduced to make it more affordable."
"I would like to have a dashboard where I can see all of the communication between components and the configuration."
"For code version control, you need to use some external software."
"Business monitoring (BAM) needs improvement because the analytics and prediction module very often has performance problems."
"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."
"I would like to see them bring back a feature, from earlier versions, that was very useful in debugging and finding issues."
"The setup can be difficult for those not familiar with the solution."
"In my opinion, the administration model and interface, of Carbon, are lacking in terms of its features and user experience."
"The micro integrator should be improved. There is room for enhancement considering alternative integration components."
"If I have to buy software, then it becomes expensive for me."
"One of the reasons that we are looking for a replacement is their way of defining integration. The language of the XML structures that I use to describe the integrations are not that standard, and it's not easy to find people who are familiar with this approach."
"WSO2 libraries are not mature enough. For example, if you want to integrate with Kafka using its Kafka library, it often has many bugs."
 

Pricing and Cost Advice

"Pricing has to be negotiated with the local Software AG representative. SAG can always prepare an appropriate pricing model for every client."
"The product is expensive."
"The price of webMethods Integration Server isn't that high from an enterprise context, but open-source ESB solutions will always be the cheapest."
"Pricing is the number-one downfall. It's too expensive. They could make more money by dropping the price in half and getting more customers. It's the best product there is, but it's too expensive."
"Always plan five years ahead and don’t jeopardize the quality of your project by dropping items from the bill of materials."
"I would like to see better pricing for the license."
"This is an expensive product and we may replace it with something more reasonably priced."
"webMethods Trading Networks is a bit costly compared to others solutions."
"The solution costs about 20,000 or 30,000 euros per year, per instance."
"The pricing of WSO2 Enterprise Integrator for enterprise subscriptions can be considered expensive, especially from the perspective of someone who prefers open-source software."
"The cost is better than IBM Cloud Pak."
"The open-source, unsupported version is available free of charge."
"It is a low-cost solution."
"I rate the product price a six on a scale of one to ten, where one is low price and ten is high price."
report
Use our free recommendation engine to learn which Enterprise Service Bus (ESB) solutions are best for your needs.
831,020 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
13%
Computer Software Company
13%
Manufacturing Company
13%
Retailer
7%
Computer Software Company
28%
Financial Services Firm
15%
Manufacturing Company
6%
Government
4%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about Built.io Flow?
The tool helps us to streamline data integration. Its BPM is very strong and powerful. The solution helps us manage digital transformation.
What is your experience regarding pricing and costs for Built.io Flow?
webMethods.io is expensive. We have multiple components, and you need to pay for each of them.
What needs improvement with Built.io Flow?
webMethods.io needs to incorporate ChatGPT to enhance user experience. It can offer a customized user experience.
What do you like most about WSO2 Enterprise Integrator?
WSO2's analytics capability is good, considering the ELC support they provide.
What is your experience regarding pricing and costs for WSO2 Enterprise Integrator?
The product has reasonable and competitive pricing for enterprise customers. It is expensive for small businesses especially. They are using the open-source solution, and they find it expensive sin...
What needs improvement with WSO2 Enterprise Integrator?
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 e...
 

Also Known As

Built.io Flow, webMethods Integration Server, webMethods Trading Networks, webMethods ActiveTransfer, webMethods.io API
No data available
 

Learn More

Video not available
 

Overview

 

Sample Customers

Cisco, Agralogics, Dreamforce, Cables & Sensors, Sacramento Kings
West
Find out what your peers are saying about WSO2 Enterprise Integrator vs. webMethods.io and other solutions. Updated: January 2025.
831,020 professionals have used our research since 2012.