We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
"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."
"We find it effortless to set up. We really don't have to do anything other than finding the application in the Zapier catalog. And as long as the application has been re-integrated into Zapier, they're able to then just provide the connection details and hook it up."
"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."
"System-to-system is fine, but when it comes to system-to-user, where Zapier is helping to communicate to a user, that's a one-way communication. If that user has to perform some action on that notification, the action isn't handled by Zapier. So there's no way to orchestrate that and it's very cumbersome."
"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."
"The price is a little bit high, especially regarding their support."
"It's very straightforward licensing. There's only one cost you have to pay, and if you want a relevant pricing plan, I think you have two or three different models or packages which include the number of notifications or Zaps, as they call it, that you can program."
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.
Zapier is a tool for primarily non-technical users to connect together web apps.
An integration between two apps is called a Zap. A Zap is made up of a Trigger and one or more Actions or Searches.
Whenever the trigger happens in one app, Zapier will automatically perform the actions or searches in another app in order.
Zaps are very lightweight and easy to set up. Zaps do not import or export old data (they only operate on new items created after the Zap is enabled). Zaps are also not kept in sync ("two way syncing") after the Zap is triggered.
Zaps are deceivingly simple if you're used to dealing with complex and difficult integrations. Their simplicity is what enables anyone to create them.
webMethods Integration Server is ranked 2nd in Enterprise Service Bus (ESB) with 11 reviews while Zapier is ranked 11th in Cloud Data Integration with 1 review. webMethods Integration Server is rated 8.0, while Zapier is rated 8.0. 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". On the other hand, the top reviewer of Zapier writes "Streamlines our system-to-system task automation at the scale we need". webMethods Integration Server is most compared with Mule ESB, IBM Integration Bus, SAP Process Orchestration, Mule Anypoint Platform and Oracle Service Bus, whereas Zapier is most compared with Workato, AWS AppSync, Coupler.io and Mule Anypoint Platform.
See our list of best Data Integration Tools vendors.
We monitor all Data Integration Tools 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.