We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
"The solution is very easy to work with."
"It's high-speed and it can be remotely administered via an API."
"The API Connect gateway service and the SQL injection feature is good."
"I like all of the features in this product and it does what it's supposed to do."
"It can look for the various security threats, productions, payload scanning, and perform routing based on the content type."
"It is easy to use, easy to install, and it's resilient for high availability."
"What I like most is the stability."
"The scalability of the solution is good."
"All of the components are very independent but are tied together to give the business value."
"The most valuable feature is stability."
"The tool is very powerful and user-friendly."
"The solution has a very comprehensive and versatile set of connectors. I've been able to utilize it for multiple, different mechanisms. We do a lot of SaaS and we do have IoT devices and the solution is comprehensive in those areas."
"One [of the most valuable features] is the webMethods Designer. That helps our developers develop on their own. It's very intuitive for design. It helps our developers to speed the development of services for the integrations."
"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."
"The comprehensiveness and depth of Integration Servers' connectors to packaged apps and custom apps is unlimited. They have a connector for everything. If they don't, you can build it yourself. Or oftentimes, if there is value for other customers as well, you can talk with webMethods about creating a new adapter for you."
"The ease of mapping... is the single largest feature. It gives us the ability to craft anything. A lot of single-purpose technologies, like Mirth, are good for healthcare messages, but we use webMethods not only for healthcare messages but for other business-related purposes, like integrations to Salesforce or integrations to Office 365. It's multi-purpose nature is very strong."
"The solution requires a lot of training manuals in order to get to know it better and to be able to use it effectively."
"The components that they include in the product that are, in fact, a WTX, really need to be removed from the product because they tend to fail."
"Scripting needs improvement. It's hard for our customers."
"Making it more user-friendly would be an improvement."
"Some pre-packaged connectors for integration with various applications, such as SaaS offerings, would be a useful addition."
"In the next release, I would like to see the product price reduced. It should be cheaper."
"The two biggest issues of this solution are the complexity and the maintenance procedures."
"The product should be more adapted to the DevOps process."
"The price should be reduced to make it more affordable."
"Technical support is an area where they can improve."
"I would like to have a dashboard where I can see all of the communication between components and the configuration."
"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 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."
"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."
"It would be nice if they had a change management system offering. We built our own deployer application because the one built into webMethods couldn't enforce change management rules. Integration into a change management system, along with the version control system, would be a good offering; it's something that they're lacking."
"I'd like to see the admin portal for managing the integration server go up a level, to have more capabilities and to be given a more modern web interface."
"The cost of this product varies from customer to customer and the relationship with IBM, including how many offerings from IBM are already being used."
"It's expensive when you compare it with others."
"The licensing cost is very expensive."
"As far as I know, they have a perpetual license for this product. They are paying perpetual fees rather than an annual subscription or annual pricing."
"The pricing and licensing costs for webMethods are very high, which is the only reason that we might switch to another product."
"The vendor is flexible with respect to pricing."
"This is an expensive product and we may replace it with something more reasonably priced."
"It's a good deal for the money that we pay."
"Currently, the licensing solution for this product is pretty straightforward. The way that Software AG has moved in their licensing agreements is very understandable. It is very easy for you to see where things land. Like most vendors today, they are transaction based. Therefore, just having a good understanding of how many transactions that you are doing a year would be very wise. Luckily, there are opportunities to work with the vendor to get a good understanding of how many transactions you have and what is the right limit for you to fall under."
"Pricing is the number-one downfall. It's too expensive. They could make more money by dropping the price in half and getting more customers. It's the best product there is, but it's too expensive."
"I do think webMethods is coming under increasing pressure when it comes to their price-to-feature value proposition. It's probably the single biggest strategic risk they have. They're very expensive in their industry. They've been raising the price recently, especially when compared with their competitors."
IBM DataPower Gateway is a single multi-channel gateway that helps provide security, control, integration and optimized access to a full range of mobile, web, application programming interface (API), service-oriented architecture (SOA), B2B and cloud workloads. It enables you to rapidly expand the scope of valuable IT assets to new channels - giving customers, employees and partners access to critical resources. It is available in the following form factors: physical, virtual, cloud, Linux and Docker.
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.
IBM DataPower Gateway is ranked 4th in Enterprise Service Bus (ESB) with 9 reviews while webMethods Integration Server is ranked 2nd in Enterprise Service Bus (ESB) with 9 reviews. IBM DataPower Gateway is rated 8.2, while webMethods Integration Server is rated 7.8. The top reviewer of IBM DataPower Gateway writes "Deals with multiple protocols, but "WTX" components are problematic". On the other hand, the top reviewer of webMethods Integration Server writes "Its single hybrid-integration platform makes it easy to troubleshoot and quickly resolve issues. Upgrades are complex". IBM DataPower Gateway is most compared with IBM API Connect, Apigee, IBM Integration Bus, Mule ESB and 3scale API Management, whereas webMethods Integration Server is most compared with Mule ESB, IBM Integration Bus, SAP Process Orchestration and Mule Anypoint Platform. See our IBM DataPower Gateway 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.