webMethods.io Reviews

We primarily use it as an integration server. We have integration use cases, including B2B, et cetera.

It is reliable and works very well. 

The integration with platforms is great.

It's straightforward to set up. 

Technical support has been responsive when we need assistance.

It is a very stable product.

The solution can scale as required. 

We're fine with the product offering.

It is quite expensive. 

I've used the solution for more than a decade. 

The solution is very stable. I'd rate the stability ten out of ten. There are no bugs or glitches. It doesn't crash or freeze. 

It is highly scalable, to my knowledge. The organization has used it for almost two decades without issue. I'd rate the scalability nine out of ten. 

We have about 100 users on the solution. 

We do not have plans to increase the number of users, to my knowledge.

We've used technical support, and they have been fine. They are very responsive. 

Positive

I had used other products previously. I use this solution since it has a lot of use cases, and the organization chooses to use the product. 

It's easy to deploy. It has its own deployment tool, which makes it very fast. We can use it both on the cloud and on-premises. 

We have a 13 to 17-member team of developers that can handle the deployment. 

We handle the initial setup in-house according to the government model. Our IT team handles the process. 

I can't comment on the exact ROI; however, it is a very useful product.

The solution has a yearly licensing fee. It is very costly.

I'm not sure if there are any extra costs involved in using the solution. 

I'd recommend the solution to others, depending on the use case. There are many factors that would be highly dependent on its success. 

I'd rate the solution ten out of ten. 

The tool helps us to streamline data integration. Its BPM is very strong and powerful. The solution helps us manage digital transformation. 

webMethods.io needs to incorporate ChatGPT to enhance user experience. It can offer a customized user experience. 

I have been working with the product for ten years. 

The solution is stable.

webMethods.io is scalable. 

webMethods.io's technical support is amazing. They have different mediums for communication, such as chatbots, emails, and phones. The response is based on the incident severity. They respond in a day even if the incident is of low severity. 

Positive

I have used IBM Message Broker and Apache. The product is much easier, and you do not need to have extensive knowledge. 

webMethods.io's deployment is not difficult and can be completed in a few hours. 

The tool is worth its money. 

webMethods.io is expensive. We have multiple components, and you need to pay for each of them. 

The product incorporates different layers of security, ranging from denial-of-service protection to IP denial and other features aimed at enhancing security. Given the importance of safeguarding information from exposure and unauthorized access, maintaining strong security measures is our key priority.

The solution focuses on low-code and zero-code approaches. This means users don't need extensive technical expertise. Instead, they can use drag-and-drop functionality.  I rate it an eight out of ten. 

We use it to manage and secure APIs. It is particularly useful when dealing with a large number of APIs from various systems like banking, government validation, and more. It makes sure data is accurate and protected and helps systems work well together.

What I like the most about the solution is that it comes with ready-made tools like handling security tokens and OAuth. API Gateway does the hard work of keeping things secure and managing who can access what, making it easy and safe without lots of custom work.

One area for improvement in webMethods API Gateway is orchestration. Currently, API Gateway lacks built-in orchestration capabilities, so organizations may need to rely on other applications for this purpose. For example, if you are calling two services and one of them fails, you may need another application to handle the rollback or recovery process. Improving orchestration within API Gateway could simplify complex service interactions.

I have been using webMethods API Gateway for almost two years.

The technical support is a bit slow. It took them more than two weeks for a single ticket. I would rate it a seven out of ten.

Neutral

Setting up webMethods API Gateway can be easy or complex. It depends on what your company needs.

It is an expensive solution and not very suitable for smaller businesses.

My advice to people who are considering using the solution is to keep in mind that if you have a background in software development, especially with Java, you will likely find it easier to work with the platform. Overall, I would rate webMethods API Gateway an eight out of ten.

We don't use webMethods Integration Server directly, but we use another offering from one of our vendors. They have built a layer on top of the webMethods Integration Server and that's a solution we have been using.

webMethods Integration Server is the underlying component, but our software vendor, has made some enhancements to the webMethods Integration Server and they offered it to us. That's what we are currently using along with some of the other solutions in the supply chain space.

Their offering is more of an integration framework across all their systems and this is how we have been using the system. webMethods Integration Server is our primary integration tool across all the solutions that we have in our supply chain.

The most valuable feature of webMethods Integration Server is all the capabilities it provides. We leverage most of the features, that they have offered to us. Our vendor has made some additional features on top of the webMethods Integration Server and we use all the features together.

