OpenText Trading Grid vs webMethods.io comparison

"The solution is easy to implement."

"The cloud version of the solution is very easy to set up."

"The most valuable aspect of this solution for me has been the configuration-based UI. Once you get the hang of it, it enables you to easily develop an API. In addition, it has many in-built policies that are quite handy."

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

"Segregation of deployment for the environments is the most valuable feature of the solution."

"It has a good integration server, designer, and a very good API portal."

"The solution is scalable."

"Most of the work in our organization can be more easily done using the tool."

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

"The high price of the product is an area of concern where improvements are required."

"Other products have been using AI and cloud enhancements, but webMethods Integration Server is still lagging in that key area."

"The licensing cost is high compared to other options."

"In terms of scale, I would give it a four out of 10."

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

"Forced migration from MessageBroker to Universal Messaging requires large scale reimplementation for JMS."

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

"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's a good deal for the money that we pay."

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

"The price of webMethods Integration Server isn't that high from an enterprise context, but open-source ESB solutions will always be the cheapest."

"I don’t have much idea about prices, but webMethods API Portal is not something cheaper."

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

"The product is expensive."

"It is a cost-effective solution."