OpenText Trading Grid vs webMethods.io comparison

"The solution is easy to implement."

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

"When it comes to the user interface, I'm already really used to it. I cannot say anything against it. For me, it's easy to use."

"It's obvious that the heart of the product lies here. It's comprised of all aspects of ESB (Enterprise Gateway, Adapter, TN, Java) and BPM (task, rules engine)."

"Oracle's self-service capabilities, of which we make extensive use, is the most valuable feature."

"The synchronous and asynchronous messaging system the solution provides is very good."

"The comprehensiveness and depth of Integration Servers' connectors to packaged apps and custom apps is unlimited. They have a connector for everything. If they don't, you can build it yourself. Or oftentimes, if there is value for other customers as well, you can talk with webMethods about creating a new adapter for you."

"Within the new version, webMethods API Gateway gives us an end-to-end lifecycle from the creation of the API up into the development, deployment, and promotion into production/live. The current end-to-end lifecycle of the API gives us enough authority and governance of the API. We know what are currently live services, what is in the testing stage of development, and what version that has been commissioned. So, the full life cycle itself gives us full authority and governance of the API."

"The tool is very powerful and user-friendly."

"Technical support needs to be better."

"The logging capability has room for improvement. That way, we could keep a history of all the transactions. It would be helpful to be able to get to that without having to build a standalone solution to do so."

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

"Support is expensive."

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

"webMethods.io needs to incorporate ChatGPT to enhance user experience. It can offer a customized user experience."

"Some things could be improved, especially how ActiveTransfer handles third-party file transfers. It would be nice to have a native file-watching mechanism for when you're scheduling jobs with a third-party scheduler. Currently, we are using an outside file watcher solution to check the files before the file transfer. It checks the location to see if the file is there. If the file is there, it will prepare it for transfer. If the file isn't available, it will send an email it can create a ticket send it now. We recommended adding this file watcher mechanism."

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

"Rules engine processes and BPM processes should be improved."

"I do see a lack of capabilities inside of the monetization area for them. They have a cloud infrastructure that is pay per use type of a thing. If you already use 1,000 transactions per se, then you can be charged and billed. I see room for improvement there for their side on that particular capability of the monetization."

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

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

"Its cost depends on the use cases."

"The product is very expensive."

"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 is a little bit high, especially regarding their support."

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