webMethods Integration Server could improve on the version control. I'm not sure if Web Method has some kind of inbuilt integration with Bitbucket or GitHub or some kind of version control system. However, that's one area where they can improve. 

The migration of the code between environments could be better. If they come up with some kind of a continuous integration process to promote the code from one life cycle to the other, that may ease the day-to-day activity for us.

I have used webMethods Integration Server for approximately seven years.

webMethods Integration Server is a stable solution for our usage.

The scalability of the webMethods Integration Server is good.

Our IT team is using the solution in my organization.

We plan to increase our usage in the future.

I have not needed to use webMethods Integration Server support.

We used other solutions before using webMethods Integration Server.

The maintenance team needed for webMethods Integration Server is minimal.

We have seen a return on investing using webMethods Integration Server.

I rate our return on investment for webMethods Integration Server a four out of five.

The solution has been doing the job for us, at least with respect to the landscape and the integrations we have in place. However, it is on a case-by-case basis.

I rate webMethods Integration Server an eight out of ten.

One of our clients is a chain management company. They have many APIs which do a lot of integrations, including B2B integrations. For that particular client, our APIs are on APIs check and handing the deals and restock. Everything is hosted on our API gateway. They can use a scan and access those APIs and do operations for sales orders and invoices.

The most valuable aspect of this solution for me has been the configuration-based UI. Once you get the hang of it, it enables you to easily develop an API. In addition, it has many in-built policies that are quite handy. We are also able to write our custom policies. I also like the daily logging option. Another handy feature is Kibana with the dashboard, which outlines the day-to-day operations in great detail.

There are things that could be improved with the webMethods API gateway. One thing is that it's too attached to the integration service and we'd like it to be a little bit more independent. We would like for them to separate operations so that it doesn't rely on the bulky integration server and so that it can be used everywhere. I would like for this to be included in the features since the client I work with always tends to avoid the solution. And if the client does not have existing interfaces with it, they choose not to proceed. 

I have been using this solution for more than 30 years.

I would rate the stability of this solution a 10, on a scale from one to 10, with one being the worst and 10 being the best.

My impression is that this solution is scalable. I wouldn't say auto-scalable because of the on-premises part.

I would rate their technical support a seven, on a scale from one to 10, with one being the worst and 10 being the best. The reason for this rating is that they are good, but they could still be improved. There is no premium support, and the regular support responds within a day or so.

Neutral

I would rate the initial setup process a six, on a scale from one to 10, with one being the worst and 10 being the best. I would say it's not too easy, but also not too difficult. It can be complex if you don't have experience with it and, in that case, you will not find the setup easy. 

For us, the deployment was fast; it took maybe a couple of minutes. One person can do the deployment on their own. The maintenance is done I think quarterly or every six months through patching.

Our model of deployment is on-premises.

I would rate the pricing plan of this solution a seven, on a scale from one to 10, with one being the worst and 10 being the best. The licensing is on a yearly basis.

This solution is a good fit for small, medium, and larger enterprise companies.

I would advise other people looking into this solution to get it because it adds an additional feature to the capabilities of your web method templates. Also, it uses existing web flow services to enable you to leverage your existing services that are already paired on your on-premises system or into the traditional system of your work method.

Overall, I would rate this solution an eight, on a scale from one to 10, with one being the worst and 10 being the best.

While I do not recall exactly which version of webMethods.io Integration we are using, I believe it to be 10 or 12. 

We use the solution in respect of eight or nine integrations that we did with the different applications.

Oracle's self-service capabilities, of which we make extensive use, is the most valuable feature. 

The products, at the moment, are new and there should perhaps be support for the older version of the protocols. While I know that they have the new versions, which are actually needed, I don't believe they have that capacity when it comes to any integration with older systems. This is because I believe us to be more advanced nowadays, with what they are doing for the roadmap of new technologies.

The solution is very stable and we have had no issues with it thus far, two years running. 

The solution is, for sure, scalable and can go to containers and dockers. I believe this to be the plan for the moment. 

I found the technical support to be very good. Although we implemented during the pandemic, us being in need of the resources from a side KSA, we did not face any difficulty, as the resources are available locally. Also, we were able to do the implementation during the peak of the pandemic. 

We had a very good implementation engineer, so the deployment was very straightforward, nothing complex. Once the input and output signatures are aligned between the systems, everything is as it should be. 

The number of people needed for maintenance will vary with the features one is using. We use features which may require two to three people. The same holds true with implementation. 

