IT Central Station is now PeerSpot: Here's why

webMethods Integration Server OverviewUNIXBusinessApplication

webMethods Integration Server is #1 ranked solution in top Enterprise Service Bus (ESB) tools. PeerSpot users give webMethods Integration Server an average rating of 8 out of 10. webMethods Integration Server is most commonly compared to Mule ESB: webMethods Integration Server vs Mule ESB. webMethods Integration Server is popular among the large enterprise segment, accounting for 73% of users researching this solution on PeerSpot. The top industry researching this solution are professionals from a computer software company, accounting for 31% of all views.
webMethods Integration Server Buyer's Guide

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

What is webMethods Integration Server?

webMethods Integration Server is widely considered to be the best integration server available in the marketplace today. The solution can help users integrate everything and anything.

webMethods Integration Server allows organizations to display and integrate existing and new business activities. The solution offers components that help users create, test, and install new services. webMethods Integration Server can automate, organize, and construct various gathered services and traditional legacy systems into productive value-added processes. webMethods Integration Server works as a secure platform for distributing and running services. The solution obtains and translates user requests, recognizes and records the requested service, translates and moves the data in the necessary format, receives the information back, and returns the information to the user in the appropriate original format. webMethods is the primary solution used by enterprise organizations for integrating functional coordination with application servers, custom applications, and databases. webMethods makes it easy for enterprise organizations to share electronic documents seamlessly.

Users have several options to audit webMethods Integration Server processes using some of the component metrics below:

  • Adapters: Using the SOA extension for webMethods, users can easily monitor the performance of every adapter users have deployed. Available metrics include Adapter Services, Adapter Connection Pools, and Adapter Notifications nodes.

  • Business Processes: A business process is a process that uses a specific set of rules to perform tasks in a prescribed order. Many business processes depend on the successful integration of numerous systems, involving many people in varying roles. With the SOA extension for webMethods, users can easily monitor that workflow, ensuring that processes are being performed as defined.

  • Java Services: This includes services created in Java or in languages coordinated with Java.

  • WebServices: This includes services regarding webserver endpoints and performance.

  • XSLT Services: This service will allow users to transform XML data into other formats and includes the transformation to other services.

  • Thread Pools: This metric uses threads to conduct services, gather documents from the webMethods Broker, and initiate triggers. Documents can be published locally on the server or to the broker that will send the document out. A JMS trigger receives inbound messages and then processes those messages accordingly.

Reviews from Real Users:

“There are a few things about this product that we definitely like. It is very robust. If you build it nicely, you can't go wrong with it. It's rock solid. The development is very fast. If you know what you're doing, you can develop something very easy and very fast.” - Rohit S., Integration Lead at a wellness & fitness company

“One of the most important features is that it gives you the possibility to do low-level integration. We can meet any requirements through customizations, transformations, or the logic that needs to be put in. When clients come to me with any problem, in about 99% of cases, I say, "Yes, it is feasible to do through webMethods." It has reached such a level of flexibility and maturity. Most of the things are available out of the box, and even if something is not available out of the box, we can customize it and deliver it for a client's requirements.” - Sushant D., IT specialist at Accenture

webMethods Integration Server Customers

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

webMethods Integration Server Video

