Most Helpful Review
Find out what your peers are saying about Mule ESB vs. webMethods Integration Server and other solutions. Updated: January 2019.
316,375 professionals have used our research since 2012.
We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
The architecture based on events has several connectors which allow integration from external and internal applications of the company.
Scalability and load balancing.
We can use Java expressions anywhere in the flow.
Mule Expression Language
It's obvious that the heart of the product lies here. It's comprised of all aspects of ESB (Enterprise Gateway, Adapter, TN, Java) and BPM (task, rules engine).
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.
The payment system needs improvement.
Limitation on external subscribers to listen to the messages on the bus.
It needs more samples. Also, the dependency on Maven should be removed.
Documentation is cryptic, product releases are far too frequent, and upgrades become troublesome.
t doesn't represent OOP very well, just a method and proprietary interface called IData.
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.
Pricing and Cost Advice
Plan your licensing model (cloud or on-premises or hybrid) that will allow seamless integration with new partners.
This is expensive. In my next project, we had to go to other vendor.
Some of the licensing is "component-ized," which is confusing to new users/customers.
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.
It is worth the cost.
Initialy good pricing and good, if it comes to Enterprise license agreements.
out of 24 in ESB
out of 24 in ESB
Compared 21% of the time.
Compared 21% of the time.
Compared 10% of the time.
Compared 33% of the time.
Compared 9% of the time.
Compared 7% of the time.
|For companies looking to modernize and unlock the value of existing on-premises systems and applications, an enterprise service bus (ESB) architecture serves as a critical foundation layer for SOA. When deployed as an ESB, the Mule runtime engine of Anypoint Platform combines the power of data and application integration across legacy systems and SaaS applications, with a seamless path to the other capabilities of Anypoint Platform and the full power of API-led connectivity.|
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 Mule ESB
Learn more about webMethods Integration Server
|Ube, PacificComp, University of Witwatersrand, Justice Systems, Camelot||Fujitsu, Coca Cola, ING, Credit Suisse, Electrolux, GTA, CosmosDirekt|
Financial Services Firm27%
Comms Service Provider9%
Financial Services Firm14%
Comms Service Provider10%