While I have yet to calculate a return on investment, I have definitely seen one. Owing to the number of users, I would say that it is huge. This is because we have used it for self-services, something which is very productive. 

In the past, we dealt with paperwork, but we now use the solution to digitize everything. We use it as a platform towards the goal of digitization, which was the whole point of the project itself. 

In the past, we had Oracle ESP and we replaced that with Software AG. Contractually, it was Oracle ESB, at which point we got the change request to switch over to Softwares AG webMethods.

I feel the solution provides a very good platform for interconnectivity between the applications, beyond what most users have, which is point-to-point connectivity. This is a good platform for doing multipoint connections and allows one to use the APIs in multiple ways for a variety of purposes and services. It also has caching features, which greatly allows one to cache the data. It has so many caching mechanisms for speeding up the data towards the users. 

This saves the user from having to go to the backend to retrieve the data, as it is available on the ESB, something which is cached and can be released to the user. This saves time going to the backend. 

I rate webMethods.io Integration as a nine out of ten. 

The API Gateway and Portal go together. It's not one or the other. Essentially they're just leveraged for overall enterprise API management facilities, being able to go on the API development life cycle, being able to go on the API run time, API monetization, things like that. Usually, most organizations, most of our customers use APIs to supplement other architectures, typically microservices-based application architecture, and SaaS integration etc.

API Gateways and API Management in general first and foremost standardizes and democratizes the Integration problem across all IT domains. API Gateway specifically allows for centralizing all integration interfaces to a simple style and normalizes the patterns of security, access control, cross-domain compatibility across the enterprise. API Gateways also enable enterprise integration across various public cloud infrastructure and enable Hybrid nature of Enterprise IT.

On the API gateway, I would say the runtime metrics that the gateway collects are definitely useful.

The product provides a lot of insights into the operations of the API itself at runtime.

The cloud version of the solution is very easy to set up.

The stability has been good. The performance is strong.

The scalability is excellent overall.

We have found the technical support to be very helpful and responsive when we have questions.

In terms of improvements, maybe on the API monetization side, having users able to create separate API consumption plans and to be able to throttle API execution against those consumption plans at run time could be better. Those are abilities that might need some improvement.

The on-premises setup can get a little complex, needs to be more simplified.

I've been dealing with the solution over the last three or so years at this point.

The stability and performance are excellent. 3G really comes strong on an enterprise-scale in terms of stability and performance. It doesn't crash or freeze. There are no bugs or glitches. We find it to be reliable.

We have found that the solution scales quite well.

API management is all about internally leveraging the software development life cycle, across various domains. Typically, most customers, when they adopt API management, they are delivering it for their entire IT software development organization, not just the integration team. The application team and the database team and so on will also use it. Everybody will be on board. Sometimes we have seen customers onboard about 60, 70 developers and then maybe a few additional external consumers. However, we also see some customers with very small teams of around 10 people. It works well for both.

We've dealt with technical support in the past. There's always that possibility, especially with newer versions, that we might run into some technical issues. However, tech support and issue management are both pretty straightforward.

You can create tickets with the portal on Software AG through Software AG's support portal. They respond within 24 hours usually, and try to resolve the issue quickly. Sometimes the issues might need a product or a quote fix, which might take a day or two. Otherwise, they might be able to look through the knowledge base and give us a solution immediately. 

They have a pretty good response time and offer quality service. We're pretty satisfied with the level of support.

In terms of setting up the solution, the solution offers both cloud and on-premises options. The on-premise license and setup can be done yourself. That can be a little complex depending on what is the overall deployment architecture that is needed. 

However, webMethods API also comes in a cloud form, the webMethods.io, and that is just a subscription. Most of our customers can just subscribe to it and they don't really have to worry about the setup. Everything is already pre-set.

Typically, while the on-premises setup is somewhat complex, we don't really require people to be continuously monitoring it once it's launched. The setup itself might take less than a week or two, depending on the size. 

In terms of maintenance, unless there's a lot of APIs subsequently developed and running, you don't really have too much. Once the customer starts developing a lot of APIs and puts a lot of those APIs into production, that's what will contribute to the support and monitoring needs of the team. 

Typically one person can handle deployment and maintenance. Of course, the cloud doesn't really require the same amount of work.

The pricing can fluctuate. I don't have the numbers on hand, however, I can say that they're somewhere in the middle in terms of pricing. They aren't the most expensive or the cheapest. They're priced right for their capabilities and the quality of service as well as the stability and performance on offer. They're well priced for their general offering.

