webMethods.io Reviews

The primary use of the webMethods platform is to communicate with multiple applications and integrate them. webMethods provides business process integration, B2B partner integration, and also uses Web services to connect software applications. My client acquired another company and we are integrating the partners of the acquired company with their clients, using various data communication standards like EDI, EDIFACT, and Rosettanet messages. 

In my previous project we used it to bridge communications between a front-end application and the back-end, connecting them with Web services through SOAP requests and SOAP responses, using JMS queues and broker.

When my organization wanted to migrate the front-end applications from a Genesys framework to .NET for various security reasons, webMethods was used for ESB integration. At the time of migration, there was no work being done on the ESB side, which reduced developers' efforts and all the services were re-used as we used Web services to connect the front-end with mainframes.

When my business client  acquired another business and we were integrating the services, as B2B uses standard communication messages, i.e. EDI, the work made the developers' task simpler, in handling all the interfaces.

All of the following three features provided by webMethods are valuable:

1. Application integration
2. Business process integration
3. B2B partner integration

But among these, I feel B2B partner integration is the most valuable. This module integrates two business partners and exchanges data through electronic data interchange messages in the form of specific standards, without any manual process needed.

When migration happens from the one release to an upgraded release from Software AG, many of the existing services are deprecated and developers have to put in effort testing and redeveloping some of the services. It would be better that upgrade releases took care to support the lower-level versions of webMethods.

On a scale of one to 10, I would rate this product an eight. I feel comfortable using this product with its ease of building interfaces for developers. This is a better integration tool for integrating with various applications like Oracle, Salesforce, mainframes, etc. It works fine in the integration of legacy software as well.

I have been using this solution for two years and four months and I haven't had any difficulty using it for building the interfaces and connecting various business processes, once I had acquired basic knowledge of the solution.

I am using webMethods Integration Server for integrating services mainly, enterprise services bus (ESB). It is a platform for the integration of different systems.

The solution can be used in many industries and different IT systems, such as internal and external databases. We have many dedicated auditors for common projects.

The most valuable feature of the webMethods Integration Server is its reliability. It has a lot of great documentation from the service providers. Additionally, it is easy to use.

This is a great solution and the vendor could improve the marketing of the solution to be able to reach more clients.

I have been using the webMethods Integration Server for approximately six years and I use it daily.

I use the latest version and sometimes older versions.

The solution can be deployed on the cloud or on-premise.

The stability of the webMethods Integration Server is good.

webMethods Integration Server is a scalable solution. There are Microsoft Windows and Linux versions available.

We have more than 10 customers using this solution.

I have used the support from webMethods Integration Server and they have been helpful. The support was able to find the solution to my problems with a fix.

The installation of the webMethods Integration Server is straightforward.

The length of time it takes for the implementation depends on the architecture and how many instances we need to install for the client. However, it typically takes a couple of days.

The implementation process starts with downloading a load that connects to the software. A server takes on the needed components, such as an integration server or universal messaging. You need to follow the integration steps.

We do the implementation of the solution.

There is a license needed to use the webMethods Integration Server.

I would recommend this solution to others.

I rate webMethods Integration Server an eight out of ten.

I'm using the product every day, and I'm working on many different projects. Most use cases are for using webMethods Integration Server as a middleware software or a middleware platform that is connecting to at least two different endpoints. It can be from one side, for example, database, web service, SAP, or any kind of connection, including Salesforce, and the other side can be the same. We are just establishing connections between these systems and doing some transformations and modifications of data in the Integration Server so it can be sent from one side to another.

Clients are mostly using it in order to connect some of their internal systems or to connect to some external systems and some other partner companies. Its benefit is that it's really useful for monitoring and tracking all the activities. And it's important, due to all the flows, all the data, go through this ESB, Enterprise Service Bus. 

The most important thing when using it is that there is a really good community from the producers, Software AG, and the Empower platform, where you can find almost every kind of error or problem that you face. You can find a solution right there in the community.

There is also typical support where you can create a ticket if you are not able to find the issue on your own. If it's something new, then they will approach you and help you in resolving it. 

The best features are these adapters. Software AG developed many different adapters for the usual databases, et cetera. I was not using Salesforce much. However, it's really handy that you have an adapter for these popular platforms. It's just plug-and-play.

When it comes to the user interface, I'm already really used to it. I cannot say anything against it. For me, it's easy to use.

