Most Helpful Review
Find out what your peers are saying about Oracle Service Bus vs. webMethods Integration Server and others in ESB.
294,620 professionals have used our research since 2012.
It is lightweight and one can easily integrate with different applications, databases, JMS, or web services through different protocols.
It was very good at supporting high transactions, up to 300 transactions per second.
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.
It needs to support more adapters, because the integration points keep changing and new things keep coming up. It also needs to be more scalable.
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
Information Not Available
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 45% of the time.
Compared 12% of the time.
See more Oracle Service Bus competitors »
Compared 11% of the time.
Compared 28% of the time.
Compared 9% of the time.
See more webMethods Integration Server competitors »
Compared 6% of the time.
Oracle Service Bus transforms complex and brittle architectures into agile integration networks by connecting, virtualizing, and managing interactions between services and applications. Oracle Service Bus delivers low-cost, standards-based integration for mission critical SOA environments where extreme performance, scalability and reliability are critical requirements.
Oracle Service Bus enables companies to use the values of their enterprise applications portfolio. From on-premise, to the cloud to mobile devices, Service Bus allows companies to leverage their existing investments in new ways by extending the performance and scalability leadership of Oracle SOA and API Management.
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 Oracle Service Bus
Learn more about webMethods Integration Server
|Sample Customers||MakeMyTrip Ltd., Griffith University, Colab Consulting Pty. Ltd., Pacfico Seguros Generales, IGEPA IT-SERVICE GmbH, Guangzhou Municipal Human Resources and Social Security Bureau, Pacfico Seguros Generales, Bank Audi S.A.L., Rydges Sydney Airport, Intelligent Pathways, Nacional Monte de Piedad IAP||Fujitsu, Coca Cola, ING, Credit Suisse, Electrolux, GTA, CosmosDirekt|
No Data Available
VISITORS READING REVIEWS
No Data Available
VISITORS READING REVIEWS