IBM B2B Integrator vs webMethods.io comparison

"Out-of-box process orchestration yields quick implementations."

"Very flexible product; it allows implementing different flows on the same infrastructure."

"It uses VMs, allowing us to enable horizontal scaling."

"Everything from the order to fulfillment to the payment process, except for physical packing and shipping, is fully automated for some customer orders."

"The solution is useful for transferring files from one format to another format. Also, the solution is useful in translation."

"The most valuable features are the flexibility and the range of EDI standards that IBM Sterling can handle."

"B2B provides a secure communication channel."

"The best feature is that many companies use the solution so there is a lot of peer support."

"The solution has a very comprehensive and versatile set of connectors. I've been able to utilize it for multiple, different mechanisms. We do a lot of SaaS and we do have IoT devices and the solution is comprehensive in those areas."

"The ease of mapping... is the single largest feature. It gives us the ability to craft anything. A lot of single-purpose technologies, like Mirth, are good for healthcare messages, but we use webMethods not only for healthcare messages but for other business-related purposes, like integrations to Salesforce or integrations to Office 365. It's multi-purpose nature is very strong."

"It is a bundled product stack for A2A and B2B usage. It is one of the best products which I have used during my integration career."

"The solution's ease-of-use is its most valuable feature, in which complex issues may be resolved."

"We needed a tool that was able to orchestrate and help us configure our APIs so that we could maintain and see the heartbeat, traffic, trends, etc."

"Given that you have one integration API in place, it takes very minimal effort to scale it to any other application that might want to use the same. Its flow-based development environment is a breeze and makes it really easy to re-use most of the existing components and build up a new API."

"I like the tool's scalability."

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

"The web interface of B2B is quite outdated and not particularly user-friendly."

"API integration could be improved. The legacy system could be on the cloud."

"The initial setup is complex."

"It supports many of our use cases but falls short in some areas as technology evolves"

"The product does not have default options for PDF generation."

"There should be a single place to do things, rather than making it complicated, not moving away and truncating the old features but instead coming up with the new and still keeping the old stuff confuses people sometimes."

"The one thing that is lacking is easy visibility. It's hard to provide business users with a view into the statuses of their transactions."

"The user interface is outdated. B2B Integrator was developed in the United States in the nineties, and the graphical user interface hasn't improved since. It's tough because you have to program the software in XML. Nowadays, other methods are easier to work with."

"On the monitoring side of things, the UI for monitoring could be improved. It's a bit cumbersome to work with."

"The patching of infrastructure is not very smooth and improved authentication should be added in the next feature."

"This solution could be improved by offering subscription based licensing."

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

"It is difficult to maintain."

"As webMethods Integration Server is expensive, that's its area for improvement."

"The solution should include REST API calls."

"A potential drawback of webMethods.io API is its adaptability to legacy systems, which can vary in compatibility."

"We pay an annual fee based on the number of VPUs. It's fairly reasonable. We're in the middle of analyzing other products, and they're all pretty much in the same range."

"The pricing is based on how many cores are used and the type of cores."

"Licensing depends upon the package you opt for within the solution. The solution is a bit costly compared to the other integration tools in the market."

"The solution is priced at $20,000 to $30,000 per year with no extra costs."

"The price of IBM B2B Integrator is too high. However, IBM may be willing to give a discount if there are negotiations. If they see that there is a good opportunity for them they can provide a discount."

"The product costs more than 40K."

"The product is very expensive."

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

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

"This is an expensive product and we may replace it with something more reasonably priced."

"Based on our team discussions and feedback, it is pretty costly because they charge us for each transmission."

"Sometimes we don't have a very clear idea what the licensing will entail at first, because it can be very customizable. On one hand, this can be a good thing, because it can be tailored to a specific customer's needs. But on the other hand it can also be an issue when some customer asks, "What's the cost?" and we can't yet give them an accurate answer."

"I do think webMethods is coming under increasing pressure when it comes to their price-to-feature value proposition. It's probably the single biggest strategic risk they have. They're very expensive in their industry. They've been raising the price recently, especially when compared with their competitors."

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