OpenText MBPM vs webMethods.io comparison

"Not just the solution's automation capabilities, but we like everything about it since we are more of a system integrator."

"Clients choose webMethods.io API for its intuitive interface, promoting seamless interaction and quick communication between systems."

"The product is powerful, straightforward, and easy to use."

"What I found most valuable in webMethods Integration Server is that it's a strong ESB. It also has strong API modules and portals."

"One of the most important features is that it gives you the possibility to do low-level integration. It provides a lot of features out of the box, and over the years, it has matured so much that any problem that is there in the market can be solved with this product. We can meet any requirements through customizations, transformations, or the logic that needs to be put in. Some of the other products struggle in this aspect. They cannot do things in a certain way, or they have a product limitation, whereas, with webMethods, I have never faced this kind of problem."

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

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

"It’s fairly easy to view, move, and mange access across different components. Different component types are categorized and can be viewed in a web based administration console."

"The connectivity that the tool provides, along with the functionalities needed for our company's business, are some of the beneficial aspects of the product."

"The user interface could be better in OpenText MBPM."

"There are shortcomings in the solution's support and documentation part."

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

"I'd like to see the admin portal for managing the integration server go up a level, to have more capabilities and to be given a more modern web interface."

"Prices should be reduced, ideally by up to 30% for long-term customers like us."

"I would like to have a dashboard where I can see all of the communication between components and the configuration."

"The learning curve is a little steep at first."

"Version control is not very easy. The packages and the integration server are on Eclipse IDE, but you can't compare the code from the IDE. For example, if you are working on Java code, doing version control and deployment for a quick comparison between the code isn't easy. Some tools or plug-ins are there, such as CrossVista, and you can also play with an SVN server where you have to place your package, and from there, you can check, but you have to do that as a separate exercise. You can't do it from the IDE or webMethods server. You can't just right-click and upload your service."

"The stability of the various modules of the product suite have been a bit of a concern lately. Though their support team is always easy to reach out to, I would prefer it not come to that."

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

"There is an annual license to use OpenText MBPM."

"On a scale of one to ten, where one is cost-efficient, and ten is expensive, I rate the pricing somewhere between nine and ten since it is a costly solution."

"Always plan five years ahead and don’t jeopardize the quality of your project by dropping items from the bill of materials."

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

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

"The solution’s pricing is too high."

"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 vendor is flexible with respect to pricing."

"There is a license needed to use the webMethods Integration Server."

"It is a cost-effective solution."