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

"The MFT component of webMethods, for example, is easy to set up and convenient to use. It handles files very efficiently and it is easy to automate tasks with complex schedules. Monitoring is centralized to MWS which can be used to monitor other products as well (Trading Networks, BPM, MFT, etc.)"

"​Broker and UM are the best features."

"Ease of implementation and flexibility to hold the business logic are the most valuable features."

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

"Our use case is for integration factory for SAP. It is mostly for SAP integration."

"The most valuable feature of the webMethods Integration Server is the built-in monitoring, auditing, RETS, and SOAP services."

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

"It is a bundled product stack for A2A and B2B usage. It is one of the best products which I have used during my integration career."

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

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

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

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

"I would like the solution to provide bi-weekly updates."

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

"The initial setup of the webMethods Integration Server is not easy but it gets easier once you know it. It is tiresome but not difficult."

"It would be nice if they had a change management system offering. We built our own deployer application because the one built into webMethods couldn't enforce change management rules. Integration into a change management system, along with the version control system, would be a good offering; it's something that they're lacking."

"The installation process should be simplified for first time users and be made more user-friendly."

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

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

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

"Initialy good pricing and good, if it comes to Enterprise license agreements."

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

"This is not a cheap solution but, compared to other products such as those offered by IBM, the pricing is similar."

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

"It is expensive, but we reached a good agreement with the company. It is still a little bit expensive, but we got a better deal than the previous one."

"Sometimes we don't have a very clear idea what the licensing will entail at first, because it can be very customizable. On one hand, this can be a good thing, because it can be tailored to a specific customer's needs. But on the other hand it can also be an issue when some customer asks, "What's the cost?" and we can't yet give them an accurate answer."

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

"The pricing and licensing costs for webMethods are very high, which is the only reason that we might switch to another product."