Magic xpi Integration Platform vs webMethods.io comparison

"The stability of the solution is OK."

"EDI is robust and integration with SAP is good."

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

"It's easy to construct new interfaces like apps and client portals."

"I like the stability of the webMethods Integration Server."

"It's a good tool, and it has a stable messaging broker."

"Clients choose webMethods.io API for its intuitive interface, promoting seamless interaction and quick communication between systems."

"With webMethods, the creation of servers and the utilization of Trading Networks facilitate B2B integration. It resolves any related issues effectively."

"It is a very stable product."

"It is not performing well."

"The price has room for improvement."

"The products, at the moment, are new and there should perhaps be support for the older version of the protocols."

"It is an expensive solution and not very suitable for smaller businesses."

"It would be nice if they had a change management system offering. We built our own deployer application because the one built into webMethods couldn't enforce change management rules. Integration into a change management system, along with the version control system, would be a good offering; it's something that they're lacking."

"Upgrades are complex. They typically take about five months from start to finish. There are many packages that plug into webMethods Integration Server, which is the central point for a vast majority of the transactions at my organization. Anytime we are upgrading that, there are complexities within each component that we must understand. That makes any upgrade very cumbersome and complicated. That has been my experience at this company. Because there are many different business units that we are touching, there are so many different components that we are touching. The amount of READMEs that you have to go through takes some time."

"For code version control, you need to use some external software."

"The learning curve is a little steep at first."

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

"Pricing has to be negotiated with the local Software AG representative. SAG can always prepare an appropriate pricing model for every client."

"webMethods Integration Server is expensive, and there's no fixed price on it because it has a point pricing model. You can negotiate, which makes it interesting."

"This is not a cheap solution but, compared to other products such as those offered by IBM, the pricing is similar."

"The product is very expensive."

"Currently, the licensing solution for this product is pretty straightforward. The way that Software AG has moved in their licensing agreements is very understandable. It is very easy for you to see where things land. Like most vendors today, they are transaction based. Therefore, just having a good understanding of how many transactions that you are doing a year would be very wise. Luckily, there are opportunities to work with the vendor to get a good understanding of how many transactions you have and what is the right limit for you to fall under."

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

"Most of my clients would like the price of the solution to be reduced."

"It is an expensive tool. I rate the product price a nine out of ten, where ten means it is very expensive."