webMethods Integration Server Overview

webMethods Integration Server is the #2 ranked solution in our list of top Enterprise Service Bus (ESB) tools. It is most often compared to Mule ESB: webMethods Integration Server vs Mule ESB

What is webMethods Integration Server?

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.

webMethods Integration Server Buyer's Guide

Download the webMethods Integration Server Buyer's Guide including reviews and more. Updated: July 2021

webMethods Integration Server Customers

Fujitsu, Coca Cola, ING, Credit Suisse, Electrolux, GTA, CosmosDirekt

webMethods Integration Server Video

Pricing Advice

What users are saying about webMethods Integration Server pricing:
  • "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."
  • "It's a good deal for the money that we pay."
  • "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."
  • "This is an expensive product and we may replace it with something more reasonably priced."
  • "The vendor is flexible with respect to pricing."

Filter Reviews

Filter by:
Filter Reviews
Industry
Loading...
Filter Unavailable
Company Size
Loading...
Filter Unavailable
Job Level
Loading...
Filter Unavailable
Rating
Loading...
Filter Unavailable
Considered
Loading...
Filter Unavailable
Order by:
Loading...
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Search:
Showingreviews based on the current filters. Reset all filters
ZD
IT Manager at a manufacturing company with 5,001-10,000 employees
Real User
Top 5
Its single hybrid-integration platform makes it easy to troubleshoot and quickly resolve issues. Upgrades are complex.

What is our primary use case?

By Software AG, we are also using Integration Server, Trading Networks, Active Transfer, Optimize for Infrastructure, My webMethods, and their EDI package. As long as there is product parity between products, it makes sense to continue using multiple products from the same vendor. Obviously, you want to make sure you have a diverse portfolio. Where those products start breaking those links, you want to make sure that you are using the best product for your company in this region. The fact that we were already using another solution from this vendor affected our decision to go with this… more »

Pros and Cons

  • "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."
  • "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."

What other advice do I have?

The solution pays for itself, but it is complicated as it stands today. Make sure that you are using it for exactly what you have architected it for. Don't try to fit a square peg into a round hole. We have been moving away from data integration for webMethods Integration Server. So, it's becoming less of a priority for us. Software AG has been moving in the direction of trying to make their tool as modern as possible. It has plugins for Docker today as well as ways to integrate into webMethods Integration Cloud. While these integrations are available, we don't use them. I would rate…
Rully Feranata
Enterprise Architect at PT Bank Mandiri (Persero) Tbk.
Real User
Top 5Leaderboard
Dramatically decreases our development time for new products, business processes, and integrations with partners

What is our primary use case?

Our use case is our service-oriented architecture transformation which started in 2017. It has been a three-year journey. Before that, between 2007 and 2017, we had not conducted a re-architecting of the SOA. In 2017, we had a big initiative for digital transformation at the bank to make ourselves more flexible, more agile, and competitive with all the startups and the financial industry in general, not only in Indonesia but also in other regions. One of the critical capabilities included the integration area. That is why, in 2017, we re-architected the SOA to have layered architecture that is… more »

Pros and Cons

  • "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."
  • "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."

What other advice do I have?

We have been using the solution's adapters and connectors for our new architecture on the integration inside of Integration Server, but with help. The product is a plain vanilla platform. You can do pretty much everything, but to exploit its capabilities, you need to use their consulting to help develop and utilize them. Those capabilities are something that our internal developer was not familiar with, so we needed to engage with the Software AG engineers to help us build those adapters. The built-in adapters do not suffice because they need customization to be implemented. Each organization…
Learn what your peers think about webMethods Integration Server. Get advice and tips from experienced pros sharing their opinions. Updated: July 2021.
523,431 professionals have used our research since 2012.
Scott Jaynes
Systems Architect at a manufacturing company with 10,001+ employees
Real User
Top 10
Helps us design process models that can orchestrate a process from beginning to end, and implement complicated tasks quickly

What is our primary use case?

We use it for everything. Three years or four years ago our company was bought. In our original company we used it for EDI, although that has pretty much gone away since the purchase. We do use it for EDI, but we use it for more free EAI, enterprise application integration. It allows us to have plant software talk to SAP. It allows us to interface with external parties through their MFT (managed file transfer) product called Active Transfer. We use it to connect all kinds of systems. Also, in a company that's big, there are always acquisitions, and before the acquisition can be fully… more »

Pros and Cons

  • "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."
  • "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."

What other advice do I have?

The biggest lesson I've learned from using it is to never build a one-off. Always think "reusability." Everything in webMethods is reusable. Even if you think you will never use it again, and you build it hastily, without error-handling, you will get burned. Always build for reusability. You should definitely build a couple of little reusable frameworks too. The first reusable framework I would build would be an error-handling framework. Once you build that, you add those service calls to every service you ever build. In that way, once things error, you always know. It knows how to send an…
A. Smart
Enterprise Architect at a energy/utilities company with 1,001-5,000 employees
Real User
Top 5
Enables a host of payment options for our customers and has automated a lot of our manual processes

