We performed a comparison between Pega BPM and webMethods Integration Server based on real PeerSpot user reviews.
Find out in this report how the two Business Process Management (BPM) solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The best part of Pega, for me, is that they let you reuse a lot of the aspects in the product."
"The interface is quite simple and easy to use, even for beginners."
"Allowed us to develop and quickly release with confidence using cloud technologies."
"Pega is a local platform that has evolved from a BPM perspective. This allows teams using this solution to address complexities without having deep knowledge in a specific development area."
"The case management is great."
"The solution provides us with a very good dashboard."
"There is a feature to accelerate the development so that business analysts can directly create their user stories and assign the task to the developers."
"It is a stable product."
"The most valuable feature of the webMethods Integration Server is the built-in monitoring, auditing, RETS, and SOAP services."
"What I found most valuable in webMethods Integration Server is that it's a strong ESB. It also has strong API modules and portals."
"The Software AG Designer has been great. It's very intuitive."
"It's very flexible and a good platform to use."
"Given that you have one integration API in place, it takes very minimal effort to scale it to any other application that might want to use the same. Its flow-based development environment is a breeze and makes it really easy to re-use most of the existing components and build up a new API."
"I feel comfortable using this product with its ease of building interfaces for developers. This is a better integration tool for integrating with various applications like Oracle, Salesforce, mainframes, etc. It works fine in the integration of legacy software as well."
"The tool is very powerful and user-friendly."
"Best feature is Insight for monitoring, and as a debugging tool. It has saved us a lot of time during crisis situations."
"I believe that Pega's strategy when it comes to the UX part is not that great currently as compared to the other emerging BPM tools in the market."
"The training aspect of Pega BPM requires significant enhancement. There should be more opportunities for third-party training and engaging events, such as hackathons where individuals can share their expertise. Additionally, the training structure itself should be more organized, as I have received feedback from my colleagues in the COE that the current training approach is overwhelming and requires excessive referencing to obtain accurate information. Another area for improvement would be the user experience with regard to RPA. Simplifying the IDA for citizen developers would make it easier for them to adopt the RPA tool."
"The UI part needs improvement."
"What should be included is some UI features and maybe some integrations. This includes documentation on how the UI works."
"Pega is claiming they're into low code but as per Gartner Magic Quadrant, Pega is not there now."
"Pega BPM could be improved by including token-based authentication and extending its integration options."
"They are currently spending some time on improving the product with respect to machine learning, especially related to robotic automation. They probably could be a little more adept on that area would help."
"The solution would benefit from more integration capabilities."
"This product is for larger companies. Compared to TIBCO I think webMethods is better in terms of ease of use and support."
"Forced migration from MessageBroker to Universal Messaging requires large scale reimplementation for JMS."
"The solution has big instances when deployed under microservices or in a containerized platform. They need to improve that so that it is competitive with other integration solutions, like Redis and Kafka. Deployments under microservices with those solutions are much more lightweight, in the size of the runtime itself, compared with Software AG."
"The Software AG Designer could be more memory-efficient or CPU-efficient so that we can use it with middle-spec hardware."
"t doesn't represent OOP very well, just a method and proprietary interface called IData."
"Support is expensive."
"I would like to see the price improve."
"Documentation needs tuning. There is a lot of dependency with SoftwareAG. Even with the documentation at hand, you can struggle to implement scenarios without SAG’s help. By contrast, IBM’s documentation is self-explanatory, in my opinion."
More webMethods Integration Server Pricing and Cost Advice →
Pega BPM is ranked 3rd in Business Process Management (BPM) with 57 reviews while webMethods Integration Server is ranked 3rd in Enterprise Service Bus (ESB) with 60 reviews. Pega BPM is rated 8.2, while webMethods Integration Server is rated 8.0. The top reviewer of Pega BPM writes "Provides built-in frameworks that can be reused and reduces time and cost". On the other hand, the top reviewer of webMethods Integration Server writes "Event-driven with lots of helpful formats, but minimal learning resources available". Pega BPM is most compared with ServiceNow, Camunda, Appian, IBM BPM and Microsoft Power Apps, whereas webMethods Integration Server is most compared with IBM Integration Bus, webMethods.io Integration, Mule ESB, TIBCO BusinessWorks and Boomi iPaaS. See our Pega BPM vs. webMethods Integration Server report.
We monitor all Business Process Management (BPM) reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.