Most Helpful Review
Find out what your peers are saying about IBM Integration Bus vs. webMethods Integration Server and others in ESB.
295,762 professionals have used our research since 2012.
It is one of the most stable products which I have seen in the market.
Easy to understand documentation with a huge list of examples and tutorials.
Web interface, REST API for viewing services, admin, stats, and deployment are premium features, which makes IIB stand among its competition.
REST API design and development support are useful. Building and exposing APIs using GUI API designer with editor makes implementation a breeze.
IBM support is fantastic and quick.
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.
IBM does not support orchestration, which is how they designed it, and other BPM tools in the market support orchestration. If they merged the BPM capability into this product, then it would be a better solution.
Development toolkit (based on Eclipse) should be improved in terms of responsiveness.
Current aggregation implementation should be deprecated. MQ independent, as well as an intuitive solution, should be proposed.
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
Support costs are high compared to the competition. Otherwise, the support is good.
Pricing is on par with its competition.
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 32% of the time.
Compared 14% of the time.
See more IBM Integration Bus competitors »
Compared 13% 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||IBM WebSphere ESB|
|Overview||IBM Integration Bus is an enterprise integration engine that offers a fast, simple way for systems and applications to communicate with each other. As a result, it can help you achieve business value, reduce IT complexity and save money.|
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 IBM Integration Bus
Learn more about webMethods Integration Server
|Sample Customers||Salesbox, €sterreichische Bundesbahnen (€BB), Road Buddy, Swiss Federal Railways, Electricity Supply Board, The Hartree Centre, ESB Networks||Fujitsu, Coca Cola, ING, Credit Suisse, Electrolux, GTA, CosmosDirekt|
VISITORS READING REVIEWS
VISITORS READING REVIEWS
No Data Available
VISITORS READING REVIEWS