webMethods Integration Server 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."
  • "With our current licensing, it's very easy for us to scale. With our older licensing model, it was very hard. This is definitely something that I would highlight."
  • "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."
  • webMethods Integration Server 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
    IT Manager at a manufacturing company with 5,001-10,000 employees
    Real User
    Top 10
    Its single hybrid-integration platform makes it easy to troubleshoot and quickly resolve issues. Upgrades are complex.
    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 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 particular product, mainly from a cost standpoint. As is any product in this region, the biggest cost is almost always the upfront cost of laying out the solution. Also, there are some costs in having that solution already available: between knowledge of the platform, having the licensing rights, and if you bring in a new solution, then you are now paying for two solutions. The native integrations between the vendors' products are very seamless. The products interact very well. At times, it's kind of hard to tell where one product ends and the next one starts. As new products come in, the integrations probably take one or two updates before they are fully integrated. However, once products are fully integrated, it is very seamless and easy to hop between one product to another. Using multiple products from the same vendor creates efficiencies: In terms of knowledge. Obviously, there is a familiarity with the product and how you expect Software AG's products to act and respond.  In terms of operational understanding between end users who are looking for specific data. They know how these products work and how to pull up these reports.  In terms of having administrators overseeing these products. There is a cost savings for using many of the same products. There are lower training costs. Also, typically, there are a lot of integrations that you ended up needing to build out, whether they be custom or out-of-the-box. Even if they are out-of-the-box, a lot of times that takes a lot of work to get those to work. However, since we are using Software AG products, it's very much like installing a plugin into an Excel program. There was a reduction in the learning curve because we had already used the vendors' products. The products used work very similarly. In terms of verbiage, key aspects, or three-letter acronyms, you don't have to relearn any of those. There is an expectation of how these products will work. These products always work the same way when Software AG is rolling these types of products out. We use webMethods Integration Server for two main aspects:  For application-to-application integrations. B2B: The transferring of on-premise data out to other business partners.

    How has it helped my organization?

    As with any integration platform, it is a single pane of glass that allows you to see and interact with transactions as they are flowing. Out-of-the-box, Software AG offers robust monitoring solutions to help you understand if a solution's up or down transactions aren't working, etc. The tool has been invaluable to our organization in terms of understanding where our data is, how it's flowing, and its current status. Having a single hybrid-integration platform for all our needs is very important. From an IT perspective, it is a way for us to easily troubleshoot and quickly resolve issues. From a business perspective, it's very important because IT is readily available to assist with any system issues which are happening at that time. Anytime that you have applications talking to each other, it is a breeding ground for problems and issues. Having a solution like webMethods Integration Server in place can empower your IT department to be able to resolve issues and roll out solutions quickly as new applications come into your portfolio. We have been on webMethods Integration Server for 15 years. We just got rid of our mainframe. It works wonders with our mainframe. With SaaS and cloud applications, webMethods Integration Server does not answer this need by itself. This is where you would be looking for APIs or custom plugins to work with those types of solutions. 

    What is most valuable?

    It is very open. It is extremely rare for us to find something that we are trying to integrate, but we can't integrate it. In the past seven years, I don't think that has ever happened. For any problem that we are looking at, the Software AG solution can solve. That has probably been the most valuable feature. 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.

    What needs improvement?

    Integration platform as a service (iPaaS) is probably the future and direction that many companies and organizations are looking at. Software AG is also rolling out robust solutions for this. So, if I was a brand new customer, that is where I would be looking. This is also the direction that I think Software AG is moving into along with almost every vendor in the industry. However, the integration platform, as it currently sits, runs really well. It's very robust and does what you would expect it to do.
    Buyer's Guide
    webMethods Integration Server
    June 2022
    Learn what your peers think about webMethods Integration Server. Get advice and tips from experienced pros sharing their opinions. Updated: June 2022.
    610,190 professionals have used our research since 2012.

    For how long have I used the solution?

    My organization moved onto the webMethods platform 15 years ago. I have been using it for the past seven years.

    What do I think about the stability of the solution?

    Software AG is a partner who has been around for many years. The company is not going anywhere. Regarding the solution, you can get the capabilities that you need out of it.  It is a known solution that works really well and does exactly what you would expect it to do. Software AG's full support for the solution’s adapters and connectors brings long-term stability to our services and integrations. Software AG has many SMEs in each region, both globally and in each product type. Being able to have access to a subject-matter expert in the specific tool or region that I'm looking for is invaluable. I feel like I am talking to someone who has hands-on experience in either developing the solution or has many years of experience with the product or similar customers. They also have people who just work in specific business groups. For example, if I'm looking for a knowledge worker to do something with IoT, then they have people ready who can answer specific questions about products that we might be looking to integrate with.

    What do I think about the scalability of the solution?

    The solution is very scalable. If you want more webMethod Integration Servers, it is very easy to spin them up. It's very easy to apply packages to each one of those solutions. Or, if you want to just have one large webMethods Integration Server, it is easy to create the configuration settings to allow that JVM to have more memory. There are less than 20 users. A solution like this is normally a back-end solution. Obviously, we have administrators who are overseeing the product to make sure it's up, patched, available, and secure. Developers who are rolling out new solutions and debugging any issues going on in production or lower environments. Then, the third group is probably the business users. That is a very small hand full of users at our company. Those users are typically looking just to make sure that the data is flowing as they would expect. For example, I expect a certain file to go out to this customer every day. That business user has access to log into the application and pull that file. The product is used extensively at my organization. Out of all our integrations, it probably counts for 60 to 70 percent. Every minute of every day, it's being used. I think the usage that we have in place today is correct. If we were to expand any further, we would probably be looking at iPaaS solutions.

    How are customer service and support?

    Their technical support is very good. I have never had any issues with the support or getting the resources that I need. Two months ago, Software AG did have a data breach, so their support desk got shut down. It has been down since then, and that has not been a pleasant experience. Prior to that, it was a pleasant experience. I think Software AG has been reeling from that, but there are ways to get a hold of their support desk. This ensures that their customers still have access to support, which has been available and out there. However, they did have a public exposure, which has ended up causing some loopholes for their customers.

    How was the initial setup?

    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. This is where we would need to look at an iPaaS solution or moving to work with microservices solutions. Obviously, the smaller you make the solution, the more you're able to in an agile fashion. From a high-level implementation strategy, we do a waterfall approach. That is the approach that we have ended up following for upgrading this solution. Deploying solutions is very easy. The biggest thing that any company has to look at, because we have had a couple of pitfalls in this, is you have to look at how you're rolling your solution out. So, if you end up stacking or creating common services in the solution, those solutions become very tricky as they start to age, as any development cycle would end up having. The smaller you create the solution, the easier it is to keep rolling out those solutions, and staying away from common services really allows you to continue to roll out with ease. As new solutions roll out or there is a different way for these apps to integrate, it has been fairly easy for developers to make the modified changes needed. The biggest thing is always knowledge because there have been some integrations that haven't been touched for 15 years. Then, if someone needs to touch one of those integrations, there is a learning curve in understanding how that integration works and what they are looking at.

    What was our ROI?

    Having a product like this is invaluable to any company in terms of the amount of time that IT gets to save in terms of integrating different products as well as having an open way to ensure that these applications are working. If you were to do this out of the box for each one of those solutions, while the upfront costs would be cheaper, the long-term stability of your applications would definitely degrade. As you are rolling this out for products that probably run your business, that's probably not a direction that any long-term company would want to go. I know my organization has seen time savings from not going with in-house built integrations from app to app. For the B2B, we are probably saving somewhere between five to 10 full-time resources who would be working on this manually. For application-to-application, it probably has cut down 50 percent of our downtimes at a minimum. When you're talking about application-to-application integration, that is the thing that you would probably end up using as a key metric. For the amount of downtime that we have, I would double the amount or length of downtime that we would have if we didn't have this solution.

    What's my experience with pricing, setup cost, and licensing?

    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. With any solution like this, on day one you have a project that you're trying to work on, but just understand where you are trying to go with the solution. Some plugins are cheaper than others, and others are more expensive than others. Just make sure that you understand the full scope of what you might end up using the product for, so you can understand the all-in costs. The tool works extremely well. Software AG offers packaged solutions for many packaged apps. Oracle SQL Server or Salesforce are add-ons that you can purchase and install easily for plug and play with packaged solutions. When you start moving into custom applications, there are no packaged solutions. The good news is that typically custom apps are built in some type of known technology, and that technology can easily be integrated into webMethods Integration Servers. Business-to-business communications is an add-on that needs to be purchased. While super important to my organization, it is an add-on outside of the standard webMethods Integration Server. I would strongly recommend the business-to-business add-ons, especially if you're looking to use webMethods Integration Server in that capacity. It just makes the development cycles a lot shorter as well as making it much easier to manage your business profiles.

    Which other solutions did I evaluate?

    We routinely evaluate other options. I wasn't here when we made the decision to move onto this solution, but we periodically reassessed the platform to see if we are still sitting on the best solution that is matched to our corporation. Today, there are many newer solutions out in the marketplace, and Software AG does offer those solutions. That is a great start. If I was starting over, I might look at those alternative solutions. However, if you are an alternative solution to webMethods Integration Server (not Software AG), then I would probably be looking a lot more into the cloud. webMethods Integration Server is used in a very legacy way. For example, we are on premise with data centers, which are legacy ways to solve a problem. If my solutions were in the cloud, then I would probably be looking at webMethods Integration Cloud as Software AG offers it, or any of the other vendors, like MuleSoft. So, you have to look at: What am I trying to integrate today?  Where are those solutions sitting?  If everything is on-prem and you are a 110-year-old company with 50 plants across the place, then probably having an on-prem is the right solution. If you are an eCommerce shop, then you are probably looking more in the cloud and for a cloud solution.

    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 webMethods Integration Server as a seven (out of 10). For what the solution can do, it does it extremely well. The upgrades are very cumbersome; they are very long and disruptive. You have to do them at least every three years. It's not a fun time for any company. If upgrades were a 100 times easier, it would get a much higher score.

    Which deployment model are you using for this solution?

    On-premises
    Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
    Rully Feranata - PeerSpot reviewer
    Enterprise Architect at PT Bank Mandiri (Persero) Tbk.
    Real User
    Top 5
    Dramatically decreases our development time for new products, business processes, and integrations with partners
    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 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 related closely to microservices. We are testing a new mobile banking channel to use a micro services architecture as well.

    The integration use cases for webMethods involve connecting all of the back-end core systems at the bank so that they use the SOA integration server layer. Everything must go through this layer to speak or communicate with the back-end systems, such as the core banking, HR systems, and the treasury system; all the core systems that sit behind the ESB layer of the Integration Server. All the front-end systems like mobile banking, sales management, the CRM, etc., must go through this ESB layer, the integration server, to communicate with the back-end system. That is the prime use case of Integration Server.

    Other than that, we successfully launched a new initiative for API about a year ago. We are commoditizing our financial services to not only be consumed by our channels, but by partners such as startups, FinTechs, InsureTechs, and other companies that would like to partner with us and use our financial services APIs.

    When it comes to commoditizing for external parties, the partners, the other banks, or financial institutions that are our subsidiaries, they can connect to it and consume our services through the API Gateway products that we are providing to them. That includes sandboxing to test their applications. If they would like to partner with us, they need to register themselves and make an agreement with the bank regarding what sort of packages and fees that will be applied for the cooperation.

    It's deployed on-prem. We are a banking institution. In Asia, regulators for the financial industry prohibit us from hosting financial transactions outside the Indonesian region.

    Are you using multiple products from this vendor?

    We are using multiple products to build the end state of our service-oriented architecture (SOA). This is all orchestrated as a big building house. Those SOAs have many capabilities inside of them on the integration side, such as webMethods Integration Server. There is also webMethods API Gateway and Software AG Apama. (Read my webMethods API Gateway review here.) Those modules inside of Software AG complement the building blocks of SOA.

    We also use it to complement other products in the markets outside Software AG, such as Kafka as well as all event processing and streaming. This is in combination with the capabilities (and beyond) of what Software AG stacks can do.

    I find the native integrations between Software AG products to be very useful from a plain vanilla standpoint. Though, when we implement native integrations, there needs to be slight customizations to fit them into our core legacy system, and that needs to be integrated with other systems. For plain vanilla capabilities, it is sufficient enough.

    The native integrations between Software AG products also have good performance in terms of transactions per second (TPS). These are acceptable in terms of the volume and speediness of a transaction that we can produce as well as being combined with the efficiency of using the hardware, memory, and CPUs.

    If you combine the commodity hardware and performance as well as the plain vanilla capabilities of internal products that Software AG has, then there is a good price per value.

    It gives you a one-stop service for your integrations area. You can really rely on one vendor, then you don't have to worry about sustainability or support. This is all guaranteed by Software AG as a single stop service from them. Whereas, when you need to combine other vendors, then you need to monitor each of their solutions, sustainability, product roadmaps, etc. Then, this becomes your technology liabilities, which is something that we consider. From the integration, we are selecting a good strategic partnership with one vendor in order to maximize our productivity. Thus, we don't have to worry how we can monitor each respective vendor if we do a best of breed combination of many vendors, just to do an integration.

    By selecting Software AG and using multiple products, this saved us about 72 percent, which has definitely given us more agility.

    Because we were already accustomed with webMethods Integration Server way before the webMethods API Gateway, they were almost the same. We just converted our knowledge from the prior WSDL into RESTful JSON standard messages. Therefore, the learning curve was very smooth because the environment that the developers use was still the same: My webMethods Console. It uses the IDEs coming from that, saving us a lot of time with the learning curve on new technologies.

    How has it helped my organization?

    One of the improvements is that everything is currently standardized. Previously, each system had its own connection to the core and back-end systems, a point-to-point connection. It created havoc for governance of the integration itself. There were so many connections without any governance whatsoever as to how the communication happened.;

    There is also an improvement on our development side. When we have requests for new business requirements, products, business processes, and integrations with partners, Integration Server has dramatically decreased our development time. That's because we have standardized all the communications to the core system in one place.

    In addition, we have improved availability of the channel itself.

    It definitely gives us flexibility. The first stage, with these products, is the learning and customization. Once these are underway and things run, the performance is meeting our expectations. And when new requirements arise it becomes easier and development speeds up. For each integration service, the development cycle has come down from seven days to three days, maximum. And that's for the complex integrations. We have cut the development cycle by almost 50 percent.

    Modifying and redeploying integrations is very easy. It gives us a good, stable, comprehensive, end-to-end development cycle, from development to deployment. It gives us a set of tools for checking the consistency and integrity of the code, which is something we didn't have with previous solutions. When deploying to the production server, it also does validation checking, whether certain libraries are missing, for example. It helps us do consistency checks. Because of that, we have cut down the system integration testing significantly. The user acceptance testing has also been reduced significantly. The reduction in testing time is almost 50 percent, compared to our previous solution. We used to test for five days and now it's just two days of testing for each of the services.

    The vendor’s full support for the solution’s adapters and connectors has helped with uptime and availability. We are close to 24/7. And the number of transactions per second, previously, was around 600 to 700. Now, it has almost doubled. We are reaching more than 1,000 TPS. We have more than 2 million transactions. It has given us that type of scalability.

    The solution has helped us contribute more to the business, to the expansion of the products and the volume of transactions.

    What is most valuable?

    There are three features of Integration Server that are the most valuable. One 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 second feature is the reliability. Mandiri Bank is the largest bank in Indonesia. That translates it into a humongous volume of transactions that flow down from the channels and go through the Integration Server, and then to the core banking itself. The components of Integration Server need to have 99.999 availability. It needs to be reliable all the time, available, and to be a scalable platform.

    The third of the highlights of the features of Integration Server is the small footprint for infrastructure. It can run on any commodity hardware, unlike other solutions that need to run on specific hardware. It gives us the freedom to scale the platforms and create the greatest possible agility for the organization to expand, based on the demands. The other side effect of that is the additional advantage of transforming the architecture that we currently use into more of a microservices base. It gives us more flexibility and agility, going forward.

    What needs improvement?

    We would like to achieve a multi-site, soft data center. Multi-site meaning that we would like to have more than two Active-Active data centers because Indonesia is a big region with three time zones. We would like to have many data centers serve us across the islands to support the massive number of transactions. We need to have a good amount of availability. Hence, we would like to have a multi-site data center. To support that, the solution needs to be capable of Active-Active implementations, an Active-Active integration server. We would like to get to the point where transactions are not only coming into one data center but, simultaneously, could be redirected to several other data center sites. Integration Server needs the capabilities to help us to achieve that goal.

    Also, 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. They need to improve it to be scalable enough and lightweight enough to run on the microservices/containerized platform.

    We are paying them a lot so we have access to their product development engineers. We are waiting for them to revamp the microservices areas. We are waiting for the new version of that. They have come back to us with something that is much more lightweight, but to us, it has still not reached the lightweight level that we want.

    For how long have I used the solution?

    We have several products from Software AG. The product is the SOA webMethods Enterprise Service Bus. We have been using that since 2007. The second, and one of the largest, is the API Gateway. Other products include Apama Complex Event Processing and Event Stream Processing engine. Those are the three main products we are currently using as part of the service oriented architecture building-blocks at Bank Mandiri.

    What do I think about the stability of the solution?

    Given that we have been using it all these years, you can imagine the stability of the system.

    We experienced major issues at the beginning of the implementation when the product was still kind of new. But over the years they improved a lot. 

    They keep producing new versions at a rate that we cannot keep up with. That is a problem for us because they have a very small set of supported versions. That is a downside of their products. Old versions are supported for a very limited time. They keep telling  us, "You need to upgrade." But we do an upgrade and they introduce a new version and the one we updated to is already obsolete. Their life cycle is very short.

    What do I think about the scalability of the solution?

    It can run on commodity hardware, so it is scalable using commodity hardware, like Intel processors of any brand, as long they run on the Linux operating system. They can do a clusterized environment and scale easily when transaction volume is bigger than we expect. It can actually scale on demand, and it's easy to set up by joining a new cluster into an existing cluster. It performs well in this case.

    We have 60,000 to 70,000 employees at the bank. About 10,000 people are using the services we create with the solution. They are mostly in the transaction back office and they monitor the day-to-day transactions from the channels. They monitor our mobile banking, trade, finance, and treasury transactions, as well as wealth management, corporate payments, and cash management. It's typically the wholesale, retail, and the micro-banking staff who heavily use this integration. For the back office, the upper-level user is a department head, while the junior level is staff that does the monitoring, day in and day out.

    How are customer service and technical support?

    When we have issues that we have not encountered, we have access to their support teams. They need to have support which is close to the Asian region. Because of the time zones there are limitations on how they respond to our support. 

    They do provide us with local partners that help us more quickly. There are several severity levels of support. For level-one they provide us with good partners in Indonesia.

    How was the initial setup?

    Since we do the transformations, we do the initial setup from the bare metal server up to the setting up of the Integration Server. We can pretty much do that ourselves, with their guides. The first time, we needed to be guided by their engineers. The setup is fairly easy, but for optimal speed and performance, we definitely reach out to their support to evaluate the configurations that we have deployed.

    When we installed the new version it took two or three days, depending on how many nodes we configured. Now, it takes a maximum of one day to establish a setup for normal configurations. For the complex ones, that have many nodes or Active-Active sites, it can take three or four days.

    We have one engineer for Software AG, another on the network team, and another on the server team.

    For the monitoring of day-to-day operations, we have support from our internal developers. We have deployed six or seven people because this is a huge implementation of Integration Server. They cover three shifts so that we have 24/7 monitoring, using the management console. We accompany that with third-party tools that help us to monitor the performance.

    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 has its own business processes and logic that differ from one to the next. It is good as a plain vanilla, but if you want to customize it further and exploit the capabilities, you need to have their engineers working closely with you to implement and utilize all of the capabilities. 

    Our back-end is a legacy system that uses a different language, so we needed to customize it. The solution helped reduce the amount of work because at least the features were already there, but it needed the customization of the engineers from Software AG in conjunction with our internal developers as the experts in our core system. Combine forces and you create your own adapters.

    Integration Server provides application integration, data integration, business-to-business communications, APIs, and microservices. Regarding the data adapters, we are not using their products for data integrations. The data integration space has come into the data warehouse area, and we are using other tools to do data integration. But for the transaction APIs, business processes, we are using built-in products from webMethods.

    That range of features comes back to the use cases that apply to the business innovations that a business would like to implement, such as real-time transactions, asynchronous transactions, fire-and-forget. I'm sure the transactions will be successfully processed by our core systems, and that is the main goal. The other features go towards how we can enrich things, but that is a second priority. 

    Which deployment model are you using for this solution?

    On-premises
    Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
    Buyer's Guide
    webMethods Integration Server
    June 2022
    Learn what your peers think about webMethods Integration Server. Get advice and tips from experienced pros sharing their opinions. Updated: June 2022.
    610,190 professionals have used our research since 2012.
    Scott Jaynes - PeerSpot reviewer
    Systems Architect at a manufacturing company with 10,001+ employees
    Real User
    Top 20
    Helps us design process models that can orchestrate a process from beginning to end, and implement complicated tasks quickly
    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 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 integrated there is always the challenge of getting data in and out of that acquisition. We use webMethods for that too, because we can either use internal network or external network.

    It's hosted in Azure, on VMs.

    How has it helped my organization?

    Its adapters and connectors absolutely provide the fastest way to build an integration. An example of the effect of that speed of integration on our business is that when our company was acquired, the acquiring company didn't have webMethods and wasn't interested in it. We were able to build interfaces quickly and show that they didn't need constant babysitting. For example, you can build frameworks. We had built an error-handling framework that can notify people with meaningful error messages when they happen. It never crashes. It always tells people what happened. We were able to build solutions much faster than with the other tools.

    Process orchestration is another benefit. Driving towards an event-driven architecture, and not a batch-oriented architecture—which introduces all kinds of time delays and doesn't give a true picture of the end-to-end process—we've used webMethods Designer to design process models that can orchestrate a process from beginning to end. For example, we can get data via SFTP, trigger an event in webMethods to process the data, and load it into a third-party data warehouse database such as Snowflake, which is a new up-and-comer. We can then trigger other processes to move that data and process it in Snowflake. We get responses back and, at the end, we can consume the processed data and send it to a different endpoint. All of that is orchestrated by webMethods. Process orchestration is a very strong point of the solution.

    Modifying and troubleshooting are very easy. They have a nice debugging app interface. It's faster than anything else that we've ever used. For example, when we were acquired, we had to keep our legacy SAP system, which was still functioning for the legacy company, synchronized with the acquiring company's SAP system. This was a very complicated task and we were able to do it very quickly using webMethods Integration Server.

    What is most valuable?

    We use Active Transfer quite a bit. It's very convenient because it is integrated with Integration Server. That means you can deploy an event-driven architecture, based on SFTP, which most people can't pull off. Most of the time, with SFTP, there is file polling and it's not an event-driven architecture. But webMethods' solution allows you to plug into their integration server and have a totally end-to-end event-driven architecture.

    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. That's particularly true of their cloud-based webMethods.io and their hybrid cloud solution. It's an on-prem plugin called CloudStreams. That allows you to connect your on-prem services with cloud-based things. The number-one example that everyone always gets is Salesforce.

    That depth of comprehensiveness is similarly true for the solution’s connectors to SaaS apps, IoT devices, and legacy applications. That is the number-one strong point of webMethods. It can connect to anything. There are so many out-of-the-box connectors for SaaS things. There are JDBC adapters, SAP adapters. They have pretty much unlimited connectivity, or you can build it through their toolkits.

    It provides a single hybrid-integration platform for all our needs.

    What needs improvement?

    Deploying is something we have found to be lacking with native webMethods tools, as is the ability to plug into a change management system, so we built our own deployment system. But again, we built it with webMethods' foundation tools and then interfaced with sub-version, version control, and our own home-built change management system. We used it to enforce that things can't go to prod unless they pass the QA stage and have had successful QA acceptance testing.

    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.

    For how long have I used the solution?

    I've been using webMethods Integration Server for 20 years.

    What do I think about the stability of the solution?

    Overall, it's very incredibly stable. I've never seen any other software platform that can run for so long without crashing. We've had servers run for over a year, and we have restarted them not because they were broken but because we were installing something. We've had servers run for over a year.

    In terms of support for the solution’s adapters and connectors and long-term stability for your services or integrations, you build once and forget it. 

    What do I think about the scalability of the solution?

    Scalability is another strong point. It's very scalable. It's very easy to stand up parallel machines, and add them to a cluster. We have two machine clusters because another strong point is that we've built everything in high-availability. We have two of everything; everything is clustered. But if we all of a sudden acquired 50 more companies, and had all kinds of additional business, we would just stand up a couple of more servers in the cluster, they would inherit the same exact code, and it would be simple very simple to scale.

    It's used for all our North America integrations. It runs the gamut of a little bit of EDI, a lot of EAI, and some MFT. Anything where one system needs to talk to another system, and trade data, we use WebMethods for that.

    We are always building new things in it. There are always new projects. 

    How are customer service and technical support?

    We don't need a lot of vendor support. You get the platform and you get some people that know how to use it and you really don't need much support from the vendor. However, when we do need support, they do have a good support portal and we do get support from their personnel pretty quickly. Our experience with their support has been good, for the most part. Once in a while we get people who aren't quite as good. I would rate it at eight out of 10.

    Which solution did I use previously and why did I switch?

    We did not have a previous solution.

    How was the initial setup?

    When it comes to upgrades, 20 years ago, it was very hard. Ten years ago, it was hard. Today, it's fairly straightforward. They've gotten much better at their upgrades.

    As for how long an upgrade takes, there are many factors involved. We had a struggle with our infrastructure team just getting us the vanilla boxes and Azure. Once you have your boxes in a network so that they can talk to each other, the installation of WebMethods is fairly simple. 

    Then there comes the complexity of importing your old code into it. And the hardest task of all is testing everything to make sure it still works. But the upgrades are pretty simple, they have apps that help out with that, and they work pretty well.

    The upgrade we're doing right now has four people involved. I am the architect, and the other roles are developer/testers.

    Day-to-day maintenance is almost zero. If there is a need for some maintenance, we have two people, me and another, who take care of system maintenance. But really, it's stand-it-up-and-forget-it. You do have to do certain things. webMethods is not in charge of your user databases. So if they fill up with data, and you haven't built in something to automatically purge them every so often, that's on you, not on webMethods. But as long as you have built in these types of maintenance routines, and schedule them, everything is pretty trouble-free.

    What was our ROI?

    I wish our company measured ROI. We're slowly getting there. 

    But webMethods Integration Server just saves time, especially development time. We can implement solutions that save repetitive user-time, often. Often, if a group comes to us and says, "Fred is spending two hours a day doing this stupid task where he's just uploading into a spreadsheet, and downloading here; can you help?" We can turn that type of thing around so fast, and eliminate Fred's two hours per day.

    What's my experience with pricing, setup cost, and licensing?

    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 could be 10 out of 10 if they dropped the price. There are so many people who don't use it because it's so expensive.

    Which other solutions did I evaluate?

    It also provides application integration, data integration, business-to-business communications, APIs, and microservices. That range of features is very important because we can do anything with it. We tried Informatica, for example, which was portrayed as being an equal, and it wasn't. It can't do everything and then you have to go out to other products and combine them. webMethods can truly do everything within the webMethods environment. And you don't have to buy add-on products. In reality, a lot of the webMethods' plugins are add-on products that were acquired at some point. But they do pretty well when it comes to integrating their acquisitions into the main ecosystem.

    The scope of abilities in Informatica is very limited. The scope of abilities for webMethods is pretty much unlimited.

    We have also looked at SnapLogic, and again, it just doesn't have the breadth of abilities that webMethods does.

    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 email to the right people, it knows how to send a meaningful error message that someone can read and see what happened. Building a meaningful error-handling framework upfront will save you so much time when things break and people ask "How do we fix it?" It will also proactively let people know things errored out, instead of reactively. We also built a deployment framework. That's a little above and beyond. The webMethods' tools are not terrible in that regard, it just doesn't talk to a change management system.

    Everything you build in webMethods is a microservice. It's been that way for 20 years. So even though the term wasn't coined back then, you can expose any service in webMethods to any other system you choose. Call it an API, call it a microservice, but it's all just built-in and it's already there.

    They are focusing on their cloud offerings, as is everybody else, because everyone wants to go that way. Sometimes it's just for the sake of saying, "I have a cloud offering," but theirs seems to be pretty solid. Their cloud offering is webMethods.io. However, I haven't used that extensively. That'll be coming up this year. There is also a hybrid thing called CloudStreams and that is for on-prem webMethods, which is what we have, but it has canned connectors to SaaS solutions like Salesforce, whereas webMethods.io is entirely in the cloud. You would use that to connect one SaaS to another SaaS.

    In terms of the solution's support for the latest standards making it possible to plug into modern tooling and third-party products, we've found no need. It's a pretty complete solution, unlike other solutions. And you really don't need to plug anything else into it.

    Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
    RohitSingh1 - PeerSpot reviewer
    Integration Lead at a wellness & fitness company with 5,001-10,000 employees
    Real User
    Top 20
    Robust, fast development process, easy to create connectors, and it supports managed file transfers
    Pros and Cons
    • "The development is very fast. If you know what you're doing, you can develop something very easily and very fast."
    • "The UI for the admin console is very old. It hasn't been updated for years and is pretty much the same one that we started with. This is something that could be refreshed and made more modern."

    What is our primary use case?

    We have a lot of use cases for this product. Initially, when we bought this product from Software AG, it was only for a specific project. But, we did watch for other opportunities where it could be used for integration and that's what happened.

    Our business model has many verticals, so it's used across the enterprise. The main function is to provide application integration within the company. We have more than 60 applications and at the moment, it's talking to more than 30 applications and integrating them. In this context, it is used by our sales team and in a lot of automations.

    Our second use case is to provide Write as a Service. We write any custom service using webMethods and then expose it to others as a REST service.

    Another thing that we use this solution for is managed file transfers.

    We have this solution deployed in a hybrid environment. It is available in our private cloud, where it is installed in AWS, and we also have it in our data center.

    How has it helped my organization?

    This solution has improved our productivity and efficiency in pretty much all of our applications. There are some currently-running automation projects where we are going to have to transform data and at the moment, it is being done manually. This is another case where we will implement webMethods to improve productivity.

    We automate our sales cycle using API orchestrations. When sales come through, for example, we register them and enroll them in the policy. All of this is done within webMethods and it works well.

    With respect to the comprehensiveness and depth of connectors that are available, they have a lot of traditional ones available. They are constantly adding new ones, which is good to see. However, what we found is that we can develop them very easily. Nowadays, pretty much everything is REST so it is easy to develop your own. We do not have a license for many of the connectors. One of them that we have is Salesforce, which was what we had originally envisioned.

    Then, what happened when we needed another connector is that we reasoned that rather than buying additional ones, we would instead create our own. Ultimately, we found that it was quite easy to do and in my experience, it is always better to use your own because the out-of-the-box connections have limitations. This is what we found with the connector for SuccessFactors; we were better off building our own because there are no constraints when we do it that way.

    This solution encompasses a range of features, which is important to us. We use it heavily for application integration and APIs, somewhat less for data integration, business to business communication, and we are trialing microservices. Although we do not yet heavily use the microservices feature, we do like that it provides it.

    We plan to expand our usage of microservices because, in the AWS world, we want to make things auto-scalable. This is what we are playing around with and although we do not yet have it in production, the plan is to use it more.

    Modifying and redeploying integrations is easy to do. This has made us more agile and the fact that we can churn things quicker has helped the business.

    What is most valuable?

    There are a few things about this product that we definitely like. It is very robust. If you build it nicely, you can't go wrong with it. It's rock solid.

    The development is very fast. If you know what you're doing, you can develop something very easily and very fast.

    What needs improvement?

    For the latest services, the product is lacking in terms of connectors. For example, there are a lot of SaaS providers and if you look for the connectors out-of-the-box, they are definitely not going to be there. They have a lot of traditional options but they are basic. If you have an advanced use case then you are better to build your own.

    For the most part, this solution supports the latest standards and makes it possible to plug in modern tooling and third-party products for automation and innovation. However, there are some things that it doesn't support and we find ourselves having to wait for a newer version. For example, when we were using version 9.10, it did not support OAuth.

    In general, I would like to see the vendor release newer features sooner. Or, it would be helpful if we can use a newer feature but don't have to upgrade the entire product.

    The UI for the admin console is very old. It hasn't been updated for years and is pretty much the same one that we started with. This is something that could be refreshed and made more modern.

    For how long have I used the solution?

    We have been using the webMethods Integration Server for almost six years.

    What do I think about the stability of the solution?

    I would rate the stability very high. Once it is running, it's very stable.

    The webMethods Integration Server is a tier-one application and if it's down, impacts pretty much everything. When it runs, no one knows about it but if it goes down, everyone screams. It is very crucial.

    What do I think about the scalability of the solution?

    With our current licensing, it's very easy for us to scale. With our older licensing model, it was very hard. This is definitely something that I would highlight. I'm very happy with our current setup because we can scale and it's more of a constraint of your commercials rather than a product constraint when it comes to scalability.

    How are customer service and support?

    We purchased a premium support package but to this point, we have not greatly depended upon it. In our day-to-day business, we haven't had to deal with them very often, which is a good thing. We generally resolve things within our team and don't generally need to rely on others. There are only a few issues that we have contacted technical support about, such as when we were having issues with the upgrade. Also, if there is something that we can't find then we will contact them.

    In general, when I compare their support with other vendors, I would not rate them high. The customer experience with support is an area that needs improvement. The reason I say this is that regardless of the issue you raise, even if it is not necessary, they ask a lot of questions.  

    Which solution did I use previously and why did I switch?

    Prior to webMethods, we were not using an integration solution. We were a .NET shop and we were using it to accomplish the same tasks. However, it was not to the full extent that webMethods is doing because its capabilities are less.

    The reason we adopted webMethods is that a new project was coming and when we estimated the cost, we found that developing everything in .NET was cumbersome. At that point, we started to look for a tool and settled on webMethods.

    We chose webMethods over MuleSoft because of how quick and easy it is for developing. It is simple and easy to use. The commercials is definitely another reason that we chose it. This was the product that was recommended after the technical evaluation was complete.

    We also use webMethods.io, although that does not fall under Integration Server.

    How was the initial setup?

    The initial setup is of medium complexity, although it depends on your scenario. If you have a simple use case to just integrate, it's easy. The actual installation is very straightforward but we had some complexity because of the zones.

    We had multiple DMZ zones and we have a PCI zone. This meant that there were a lot of firewall rules that needed to be created. It was a greenfield project, so we had to build everything in addition to the webMethods aspect. The project was definitely complex. However, the webMethods setup in isolation was very straightforward. If you just focused on, "Okay, this is the one that you have to install." It's straightforward. If you know what you're doing, it's easy.

    Upgrading is something that we can't do in a very fast manner. It's not like we are going to upgrade every six months. We have to wait a while. On the other hand, that's where the microservices architecture is good because anytime something new is released, we can upgrade to the latest.

    What about the implementation team?

    We completed the initial setup in-house.

    Which other solutions did I evaluate?

    We evaluated MuleSoft and webMethods. There may have been others but these were the top choices. When we asked for demonstrations, these were the products that we looked at.

    This product provides us with a single hybrid-integration platform for all of our integration needs. We do have another product but it is for a very specific use case, and it is separate because of the licensing. Otherwise, webMethods is our go-to for integration.

    What other advice do I have?

    On the topic of development time, this product can save you time but it depends on what you're comparing it to. For example, if you are comparing it to having no platform, where all of the integrations have to be developed from scratch, then this product will definitely save you a lot of time. The undertaking would be massive. If instead, you are comparing it to another product such as MultSoft, then it will be a different answer. It is tricky to estimate because it depends on the tool.

    This is a product that the vendor keeps adding things to. Sometimes, we have to wait until the next version comes out before there is support for what we want to do, but there hasn't been anything major.

    My advice for anyone who is implementing this solution is to spend some time thinking about how it will be used. I have seen instances where the product was being used and didn't work properly. If it is designed nicely then it will work wonders, so spend some time thinking about the design and how it will be used and it's never going to have any issues.

    I would rate this solution a nine out of ten.

    Which deployment model are you using for this solution?

    Hybrid Cloud

    If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

    Amazon Web Services (AWS)
    Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
    Flag as inappropriate
    A. Smart - PeerSpot reviewer
    Enterprise Architect at a energy/utilities company with 1,001-5,000 employees
    Real User
    Top 10
    Enables a host of payment options for our customers and has automated a lot of our manual processes
    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 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.

    How has it helped my organization?

    We're able to secure our front-end website away from our back-end systems using Integration Server. It acts as a go-between. That way, whether we're requesting things from our website or our IBR or our IPT, we can have multiple interfaces. They're secured in their own ways, and they don't have direct access to our back-end databases.

    We're a utility company and before we got this application we would actually send out people to the meters to read them. Sometimes they had handheld devices, but sometimes they had to walk up to the meters. When we switched to AMI meters, we leveraged the ability of the solution to talk to each of the meters on a daily basis, as well as to turn a meter on and off in real time.

    Additionally, we use the same application to process payments. Before this solution, we primarily had walk-in centers and a lot of manual processes for receiving payments. Very few payments were done online or via eCheck. Now we can have a whole host of payment options, as well as enable different payment vendors to connect. It has automated a lot of our manual processes.

    webMethods Integration Server provides a single hybrid integration platform for all our needs. It provides reusability. We don't have to worry about taking each and every point-to-point integration. Now we are hosting a true enterprise service bus, by having a set of APIs that can really be leveraged and reused by multiple vendors and multiple connectors.

    Its adapters and connectors provide the fastest way for us to build an integration. We're able to turn things around pretty quickly. I'm sure there are other faster ways that other people have done, but this meets our needs. 

    It's helped us to become more modern. It's allowed us to service our customers in the ways that they want. They can now use on-the-phone payments or website payments or whatever way they want to do it.

    Internally, it provides a standard way for us to be able to interface with things. Now, we don't have to have unique ways to do so and much more code and numerous ideas on how to do things. We just end up having a standard.

    It provides us with ease of modifying and redeploying integrations. We have been able to do that very successfully. It just makes it easier. We were able to put in an Agile framework, which means that as requirements come up and changes are made, we're able to schedule them on a regular basis. But we were doing that for the long-term before, as well.

    Its support for the latest standards make it possible to plug in modern tooling. We've used that in several places, especially for IoT integrations. The result has been reduced costs and improved customer satisfaction.

    What is most valuable?

    The most valuable feature is its ability to quickly spin up connections between the real-time interfaces, as well as being able to regulate how much traffic moves back and forth between applications. This is important because one of the things that we utilize it for is payments from our customers. We can have multiple customers utilizing the same set of APIs and they can make real-time payments into our system, which is really useful. We don't have to worry about people making duplicate payments or providing incorrect information. And we get that information right away.

    Also, 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. There's a standard utility protocol for talking and several of the applications we have utilize that utility. It's a standard set of APIs, and Integration Server adapted to that right away. For our website we're utilizing standard Wisdom APIs and we were able to create that. The solution is very versatile with all its capabilities and is able to do what we need to do. We even use it for Salesforce.

    It provides us application integration, data integration, business-to-business communications, and APIs. We haven't used it for microservices. That range of features is very important to us. It conducts our real-time payment applications, as well as our real-time integrations between our internal applications.

    What needs improvement?

    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.

    For how long have I used the solution?

    I have used webMethods Integration Server for about 12 years.

    What do I think about the stability of the solution?

    We haven't had any issues. Everything has been working. We like the new version, the new upgrades. It seems they keep improving upon things. We've put in high-availability and fault tolerant solutions so we have had zero downtime due to the system itself.

    What do I think about the scalability of the solution?

    We haven't run into any limitations up until now. We utilize it for a lot of different things, but we haven't run into any speed issues or other problems.

    We end up talking to our customers using the solution and we have over 250,000 customers. Our internal users don't really even notice it. They just see that everything is up and running and available in real time.

    How are customer service and technical support?

    We haven't run into an issue requiring technical support from their side. It's usually something that we have to adapt to or modify. It's usually something internal.

    Which solution did I use previously and why did I switch?

    We used eCheck. It was website-based for point to point integrations. We switched to Integration Server to improve speed to market and have a quicker way to turn things around. We also wanted to put in some newer interfaces that would talk to all of our customers.

    How was the initial setup?

    The initial setup was pretty straightforward. We were able to quickly utilize some templates, things that they already had, to get it up to speed.

    We took our time. We developed and deployed our first product in eight months. Then, over the course of time, we were able to add more and more until we had a robust solution.

    Our implementation strategy was to look at business needs to prioritize things.

    In terms of maintenance, it only requires oversight, nothing too obtrusive. We've got one integration engineer dedicated to all of our integrations and we haven't had any issues yet.

    What about the implementation team?

    webMethods provided the name of a third-party and then we reached out to them and we got them onboard. The company's name was Kellton Tech and they did a very good job. They're still with us.

    What was our ROI?

    We were able to realize ROI fairly quickly because we were able to reduce a lot of the manual work and point-to-point integrations. If you think of truck costs and the amount of gas expense, we don't have to worry about those on a daily basis anymore. Those alone would justify it.

    What's my experience with pricing, setup cost, and licensing?

    It's a good deal for the money that we pay.

    Which other solutions did I evaluate?

    We went through evaluation criteria with three or four vendors and we found this one to be the best. The primary advantages of this solution were the supportability and ease of use. Also, the deployment time was reduced and development was more Java-based.

    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." We're trying to redesign and re-engineer it for that to happen.

    As an overall product and solution, it has met our needs.

    Which deployment model are you using for this solution?

    On-premises
    Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
    Sushant Dayal - PeerSpot reviewer
    IT specialist at Accenture
    Real User
    A mature, flexible product that comes with a lot of features and also allows you to meet any requirement through customization
    Pros and Cons
    • "One of the most important features is that it gives you the possibility to do low-level integration. It provides a lot of features out of the box, and over the years, it has matured so much that any problem that is there in the market can be solved with this product. We can meet any requirements through customizations, transformations, or the logic that needs to be put in. Some of the other products struggle in this aspect. They cannot do things in a certain way, or they have a product limitation, whereas, with webMethods, I have never faced this kind of problem."
    • "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."

    What is most valuable?

    One of the most important features is that it gives you the possibility to do low-level integration. It provides a lot of features out of the box, and over the years, it has matured so much that any problem that is there in the market can be solved with this product. We can meet any requirements through customizations, transformations, or the logic that needs to be put in. Some of the other products struggle in this aspect. They cannot do things in a certain way, or they have a product limitation, whereas, with webMethods, I have never faced this kind of problem. When clients come to me with any problem, in about 99% of cases, I say, "Yes, it is feasible to do through webMethods." It has reached such a level of flexibility and maturity. Most of the things are available out of the box, and even if something is not available out of the box, we can customize it and deliver it for a client's requirements.

    What needs improvement?

    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. CrossVista came up with a solution, which was with the upgraded version of webMethods, but even that was lagging. CrossVista was a bit delayed in coping with the new versions of webMethods. Many times, we get into a situation where we want to know who made a change, when it was made, and how it was before the change. When something that was working well previously suddenly stops working, we want to go back and see who made that change, but because of these version control restrictions, we have to take a longer path. We have to go to the version control system. There is no direct feature in webMethods for that.

    There should be more visibility. Currently, Software AG has multiple tools. They have webMethods, and then they have Terracotta as a different product. They have an API governance tool as a different product. They also have Trading Networks. Some of the tools have a very good UI, and some of them don't. For example, earlier, there was a message broker, and you were able to visualize what is happening to a document on the server. You could plug in a broker and see everything. You could see the number of documents that are there on a broker. You could see different queues and topics created. They then moved to Universal Messaging, which is a nirvana-based universal messaging solution. Now, the plug-in is gone, and from the MWS server, you cannot see what is happening in UM. A different view is created for that in Enterprise Manager, which is a desktop UI application. It is not a browser-based application. So, sometimes to monitor different tools, you have to go to different screens. Everything can't be monitored centrally. If you have MWS, not everything is on MWS. Command Central is a different screen altogether. There should be a centralized UI on which every component can be plugged in so that it's easy to control, view, and monitor everything. That's what I really want to have. The Universal Messaging Enterprise Manager is especially very difficult. Sometimes, it takes time to launch on your desktop. It is basically a desktop application, and you need to have a powerful laptop or hardware to launch it. They should make it a browser-based solution.

    Their support could also be improved. They could be more responsive and quicker.

    For how long have I used the solution?

    I have been working with this solution for almost 12 years.

    What do I think about the stability of the solution?

    Its stability is very high. It is very stable, and I've never seen it crash. In my 12 years of career, there have been hardly one or two instances where there was an issue, but that was also because of some issue in the development where we had memory leakage.

    What do I think about the scalability of the solution?

    Its scalability is good, but you have to plan it in advance. When you are designing your overall infrastructure architecture and delivery framework, you need to put scalability at the core of it. Once your infrastructure is set up, it's not very easy to scale it up or down.

    How are customer service and support?

    Most of the time, admins interact with the support because they handle day-to-day installations or upgrades. I have had some experience with them. I don't have much experience. I hardly had one or two instances where I had to interact with them. It was not very smooth. It was okay. I ultimately managed to get support, but it was not very straightforward. The ticket lingers on for two days or three days, and there are multiple reassignments before it reaches the right party. Based on the little experience I have had, I would rate them a three out of five.

    Which solution did I use previously and why did I switch?

    I have not got a chance to work a lot with other vendors. The first ESB I used was OpenESB, which is Glassfish-based. It was ultimately owned by Oracle when they acquired Sun. I used it back then. I also got a chance to work a bit on microservices and Apigee. Microservices are based on Spring Boot. So, it is a Java product. Apigee is an API governance tool. It is now a Google product. 

    Apigee is a very good tool for API management, but a lot of scripting and coding skills are required. You need to be a genuine coder, and you should have an understanding of JavaScript, Python, or whatever else you are using to work with Apigee, whereas with webMethods API governance, even if you're working as a developer or designer for the integration server, you just need to know the basic concepts of programming. You do not need to know .NET, Java, etc. You just need to know about the integration. You should know how a web service works, how an API works, and how SFTP works. The tool itself is based on Java. It also uses Eclipse IDE. It has similarities with Java. If you feel that something is not achievable through what is provided out of the box or you want to do it in a slightly different or optimized way for your requirement, it gives you an option to write a Java service. There is an option to write Java code, but as the product is becoming mature, the requirement for a Java service is becoming very less. The product is evolving based on the learning of the user experience. It is evolving based on the problem statements and the scenarios where the product was not giving sufficient solutions. They kept including any missing functionalities in the new versions. That's why now the requirement to write a Java service is minimal. In a team of 100, if you have two Java resources, that is more than enough.

    How was the initial setup?

    It depends on what role you are playing. Are you working as a developer or are you working as an admin? For a developer, it's very simple. It's not very complex. You just need an Eclipse-based designer IDE and a browser installed on your machine. That's all. You are all set. However, as an admin, you have to install and maintain all the components. You have to install the patches, and updating these versions is not very smooth. The update manager that they have provided is not very accurate. Sometimes, it fails. If it fails in between, it is very difficult to recover from that failure. So, from an admin's point of view, it is a bit difficult, but from a developer's point of view, there is nothing much.

    We generally have webMethods Integration Server on-prem. We are deploying it on-prem, and there is a deployer, and there is also a webMethods IO component, which is more cloud-based. The VM on which it is installed could be hosted somewhere on the cloud, which is a different story, but the product itself doesn't have any cloud capability where you can directly put it on a cloud provider host.

    What other advice do I have?

    I would rate it an eight out of ten.

    Which deployment model are you using for this solution?

    On-premises
    Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
    Flag as inappropriate
    Enterprise Architect at a computer software company with 1,001-5,000 employees
    Real User
    Top 10
    Enables us to react very quickly to changing business demands, but pricing compared to competitors is an issue
    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 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.

    How has it helped my organization?

    webMethods provides application integration, data integration, business-to-business communications, APIs, and microservices. We use it for all of those purposes. Having that range of features in a single platform is very important, because that means we have a single platform to learn and use. It reduces training costs. It reduces overall infrastructure costs. It even makes hiring easier because we have one set of resources we need to hire for.

    In a very fast moving space—which is weird to say about healthcare, but it has certainly become that in the last few years, and especially in the last year—the ability to move very quickly and to reuse components and to connect to almost anything have become pretty paramount. The solution’s adapters and connectors provide the fastest way to build an integration. The demand curve for integrations goes up daily, so our ability to perform and build integrations is a key core competency.

    What is most valuable?

    Because we use most of the platform, it's hard to call out a most valuable feature, but it's probably the ease of mapping which 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 ease of deploy and maintenance of integrations is a key element for us. If the strength is the mapping tool and the ability to change quickly, and having all of the components that we can then alter as we need to, the result is that it allows us to react very quickly to changing business demands. For example, we have a need to send the same types of data to many different integration partners, and because we're able to tailor the delivery to each endpoint, but use one master flow, it allows great economies of scale.

    What needs improvement?

    I'd like to see the admin portal for managing the integration server go up a level, to have more capabilities and to have a more modern web interface.

    For how long have I used the solution?

    We've been using webMethods Integration Server for four or five years.

    What do I think about the stability of the solution?

    It has been very stable.

    What do I think about the scalability of the solution?

    We find that it scales very well. It's a true enterprise tool.

    Our usage will increase as our business grows. It's a core part of our infrastructure.

    How are customer service and technical support?

    The tool is very good and we haven't really needed to engage with support enough to know if their support for the solution’s adapters and connectors brings long-term stability.

    Support has been there in the couple of times we've needed them. We have gotten a fine response. They completely meet our expectations of support for an enterprise tool. But typically, there's no need for them.

    Which solution did I use previously and why did I switch?

    We had a couple of competing platforms: Systems Integration from IBM, and MuleSoft in the open source world. We switched to webMethods for the support from the company and the range and depth of available adapters and connectors. It gave us more capabilities.

    What about the implementation team?

    We used an integration partner to help us stand it up, so the setup didn't really impact us. We had a total of two or three people involved on our side. We used The Normandy Group and our experience with them was very positive.

    It took us about three months to have the first integration running. The implementation strategy was 

    • install tool
    • get it to work
    • build first integration.

    Those same two people in our organization are the ones involved in the day-to-day maintenance of Integration Server. We have two webMethods technical resources who are responsible for about 400 integration points or integration services.

    What was our ROI?

    We have seen return on investment from using it. We have to compute that every year, and the value is always greater than the cost. It's just that every year it gets harder to justify that value against the competitors. 

    What's my experience with pricing, setup cost, and licensing?

    Keeping in mind that we haven't explored the microservices completely, which has been a key element of their innovation recently, 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.

    Which other solutions did I evaluate?

    I'm familiar with Mirth, in the healthcare space, and IBM SI is still a very large tool. Various other IBM platforms that will do similar things. The space has gotten more crowded over the years.

    The single biggest differences between webMethods and the other solutions are the range of the offering, the connectors, the stability of the system, the fact that it is an enterprise-grade system, and that you can basically do anything you need with it. 

    The con is the fact that you are paying for the best-of-breed solution in the space, and the expense of it can be quite high. When you couple that with the fact that adding Software AG services increases the cost very fast, there is a real detriment to our adding additional Software AG offerings to the portfolio. The sheer expense makes us reluctant to do that. It's still justifying its cost for us, currently, but I feel that there are open source solutions that are charging up very fast. Also, finding resources who are trained in the tool is becoming increasingly hard as they become increasingly more in-demand.

    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 being framed into set paths, we can build what we need.

    I would rate it at seven out of 10. The cost-to-feature value is what brings that number down. The difficulty in finding webMethods-trained resources in North America also brings that number down. The powerful, scalable, stable nature of the offering brings that number up.

    Which deployment model are you using for this solution?

    On-premises
    Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
    Dries Vanmarcke - PeerSpot reviewer
    Technical Architect at Colruyt
    Real User
    Top 5
    Our transformations can be quickly implemented without a lot of fuss
    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 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 Server to integrate our cloud applications. We only have cloud on-premise integrations and not cloud to cloud. That is also why we're not focusing on a hybrid setup.

    How has it helped my organization?

    Integration Server does our business-to-business integrations. It does all of our EDI integrations of passing over our Integration Server and our LAN connects to our internal applications.

    Its adapters and connectors provide the fastest way to build an integration. We don't need to create our own implementations because we can use the adapters. We can immediately connect to the backend systems without creating a lot of our own custom code by using these adapters.

    The vendor's full support for Integration Server's adapters and connectors brings long-term stability to our services because if something changes to the backend application, we don't need to bother with it. Software AG just adapts the adapter and we get a new version. It's much easier working this way.

    Deploying a new application is rather easy. You need a deployer and to build a system. We have built something around it to add it to our continuous integration pipeline, but we have the necessary tools to test our production environments.

    We use the same system to modify or redeploy these integrations. If we have a bug we'll adapt our codes and deploy a new version. The code changes need the most time. If it's a small code change, then it goes very quickly. If it's an important bug, it'll take more time. The deployment and build don't take a lot of time.

    What is most valuable?

    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.

    Using an adapter is quite easy. For example, the SAP adapter works very well, and connecting to custom applications is very easy.

    We would use MQTT when we need to connect to IoT devices. For the other legacy apps, in most cases, we use the adapters. Acquiring an adapter is quite easy.

    Integration Server provides us with application integration, data integration, business-to-business communications, APIs, and microservices. Internally we don't use it for data integration, but it is possible. We don't work with microservices but I know that it's also possible.

    It is important to us that Integration Server offers us a broad range of features like application, data integration, and API. It's important to have that kind of broad setup because it's a service burst. It's in the middle of a lot of integrations. It has to be able to have a lot of features

    What needs improvement?

    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. 

    With an integration platform, it sometimes needs to happen faster because you sometimes have clients or providers that already use new specifications.

    For how long have I used the solution?

    I have been using webMethods Integration Server since 2011. 

    What do I think about the stability of the solution?

    I am very satisfied with stability. It's very stable, we haven't had any issues at all.

    We had a lot of issues with our other solution but none with Integration Server.

    What do I think about the scalability of the solution?

    There are many scalability options, it is possible to add core CPUs to your server or you can add additional servers. Both are possible, both are not complex. The only thing that you need to take into account is then the licensing, but there are no technical issues for scalability.

    How are customer service and technical support?

    Technical support is okay. It's comparable with other companies. It of course depends on the kind of issue that you have, but I'm rather satisfied with their support.

    Which solution did I use previously and why did I switch?

    We were using IBM before webMethods. We used a combination of the two. When we started we had both webMethods Integration Server only for B2B. We used WebSphere Enterprise Service Bus for internal application integration. It's easier to have only one. That is the reason that we chose one of both. The second reason was also that IBM was deprecating their product and asking to switch to another one. Instead of going through IBM, we figured we could do everything with webMethods which is why we completely switched over.

    webMethods had a very good overview of all transactions. That was the main reason we went with them.

    How was the initial setup?

    The initial setup was of medium complexity. It's new so you need to learn it. A tool like this is never easy. webMethods Integration Server was easier than a different solution that we were using. But it's not a walk in the park. You need to spend time on it. There are configuration settings that can't be avoided. It's a complex feature set. We have had more complex systems also in our landscape. It's not just "click, click, click, done."

    I was not involved in the initial deployment. But I know that they upgraded to webMethods Integration Server in a month. It took a few months to learn everything in the system.

    What about the implementation team?

    We worked with a consultant for the deployment. We worked with a consultant from Software AG which went well. We have also worked with other consultants from consultancy companies that were not directly linked to Software AG but work with a lot of Software AG products. They helped us to set up our webMethods products.

    What's my experience with pricing, setup cost, and licensing?

    I don't think webMethods is the cheapest but I think the quality is worth it. But it's not cheap.

    We're satisfied with our choice and the price is not a reason to look for something else.

    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.

    Which deployment model are you using for this solution?

    On-premises
    Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
    Buyer's Guide
    Download our free webMethods Integration Server Report and get advice and tips from experienced pros sharing their opinions.
    Updated: June 2022
    Buyer's Guide
    Download our free webMethods Integration Server Report and get advice and tips from experienced pros sharing their opinions.