OpenText Trading Grid vs webMethods.io comparison

"The solution is easy to implement."

"High throughput and excellent scalability."

"It integrates well with various servers."

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

"We have a reusable code that we can replicate for any new interfaces."

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

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

"From a user perspective, the feature which I like the most about Integration Server is its designer."

"ActiveTransfer lets us maintain the file in the staging area before we transfer it. After that, we can remove the file to make sure that the reconciliation process is done. Sometimes we will zip and unzip the files, but if we have a GKB file, we often ignore it."

"Technical support needs to be better."

"With respect to the API gateway, the runtime component, the stability after a new release is something that can be improved."

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

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

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

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

"This product is for larger companies. Compared to TIBCO I think webMethods is better in terms of ease of use and support."

"Technical support is an area where they can improve."

"The improvement needed is related to the model's position. As of now, it seems to be more of a conceptual idea rather than a widely implemented solution. For how long"

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

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

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

"There are no hidden costs in addition to the standard licensing fees for webMethods. For corporate organizations, it's a very cheap or fairly priced product, but for growing or small businesses, it's quite expensive. These businesses would probably need to consider an enterprise services bus at some point. Thus, from a pricing point, it closes out non-cooperate businesses."

"It is a cost-effective solution."

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

"Its cost depends on the use cases."

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