OpenText Trading Grid vs webMethods.io comparison

"The solution is easy to implement."

"The tool helps us to streamline data integration. Its BPM is very strong and powerful. The solution helps us manage digital transformation."

"The most valuable feature of the webMethods Integration Server is its reliability. It has a lot of great documentation from the service providers. Additionally, it is easy to use."

"A product with good API and EDI components."

"The most valuable feature is stability."

"The core product can be used not only for automatic file transfers between applications, but also as an Enterprise Service Bus (ESB)."

"Best feature is Insight for monitoring, and as a debugging tool. It has saved us a lot of time during crisis situations."

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

"They are the building blocks of EAI in SAG products, and they offer a very good platform."

"Technical support needs to be better."

"I am not satisfied with the solution because it takes too much effort to migrate and add new information. The migration could be easier."

"This product has too many gaps. You find them after update installations. This should be covered by automatic testing."

"When migration happens from the one release to an upgraded release from Software AG, many of the existing services are deprecated and developers have to put in effort testing and redeveloping some of the services. It would be better that upgrade releases took care to support the lower-level versions of webMethods."

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

"It is quite expensive."

"A while ago, they were hacked, and it took them a very long time to open their website again in order to download any service packs or any features. I don't know what they could do differently. I know that they were vulnerable, and there was some downtime, but because they were down, we were unable to download any potential service packs."

"We need more dashboards and reporting engines that can provide detailed information for management. In short, we need better analytics."

"The initial setup of the webMethods Integration Server is not easy but it gets easier once you know it. It is tiresome but not difficult."

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

"The solution's development license is free for three to six months. We have to pay for other things."

"Always plan five years ahead and don’t jeopardize the quality of your project by dropping items from the bill of materials."

"webMethods Trading Networks is a bit costly compared to others solutions."

"The product is very expensive."

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

"Some of the licensing is "component-ized," which is confusing to new users/customers."

"The price is high and I give it a five out of ten."