OpenText Trading Grid vs webMethods.io comparison

"The solution is easy to implement."

"It frankly fills the gap between IT and business by having approval and policy enforcement on each state and cycle of the asset from the moment it gets created until it is retired."

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

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

"There's hardware, software and application integration, providing hosting flexibility."

"I would say the core Web-based integrations work the best. They are the most efficient and robust implementations one can do with webMethods."

"What I like best about webMethods Integration Server is its portfolio of connectors."

"​Broker and UM are the best features."

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

"Technical support needs to be better."

"Business monitoring (BAM) needs improvement because the analytics and prediction module very often has performance problems."

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

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

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

"webMethods Integration Server needs to add more adapters."

"The interface needs some work. It is not very user-friendly."

"Rapid application development has to be considered, especially for UI, where user interference is crucial."

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

"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 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 solution's development license is free for three to six months. We have to pay for other things."

"The pricing is a yearly license."

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

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

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

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