We performed a comparison between webMethods Integration Server and WSO2 Enterprise Integrator based on real PeerSpot user reviews.
Find out in this report how the two Enterprise Service Bus (ESB) solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."What I like best about webMethods Integration Server is its portfolio of connectors."
"From a user perspective, the feature which I like the most about Integration Server is its designer."
"A product with good API and EDI components."
"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)."
"It has a good integration server, designer, and a very good API portal."
"One valuable feature is that it is event-driven, so when new data is available on the source it can be quickly processed and displayed. Integration is definitely another useful feature, and B2B is one area where webMethods has its own unique thing going, whereby we can do monitoring of transactions, monitoring of client onboarding, and so on."
"The development is very fast. If you know what you're doing, you can develop something very easily and very fast."
"Some of the key features are the integration platform, query mechanism, message handling within the bus, and the rules engine. We've had a really good experience with webMethods Integration Server."
"I like the user-friendly system and development of the service-oriented architecture."
"The solution's technical support is very knowledgeable."
"It's a consolidated product. It works and it does its job pretty well."
"The solution's customer service is good."
"The solution basically conforms to our standards."
"It's a very complete product. It allows us to network security and add more layers of security to the system."
"WSO2's analytics capability is good, considering the ELC support they provide."
"The learning curve for this solution is very good."
"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."
"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."
"Version control is not very easy. The packages and the integration server are on Eclipse IDE, but you can't compare the code from the IDE. For example, if you are working on Java code, doing version control and deployment for a quick comparison between the code isn't easy. Some tools or plug-ins are there, such as CrossVista, and you can also play with an SVN server where you have to place your package, and from there, you can check, but you have to do that as a separate exercise. You can't do it from the IDE or webMethods server. You can't just right-click and upload your service."
"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."
"The solution has big instances when deployed under microservices or in a containerized platform. They need to improve that so that it is competitive with other integration solutions, like Redis and Kafka. Deployments under microservices with those solutions are much more lightweight, in the size of the runtime itself, compared with Software AG."
"This product is for larger companies. Compared to TIBCO I think webMethods is better in terms of ease of use and support."
"I would like to have a dashboard where I can see all of the communication between components and the configuration."
"Forced migration from MessageBroker to Universal Messaging requires large scale reimplementation for JMS."
"You cannot include the validation of XPath."
"The product's price is an area of concern where improvements are required."
"The administration side is complex and could use significant improvements to enhance the solution's functionality."
"They should introduce better pricing for small companies."
"The server is very specific and it is very difficult to get experience with it."
"They should release upgrades more frequently."
"If I have to buy software, then it becomes expensive for me."
"I would like to see better documentation for the open-source version."
More webMethods Integration Server Pricing and Cost Advice →
webMethods Integration Server is ranked 3rd in Enterprise Service Bus (ESB) with 60 reviews while WSO2 Enterprise Integrator is ranked 7th in Enterprise Service Bus (ESB) with 18 reviews. webMethods Integration Server is rated 8.0, while WSO2 Enterprise Integrator is rated 7.6. The top reviewer of webMethods Integration Server writes "Event-driven with lots of helpful formats, but minimal learning resources available". On the other hand, the top reviewer of WSO2 Enterprise Integrator writes "Consolidated, reliable, and has responsive technical support". webMethods Integration Server is most compared with IBM Integration Bus, webMethods.io Integration, Mule ESB, TIBCO BusinessWorks and IBM BPM, whereas WSO2 Enterprise Integrator is most compared with Red Hat Fuse, IBM Integration Bus, Oracle Service Bus, Talend Open Studio and Mule ESB. See our WSO2 Enterprise Integrator vs. webMethods Integration Server report.
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.
