We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
"It is user friendly, it's not complex."
"The most valuable features are the stability and the time to market."
"The most valuable part of the solution is the ease-of-use and ease of deployment."
"The most important thing is that it is easy for developers to work with."
"It is very stable. It is a market leader, and it has connectors to many of the legacy systems. It also has enterprise cloud connectors."
"The high availability, tolerance, and load balancing features are top-notch. Its scalability features are also pretty cool."
"Good performance and reliability."
"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."
"They don't support out of the box - you have to buy adapters or you have to have the technology."
"There are not many plugins available to integrate the databases. We have to write it in Java and integrate it. The developers should have more knowledge. These are the three main aspects that they could improve."
"The container-based image is too large and this makes auto-scaling difficult."
"The cost of this product is too expensive for smaller companies or those with a small number of integrations."
"Its price can be improved. For medium enterprises, it is a very expensive tool. In the market, you won't get many resources for this solution. You won't find many developers in the market very easily. The latest version of TIBCO (6.4 or 6.x) is not very stable. It has got many issues. We have raised this with TIBCO, and they are taking a lot of time to come up with a fix, which is making us move away from this product. Some of the performance-tuning aspects are also missing in version 6. They should provide performance-related fixes, which will be helpful for the customers. If you are migrating from the current version to the container-supported version, it is quite expensive. The product has evolved, but it is very pricey. That's one of the challenges. They have provided all the features that are there in other products, but this is a platform upgrade. The platform has completely been changed from 5.x to 6.x, and we can't use the same environment. We can't run both versions on the same server as VM. The development environment is entirely different. In version 5.x, there was a proprietary designer. Now, it has common plug-ins developed on top of Eclipse."
"The Business Studio tool can be improved, which is the tool for designing the processes. Improving the Business Studio tool will make this solution more stable. It has a steep learning curve, and it is pretty tough to learn."
"Could be more user friendly in the development area."
"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."
"My understanding is that the licensing is very costly."
"It is a bit expensive for medium-sized companies. If you are migrating from the current version to the container-supported version, it is quite expensive. The existing licensing will not work because the product platform itself is different."
"Its price policy has changed quite a lot in the last two years. It was extremely expensive previously. Nowadays, you can buy a license for BusinessWorks for €2000. Looking at what you get in return in terms of support, TIBCO community, and stability, it is fairly reasonable. It is not too expensive."
"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."
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.
TIBCO BusinessWorks is ranked 11th in Data Integration Tools with 7 reviews while webMethods Integration Server is ranked 1st in Enterprise Service Bus (ESB) with 11 reviews. TIBCO BusinessWorks is rated 8.4, while webMethods Integration Server is rated 8.0. The top reviewer of TIBCO BusinessWorks writes "Stable and has connectors to many of the legacy systems, but needs better pricing and fixes for stability issues in the latest version". 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". TIBCO BusinessWorks is most compared with Mule Anypoint Platform, Spring Cloud Data Flow, Talend Open Studio, Informatica PowerCenter and Denodo, whereas webMethods Integration Server is most compared with Mule ESB, IBM Integration Bus, SAP Process Orchestration, Mule Anypoint Platform and Talend Open Studio.
See our list of best Cloud Data Integration vendors.
We monitor all Cloud Data Integration 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.