OpenText Trading Grid vs webMethods.io comparison

"The solution is easy to implement."

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

"webMethods platform is used to build an EAI platform, enabling communication between many internal systems and third-party operators."

"I like the stability of the webMethods Integration Server."

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

"The developer portal is a valuable feature."

"The solution's ease-of-use is its most valuable feature, in which complex issues may be resolved."

"The performance is good."

"All of the components are very independent but are tied together to give the business value."

"Technical support needs to be better."

"The configuring of the JWT token would be improved as it is a confusing process. We require more information on this part of the solution."

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

"One area that needs improvement is the version upgrade process. Many customers I've worked with encounter challenges when transitioning from their current version, such as x or 9, to a newer version. The process is not smooth, and they must shift their entire website."

"The patching of infrastructure is not very smooth and improved authentication should be added in the next feature."

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

"The certifications and learning resources are not exposed openly enough. For instance, they have a trial version which comes with only a few basic features, and I think that community-wise they need to offer more free or open spaces where developers can feel encouraged to experiment."

"As webMethods Integration Server is expensive, that's its area for improvement."

"The price has room for improvement."

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

"The vendor is flexible with respect to pricing."

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

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

"I would like to see better pricing for the license."

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

"I do think webMethods is coming under increasing pressure when it comes to their price-to-feature value proposition. It's probably the single biggest strategic risk they have. They're very expensive in their industry. They've been raising the price recently, especially when compared with their competitors."