WSO2 Enterprise Integrator vs webMethods.io comparison

"The messaging part is the most valuable feature."

"The developer portal is a valuable feature."

"The main assets are its flow language, debugging, and Broker. Flow language is far better and more flexible for debugging."

"The product supports various types of digital documents, including XMLs and EDI."

"This solution has given us a competitive advantage because we have better automation and insight."

"The most valuable feature is stability."

"Ease of implementation and flexibility to hold the business logic are the most valuable features."

"What I like the most about the solution is that it comes with ready-made tools like handling security tokens and OAuth."

"The solution's technical support is very knowledgeable."

"The installation process is easy."

"WSO2's analytics capability is good, considering the ELC support they provide."

"The solution's customer service is good."

"It's a very complete product. It allows us to network security and add more layers of security to the system."

"I like the user-friendly system and development of the service-oriented architecture."

"The customer service executives are very responsive."

"Currently, I find the configuration part quite valuable, where you can easily configure things."

"There are things that could be improved with the webMethods API gateway. One thing is that it's too attached to the integration service and we'd like it to be a little bit more independent. We would like for them to separate operations so that it doesn't rely on the bulky integration server and so that it can be used everywhere."

"Version control is not very easy. The packages and the integration server are on Eclipse IDE, but you can't compare the code from the IDE. For example, if you are working on Java code, doing version control and deployment for a quick comparison between the code isn't easy. Some tools or plug-ins are there, such as CrossVista, and you can also play with an SVN server where you have to place your package, and from there, you can check, but you have to do that as a separate exercise. You can't do it from the IDE or webMethods server. You can't just right-click and upload your service."

"There should be better logging, or a better dashboard, to allow you to see see the logs of the services."

"I would like to have a dashboard where I can see all of the communication between components and the configuration."

"Need to see more API portal features like monetizing APIs and private cloud readiness."

"I would like to see the price improve."

"I'd like to see the admin portal for managing the integration server go up a level, to have more capabilities and to be given a more modern web interface."

"wM SAP Adapter User Guide - Example, like Message Broker setup was unclear, leading to issues during Testing and we had refer the internet forums to understand that there is a Message Broker Cleanup utility and that needs to be setup as well."

"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."

"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."

"There are a lot of security settings that when you apply you have to re-apply again every time you modify a setting. It is something that really needs to be enhanced."

"The integration capabilities need to be improved."

"I would like to see them bring back a feature, from earlier versions, that was very useful in debugging and finding issues."

"They should introduce better pricing for small companies."

"The setup can be difficult for those not familiar with the solution."

"WSO2 libraries are not mature enough. For example, if you want to integrate with Kafka using its Kafka library, it often has many bugs."

"The pricing and licensing costs for webMethods are very high, which is the only reason that we might switch to another product."

"The price is a little bit high, especially regarding their support."

"With our current licensing, it's very easy for us to scale. With our older licensing model, it was very hard. This is definitely something that I would highlight."

"It is expensive, but we reached a good agreement with the company. It is still a little bit expensive, but we got a better deal than the previous one."

"I do see a lack of capabilities inside of the monetization area for them. They have a cloud infrastructure that is pay per use type of a thing. If you already use 1,000 transactions per se, then you can be charged and billed. I see room for improvement there for their side on that particular capability of the monetization."

"webMethods.io Integration's pricing is high and has yearly subscription costs."

"Some who consider this solution often avoid it due to its high price."

"There is a license needed to use the webMethods Integration Server."

"It is a low-cost solution."

"The solution costs about 20,000 or 30,000 euros per year, per instance."

"I rate the product price a six on a scale of one to ten, where one is low price and ten is high price."

"The cost is better than IBM Cloud Pak."

"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 open-source, unsupported version is available free of charge."