webMethods.io Reviews

What I found most valuable in webMethods Integration Server is its strong ESB. It also has strong API modules and portals.

As webMethods Integration Server is expensive, that's its area for improvement.

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

webMethods Integration Server is very stable as a product.

webMethods Integration Server is a scalable product.

I haven't contacted the technical support for webMethods Integration Server yet.

The initial setup for webMethods Integration Server is straightforward. It's just a normal process, so on a scale of one to five, I'd give the setup a rating of four.

webMethods Integration Server is expensive, and there's no fixed price on it because it has a point pricing model. You can negotiate, which makes it interesting.

My company has a partnership with webMethods Integration Server.

My main advice to anyone looking to implement webMethods Integration Server is to figure out the governance target. You also want to aim for a good implementation, so you'll need to know your target.

My rating for webMethods Integration Server is seven out of ten because it could be more innovative and still needs more connectors or adapters.

In the API gateway, there is a new feature that allows us to filter logs within a payload. This has been a useful feature.

The configuring of the JWT token would be improved as it is a confusing process. We require more information on this part of the solution. 

This is a stable solution.

This is a scalable solution. 

The initial setup was straightforward and easy. 

 The pricing of this solution is reasonable. 

This solution is flexible and can be used across a number of projects. I have used it for banking and retail. 

I would rate this solution a nine out of ten. 

webMethods Trading Networks is a good solution for interacting with outside of the organization. We can integrate the solutions with multiple outside the organization. 

We can create multiple users and different types of documents. The same document type we can process to the different kinds of partners. They are reusable, we can map to the respective document type.

I have been using webMethods Trading Networks for approximately eight years.

I have found webMethods Trading Networks to be stable.

webMethods Trading Networks is scalable.

For smaller organizations, I would suggest they use the rest APIs and the API gateway approach.

Technical support is very good and user-friendly. For example, if any B2B interface fails we can easily go into the My webMethods Server, where we can see all of the transactions. There we can find the document type or the partner name or receiver's name. If they provide an invoice number, we can use that invoice number, to find the logs to investigate the issue. Additionally, we can find out the resolution after our investigation.

We had a good experience setting up webMethods Trading Networks, it was simple. We did not face any large challenges. However, My webMethod completely depends on the backend table. That table should be properly installed. If it is properly installed, there are no problems configuring My webMethod server.

webMethods Trading Networks is a bit costly compared to others solutions.

This is a good solution for EDA integrations, I would recommend it.

I rate webMethods Trading Networks a nine 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.

We send EDIs to our customers and then to our backend system, SAP. We're basically integrating our external partners with our backend ERP system. We are customers of Built.io. 

The EDI is pretty robust with the IO. The solution they provide at Software AG is pretty good and solid. The integration with SAP is also good. Those are very solid compared to other products.

There is room for improvement because Software AG is leading to the market for the IO, for the iPass so they may have to improve a lot on the other data, like scaling and also some of the connectors to different types of cloud applications. I doubt they have all the connectors to all the applications, like other products have. They have standard connectors like SAP, Salesforce and the others; they need to have Azure, and AWS, all those connectors. In general, improved scalability and connection to different cloud applications would make a big difference. I think that the product is not completely mature and they need to do some work on that. I would like to see a reduced price for the solution. 

I've been using this solution for three years. 

The stability is pretty good.  

The scalability needs to be improved with connectors to the other applications. 

The support team is very accessible and ready to help with any issues and questions. 

The initial setup was a little complex for me because  you need to install Docker and you need to carry out numerous configurations and then send it out to the API gateway. That's one of the things they need to improve. In other solutions, it's like a click of a button, and it does everything for you. It has some limitations, so they need to improve that and make it simpler for installation. 

License costs are quite high. 

Installation can be problematic, but once you've done that, it's easy to use. It's somewhat lacking with CICD, Continuous Integration and Continuous Development. If they want to integrate a Software AG product into a Docker and deploy using Docker and CICD, those kinds of things are lacking.

I would rate this solution a seven out of 10. 

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

The designer is very helpful in developing services.

Interacting with and developing services is very fast. As long as the requirements are clear, developing service will take no longer than one or two working days.

The tool is very powerful and user-friendly. For example, I have a new team member and within one or two months, they are able to write and deploy services. Once you have a basic understanding of it, you can begin developing.

We would like to have a gateway server included, where we can control the number of requests.

There is an interface in webMethods for building a portal, but we are not using it because the price of the license is too high.

I would like to have a dashboard where I can see all of the communication between components and the configuration. As it is now, it is a lengthy search process. When a request comes in, sometimes you have to go to the administration page and then search the web after that. I need to be able to trace the flow from the port to the service to find the issue and there is no diagram to show me the parts. This is something that would be helpful.

I have been working with WebMethods for more than seven years, since 2012.

We have no complaints about stability.

Scalability has not been a problem for us.

We have not needed to contact technical support.

Our in-house team is responsible for maintenance.

This is an expensive product and we may replace it with something more reasonably priced.

We are considering switching to WSO2 Enterprise Integrator because the pricing is better.

My advice to anybody who is considering this product is that it is a very powerful tool that will empower the development of services. If there is a proper plan then it can be achieved within a short period of time. After a service has been developed and tested, it is moved to the staging environment. Once it is tested, we move it to production. Moving it will not take more than a few minutes.

It is definitely a product I recommend to people who have the money to pay for it.

I would rate this solution an eight out of ten.