When there is some issue or bug, they work on the development of that. And then, in the next release, they just fix it. I had a few situations when I faced some issues, and then I had to report them. Within the next three weeks, typically, it just gets fixed.

For code version control, you need to use some external software. It would be good to have it just built into the product so that you don't have to use anything external.

The interface could be modernized. 

I've been using the solution for about five years. 

If it's set up properly and if you do it in a good way in large-scale organizations, you need to have a maintenance team that is doing the maintenance and support. If it's working properly and updated properly with the latest versions of updates, then there should be no issues with using it. It is reliable. One of the main benefits of Integration Server is that it is reliable.

Our entire company uses the solution. There might be 100 people using it on a daily basis. 

Scalability is one of the main purposes of the product - scalability meaning that it can adapt to small customers, clients, and even to bigger systems and clients with a lot of data going through the Integration Server. 

Technical support is really good. They are replying really quickly. In a day or two, you can get a response for your issue, or probably even quicker if you mark it as urgent. 

For me, it's fine. I had some contact with Software AG support. They wrote really helpful. And a few times we even had some meetings with screen-sharing sessions so they could help and see the issue. It was really nice. 

I know there are a few really great options on the market; however, I do not have experience with them. 

When it comes to deploying the Integration Server, you just need to follow the documentation, which is really good. The documentation created by Software AG for using and working with each of the products is really nice, and I'm satisfied with that. For the first time you use it, you need to install the Integration Server on Windows or Linux machine or whatever, and if you follow the steps via the documentation, it should not create any issues.

The deployment can be done by one person. It might take an hour or two.

If you are installing many Integration Servers in a cluster, then these things take time to configure the clusters and all other setups related to the network. That said, for the basic product, if you want to use it just for your own purposes, if it's just one instance, it does not take much of your time to get it up and running.

There isn't much maintenance needed after the solution is live. 

The solution was deployed in-house. It's not rocket science. It's easy, and you can do it just by following the instructions. It's a really user-friendly installation.

I'm working in the development part of the company. I'm not aware of the prices.

I would say it's an affordable product. When it comes to big organizations, it's for sure affordable.

We are a Software AG partner.

I'm mostly using the latest version. I was using version 9.9 when I started. Then I was going through all the versions, including 10.1, 10.3, 10.5, and 10.7. Now, 10.11 is the latest one. However, I'm not sure that I started working on that one in any of my projects. 

We are a partner company of Software AG, the producer of webMethods.

New users should look for a list of references and companies that are using this product. 

For a large-scale organization, this is a must-have product. When it comes to Integration Server and the Enterprise Service Bus as the product which needs to be implemented in an organization, it has many benefits like properly monitoring, tracking, and controlling all the flows in the company and outside the company. It's a great product to have.

I'd rate the solution eight out of ten.

I am an integrator of the solution. Our use case is for integration factory for SAP. It is mostly for SAP integration.

The solution is deployed on-premise. We are one version 7.

I am not satisfied with the solution because it takes too much effort to migrate and add new information. The migration could be easier. There's a lot of rework that needs to be done if you go to a newer version.

I have been using this solution for one year.

The solution is stable.

For supporting the solution and installing things, we have maybe 10 or so users. We have no plans to increase usage.

The solution is scalable.

Before using webMethods, I used a different cloud data migration solution for other customers. 

It's a running system, so I haven't had any experience with the installations.

The pricing is a yearly license.

I would rate this solution 8 out of 10.

I would recommend this solution, but it is old fashioned.

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

The most valuable feature is stability. 

We have been experiencing problems with using Terracotta for clustering, which is something that they should improve.

Technical support is an area where they can improve.

I have been working with this product for approximately 15 years. The organization that I am currently with has been using it for about five.

This is a stable product. The Universal Messaging component had some issues with stability, although they have now been fixed. Over that time, they disappointed the customers for about two years.

We had some issues with clustering as we were trying to scale. We are using Terracotta and it gave us some problems.

The technical support team pays attention to our issues but at the same time, they don't seem to have an in-depth technical background. 

We still using IBM MQ today, although these are legacy integrations.

I have just recently started learning about MuleSoft, personally. From my research, I find that MuleSoft is better in terms of their cloud strategy.

The initial setup is not complex. I would say that it is straightforward.

