Most Helpful Review
Find out what your peers are saying about Pega BPM vs. webMethods Integration Server and others in Business Process Management.
295,762 professionals have used our research since 2012.
It cuts down the time taken for coding. Earlier it used take for us four hours to do a particular code. Now this can be done in less than 30 minutes. That's the kind of productivity gains you can get.
The user interface and the ease of developing the workflow for an application are valuable features.
Decreased time for plane departures and landing, supported analytical insight for planning of three to six month forecasting, and helped with operational decision planning and support.
Allowed us to develop and quickly release with confidence using cloud technologies.
We have a reusable code that we can replicate for any new interfaces.
The main assets are its flow language, debugging, and Broker. Flow language is far better and more flexible for debugging.
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.)
Application integration, business process integration, and B2B partner integration are valuable. But among these, I feel B2B partner integration is the most valuable. This module integrates two business partners and exchanges data through electronic data interchange messages in the form of specific standards, without any manual process needed.
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.
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.
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.
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 biggest thing I have seen is when going from one version to another and upgrading to the latest version, it takes a pretty long time for an organization to go through an upgrade process. I think that's an area where they can make it a little smoother.
There have been some performance scalability issues. Suppose you want to add more users. You go from, say, 800 users to 1,500 users, and sometimes that creates issues for which there is no clear explanation. To fix it you have to escalate it with customer service and sometimes the response is not up to the mark in resolving those issues.
It is scalable, but it also interacts with a lot of other systems. I think they thought that the interface to other systems, legacy systems, was its strength, but when problems do occur, quickly diagnosing those problems has been a challenge.
Pega Cloud early adoption and use for cross enterprise capability was new to many. The early adoption meant version 2.0 of their cloud service may require refactoring and redesign of some services.
Business specific functionality is needed.
We got the product via a reseller, and the support from the reseller has been less than desirable.
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.
When migration happens from the one release to an upgraded release from Software AG, many of the existing services are deprecated and developers have to put in effort testing and redeveloping some of the services. It would be better that upgrade releases took care to support the lower-level versions of webMethods.
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.
The product needs to be improved in a few ways. First, they need to stabilize the components of the whole platform across versions. Also, they should stop replacing old components with brand new ones and, rather, improve by evolution.
Large file handling is pretty hard comparatively to other middleware tools.
Business monitoring (BAM) needs improvement because the analytics and prediction module very often has performance problems.
This product has too many gaps. You find them after update installations. This should be covered by automatic testing.
Pricing and Cost Advice
They have both on-premise and cloud licensing. If you are a small to medium company, go for the cloud option because that eliminates a lot of the setting up of your DevTest and performance environments, multiple environments, because you can buy that from Pega with the cloud option. So your setup time really goes down. If you're a large company, then you're better off putting it within your company. You have other skill resources within your company to create environments.
They need to come up with licensing options. Right now they do have a cloud-based option, but the cloud prices I've seen are much more expensive compared to competing products.
Licensing is expensive. You need to wisely select between per user and per case.
Pricing has to be negotiated with the local Software AG representative. SAG can always prepare an appropriate pricing model for every client.
Always plan five years ahead and don’t jeopardize the quality of your project by dropping items from the bill of materials.
Some of the licensing is "component-ized," which is confusing to new users/customers.
It is worth the cost.
Initialy good pricing and good, if it comes to Enterprise license agreements.
Compared 18% of the time.
Compared 14% of the time.
See more Pega BPM competitors »
Compared 8% of the time.
Compared 28% of the time.
Compared 9% of the time.
See more webMethods Integration Server competitors »
Compared 6% of the time.
Also Known As
|Also Known As||Pegasystems, SmartBPM|
Pega BPM helps you simplify and automate your operations so that you can reduce costs and improve business agility. Pega's unique Build For Change technology delivers repeatable solutions that can be efficiently reused and tailored to meet the requirements of diverse customers, product lines, channels, and geographies.
The award-winning webMethods Integration Server, our Enterprise Service Bus (ESB), is a complete enterprise application integration solution. It's standards-based so it "speaks" any technology. You can integrate any technology from any vendor: ERP systems, databases, mainframes and legacy apps. SaaS platforms, Web services, JMS messaging systems and packaged apps.
Learn more about Pega BPM
Learn more about webMethods Integration Server
|Sample Customers||The State of Maine, ANZ, Coca-Cola, Department for Environment, Food & Rural Affairs (DEFRA), ME, New South Wales, OptumRx, Texas Department of Transportation, UnitedHealthcare Medicare & Retirement||Fujitsu, Coca Cola, ING, Credit Suisse, Electrolux, GTA, CosmosDirekt|
VISITORS READING REVIEWS
VISITORS READING REVIEWS
No Data Available
VISITORS READING REVIEWS