We performed a comparison between JBoss ESB and webMethods Integration Server based on real PeerSpot user reviews.
Find out what your peers are saying about IBM, MuleSoft, Software AG and others in Enterprise Service Bus (ESB)."The solution is very easy to use. I can download the trial version and just give it a go."
"The main assets are its flow language, debugging, and Broker. Flow language is far better and more flexible for debugging."
"Application integrations are offered out-of-the-box, and that is extremely important to us. This is one of the main use cases that we have for it. It is about 60 to 70 percent of the workload in our application today."
"webMethods platform is used to build an EAI platform, enabling communication between many internal systems and third-party operators."
"webMethods Integration Server is an easy-to-use solution and does not require a lot of coding."
"We can arrange data caching and look at the solid state. Also, the API gateway is a very good component that can handle relevant cachings and integrations, as well as and also load permitting."
"All of the components are very independent but are tied together to give the business value."
"The product is very stable."
"A product with good API and EDI components."
"The EPA, from what I understand, lacks a lot of features and it doesn't really know how to interface with legacy systems or how to develop APIs for legacy systems."
"Need to see more API portal features like monetizing APIs and private cloud readiness."
"We got the product via a reseller, and the support from the reseller has been less than desirable."
"Upgrades are complex. They typically take about five months from start to finish. There are many packages that plug into webMethods Integration Server, which is the central point for a vast majority of the transactions at my organization. Anytime we are upgrading that, there are complexities within each component that we must understand. That makes any upgrade very cumbersome and complicated. That has been my experience at this company. Because there are many different business units that we are touching, there are so many different components that we are touching. The amount of READMEs that you have to go through takes some time."
"For code version control, you need to use some external software."
"In terms of scale, I would give it a four out of 10."
"The logging capability has room for improvement. That way, we could keep a history of all the transactions. It would be helpful to be able to get to that without having to build a standalone solution to do so."
"The initial setup of the webMethods Integration Server is not easy but it gets easier once you know it. It is tiresome but not difficult."
"As webMethods Integration Server is expensive, that's its area for improvement."
More webMethods Integration Server Pricing and Cost Advice →
Earn 20 points
JBoss ESB is ranked 14th in Enterprise Service Bus (ESB) while webMethods Integration Server is ranked 3rd in Enterprise Service Bus (ESB) with 60 reviews. JBoss ESB is rated 7.0, while webMethods Integration Server is rated 8.0. The top reviewer of JBoss ESB writes "Easy to use with flexible pricing, but needs more flexibility surrounding integrations". On the other hand, the top reviewer of webMethods Integration Server writes "Event-driven with lots of helpful formats, but minimal learning resources available". JBoss ESB is most compared with Mule ESB, Red Hat Fuse, Oracle Service Bus and IBM Integration Bus, whereas webMethods Integration Server is most compared with IBM Integration Bus, webMethods.io Integration, Mule ESB, TIBCO BusinessWorks and Boomi iPaaS.
See our list of best Enterprise Service Bus (ESB) vendors.
We monitor all Enterprise Service Bus (ESB) 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.