What is our primary use case?

It interfaces between applications, as well as between the cloud and our existing on-prem applications. We primarily utilize packaged applications; we don't really have a lot of custom applications. We do have a few custom interfaces, and some vendors may have created a custom interface on their own, but we present a standard integration, a standard enterprise service bus, to connect to.

Pros and Cons

  • "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."
  • "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."

What other advice do I have?

Start with proofs of concept. Create a few good proofs of concept and get it up and running and you'll be able to escalate things. Make them achievable. The biggest lesson I have learned from using the solution is that I should have envisioned it a little bit bigger. We had a lot of point-to-point solutions that we could have considered and I think we still have a lot more to go. Also, if the back-end is not available, we should build in some logic that says, "Okay, now that I'm not getting a valid response or any response, I should be able to quickly use a default or turn off some features."…
BC
Enterprise Architect at a computer software company with 1,001-5,000 employees
Real User
Top 5
Enables us to react very quickly to changing business demands, but pricing compared to competitors is an issue

What is our primary use case?

We're a healthcare technology organization and that space has a great deal of integration work, so we use webMethods to help us manage and develop integration solutions for various healthcare-related needs. Those include HL7 messages, the new interop messages, the new CMS directives for data blocking, Affordable Care Act integrations, and integrations with other health systems. Our particular product is a SaaS, multi-tenant environment that's on-prem but moving to cloud. It is used by hundreds of healthcare providers to run their businesses.

Pros and Cons

  • "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."
  • "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."

What other advice do I have?

It's a very valuable and a very powerful tool, but it's a tool that you have to dedicate resources to, to learn and to use well. Use an integration partner to help get it stood up and in use in your organization faster. That is something that is very valuable. And then dedicate staff to learn it. This isn't one more tool in the toolbox. This has to become someone's toolbox. The comprehensiveness and depth of its connectors to packaged apps and custom apps is fairly low, but its ability to build what you need is very high. The value of the tool is the Lego block nature of it, so instead of…
Dries Vanmarcke
Technical Architect at Colruyt
Real User
Top 5Leaderboard
Our transformations can be quickly implemented without a lot of fuss

What is our primary use case?

Our primary use case for webMethods Integration Server is for our internal application integration. We use it to expose REST and SOAP web services and to connect it with SAP. We also use it as a bridge to transform web service calls. We'll use an ESB if we want to transform the protocol or the message. It's also used to connect our internal custom-written Java applications with products like SAP, which don't have an open standards interface. We only use it on-premise. We are considering going to a hybrid setup but at the moment, we don't have it yet. Nevertheless, we still use the Integration… more »

Pros and Cons

  • "It's a visual tool, so our transformations can be quickly implemented without a lot of fuss. The fact that we have an easy way to expose REST services is also very interesting. It offers the possibility to connect over GMS to synchronize message brokers."
  • "In terms of improvement, it would be better if it adapted quicker to open standards. It took a while for API specification before the last version was available. The spec of version two was rather quick."

What other advice do I have?

It's wise to work with a consultant when you introduce Integration Server because you need to learn about the product. It's better to have advice from someone who already has experience with it. I would rate webMethods Integration Server an eight out of ten. I'm quite happy and satisfied with it but nothing is perfect.
Ameer Alhadidi
Senior Integration Developer at ROP
Real User
Top 20
User-friendly and it makes developing services quick and easy

What is our primary use case?

We are looking to use webMethods as part of our business process management solution. We have a mainframe and it facilitates connectivity with our database.

Pros and Cons

  • "The tool is very powerful and user-friendly."
  • "I would like to have a dashboard where I can see all of the communication between components and the configuration."

What other advice do I have?

My advice to anybody who is considering this product is that it is a very powerful tool that will empower the development of services. If there is a proper plan then it can be achieved within a short period of time. After a service has been developed and tested, it is moved to the staging environment. Once it is tested, we move it to production. Moving it will not take more than a few minutes. It is definitely a product I recommend to people who have the money to pay for it. I would rate this solution an eight out of ten.
RS
Regional Integrated Platforms Tech Lead at a insurance company with 10,001+ employees
Real User
Stable, straightforward to set up, and flexible in terms of pricing

What is our primary use case?

This product is used for application integration. I have implemented this solution for many clients across the world.

Pros and Cons

  • "The most valuable feature is stability."
  • "Technical support is an area where they can improve."

What other advice do I have?

I have found that the home-grown products from this vendor always do pretty well, but when they acquire new products from third-parties, there has been some disappointment. Overall, this is a pretty good product. In fact, my only real complaint is about support. I would rate this solution an eight out of ten.
See 1 more webMethods Integration Server Reviews
Buyer's Guide
Download our free webMethods Integration Server Report and get advice and tips from experienced pros sharing their opinions.