The vendor is flexible with respect to pricing.

I have found that the home-grown products from this vendor always do pretty well, but when they acquire new products from third-parties, there has been some disappointment.

Overall, this is a pretty good product. In fact, my only real complaint is about support.

I would rate this solution an eight out of ten.

The Software AG Designer has been great. It's very intuitive.

The development tools need to be improved. They aren't very effective for us to use as the requirement to use the Software AG Designer is quite big. Sometimes our developer doesn't have a really high-end spec laptop or desktop computer. They sometimes have trouble opening the Software AG Designer to develop something.

The Software AG Designer could be more memory-efficient or CPU-efficient so that we can use it with middle-spec hardware. That would be a great improvement for us in development.

For a new user, the initial setup is hard. 

The quality of the message queuing could be improved. In webMethods they have something called Universal Messaging. Future modules could be included in the Integration Server for different queuing. Currently, they have the basic queuing for messaging. Maybe in the future, they can have built-in different priority queuing to make it a lot faster.

I've been using the solution for about three months. It hasn't been that long just yet.

We are still in development and trial. We didn't reach the point of production where we could really gauge its reliability and therefore we didn't really know how stable it is. We're still in the early stages.

We used to use Red Hat, however, I was not fully in charge of that Red Hat project. I can't speak to any particulars. We didn't really switch. It was a requirement from the existing client to use webMethods as they already had webMethods since version 9.5 and wanted to continue with it.

The initial setup is hard for an early learner like me. It's quite difficult as we were presented with too many features and we didn't really know what was going to be installed.

For example, when we tried to install Integration servers, we had so many other features that needed to be installed, and we don't really know what that was about. By the time we try to install, we forgot to install some other items, such as JDBC for the database. At that point, we needed to install it again. Overall, it's kind of hard for us to use the initial setup.

I'm not really familiar with the commercial side. I don't really know about pricing as I'm only on the operations side.

I'm only a vendor for the customer that already has this operating.

I'd rate the solution at a seven out of ten.

I must be blunt. The solution is really hard to use, as the manual and documentation fail to provide proper explanations, especially to people who are first time users of webMethods, Software AG. I struggle with the installation. I sometimes think that the Integration Server is fine and that I had no problem with the API gateway, only to find myself having to redo this, as I lack a dedicated person who can instruct us on installation. I must rely on the Software AG forum. 

The installation process should be simplified for first time users and be made more user-friendly. 

I started using webMethods Integration Server around a month ago. 

I do not have the privilege of contacting technical support, so I try to make use of the information on the internet to self-learn. 

Prior to webMethods Integration Server, we worked with TIBCO BusinessWorks. This we did for another client. As some of the prospect companies already use webMethods Integration Server, we decided to undertake learning its use. 

The installation process should be improved for first time users, as it is quite difficult, and it should be made more user-friendly. 

I cannot comment on the pricing, as this is in the purview of my boss, from whom I received access to download the product. My role is solely to explore the solution's capabilities. 

There are five people, myself included, who are involved in learning about the solution for the initial project. 

A person who plans to use the solution should purchase a license or subscription, so that he will have someone to instruct him on its use. Operationally, I consider the solution to be quite good. I am referring to the PSR involving the middle integration service development. All the features seem to be there, including SSIS, SQL Server Integration Service and UI. There is a need for much scripting of it. On the development side, webMethod is quite good.

As the solution is good overall, I rate it as an eight out of ten. 

We use it for our ERP systems. It is a middleware tool that we use to connect two systems and the outside partners.

It is good for communicating between the systems and for publishing and subscribing. We can easily retrieve data. It is good in terms of troubleshooting and other things.

Some of the things that we use cannot be done in this solution. For these things, we have to either use a Java service or a util service. There is no predefined or existing service that we can use. So, we have to work on the util service and write on top of it.

Its price can also be better. It is pretty costly because they charge us for each transmission.

I have been using this solution for four years.

There have not been any stability issues.

It is not that much scalable. We have around ten people who are using this solution. Only the integration team uses this solution. Other teams have the ERP system.

It is easy to get support. When we posted a query or some issues, they got back to us. They are responsive and knowledgeable.

It is straightforward and easy. You have the documentation, which is easy to follow.

Based on our team discussions and feedback, it is pretty costly because they charge us for each transmission.

I would rate webMethods API Portal a seven out of ten.