We are partners with Software AG. We've been a partner for more than 20 years now.

I'm a consultant. I work with a consulting company. 

I'm familiar with API Gateway, API Portal, and Active Transfer.

The API Portal and Gateway form the layer of API management, however, usually, API management does not go on its own. There's typically some level of an integration layer behind it as well. Either a customer is applying an API management layer on top of an existing integration layer, or, if not, a customer is starting fresh and has to apply both layers subsequently, or consecutively, kind of like creating an API management layer, and integration, a hybrid integration layer. 

Both go together, especially in data integration, or in application integration and cloud application integration.

I'd rate the solution at an eight out of ten.

The API Gateway and the Portal go together. It's not one or the other. Essentially they're just leveraged for overall enterprise API management facilities, being able to go on the API development life cycle, being able to go on the API run time, API monetization, things like that. Usually, most organizations, most of our customers use APIs to supplement other architectures, typically microservices, based application architecture, and so on.

On the portal, the user management and the API life cycle management are definitely robust. 

They have nominal features for API. They have a self-serve API portal as well. That means consumers for APIs can come onto the portal and learn about various APIs that they can put into the consumption model. 

The initial setup of the cloud version of the solution is very easy.

The solution can scale.

The product is quite stable.

Technical support is responsive and quite helpful.

We have found the pricing of the solution to be fair.

On the API monetization side, being able to create separate consumption plans and throttle all those consumption plans towards the run time. Those are abilities that might need some improvements.

The on-premises setup can be difficult.

I've been dealing with the solution over the last three or so years at least.

The stability and performance are definitely very good. 3G really comes strong on an enterprise-scale in terms of stability and performance. It doesn't crash or freeze. There are no bugs or glitches.

The solution can scale quite well. A company that needs to scale can do so.

API management is all about internally leveraging the software development life cycle, across various domains. Typically, most customers, when they adopt API management, they are delivering it for their entire IT software development organization, not just the integration team. The application team and the database team and so on will also use it. Everybody will be on board. Sometimes we have seen customers onboard about 60, 70 developers and then maybe a few additional external consumers. However, we also see some customers with very small teams of around 10 people. It works well for both.

We've dealt with technical support in the past. There's always that possibility, especially with newer versions, that we might run into some technical issues. However, tech support and issue management are both pretty straightforward. 

You can now create a ticket on an issue with the portal on Software AG through Software AG's support portal. They respond within a day, and at least try to resolve the issue. Sometimes the issues might need a product or a quote fix, which might take a day or two. Otherwise, they might be able to look through the knowledge base and give us a solution immediately. In general, they have a decent response time and a decent quality of service. We're satisfied. 

In terms of setting up the solution, there are two ways. The first is that you can have an on-premise license and set up this conference yourself. That can be a little complex depending on what is the overall deployment architecture that is needed. On the other side, webMethods API also comes in a cloud form, the webMethods.io, and that is just a subscription. Most of our customers can just subscribe to it and they don't really have to worry about the setup. Everything is already pre-set.

Usually, while the on-premises setup is fairly complex, we don't really require people to be continuously monitoring it once it's launched. The setup itself might take less than a week or two, depending on the size of the enrollment. In terms of maintenance, unless there's a lot of APIs subsequently developed and running, you don't really have too much. Once the customer starts developing a lot of APIs and puts a lot of those APIs into production, that's what will contribute to the support and monitoring needs of the team. Typically one person can handle deployment and maintenance. Of course, the cloud doesn't really require the same amount of work. 

The pricing fluctuates. I don't have the numbers with me, however, I can say that they're not the cheapest in the market, and they're not the most expensive either. They fall right in the middle, and they're priced right for their capabilities and the quality of service as well as the stability and performance on offer. They're well priced for their general offering.

We are partners with Software AG. We've been a partner for more than 20 years now.

I'm an IT consultant. We are a consulting company, most of my teams are certified in Software AG technology, and we've worked for a lot of customers leveraging that technology.

We typically deal with the most up-to-date versions of the solution, although occasionally, one or two might be a version behind.

A lot of the API Portal and Gateway form the layer of API management, however, usually, API management does not go on its own. There's typically some level of an integration layer behind it as well. Either a customer is applying an API management layer on top of an existing integration layer, or, if not, a customer is starting fresh and has to apply both layers subsequently, or consecutively. It's kind of like creating an API management layer, and a hybrid integration layer. Both go together, especially in data integration, or in application integration and cloud application integration.

Overall, I would rate the solution at a seven out of ten.