webMethods.io Reviews

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 use webMethods for integrating our applications.

The best part of webMethods is the out-of-box features that it provides to users, which ultimately saves on effort put into development.

All of the components are very independent but are tied together to give the business value.

The EDI is very eye-catching.

We have been having some non-technical, functional issues, which is why we're exploring other products.

The price should be reduced to make it more affordable.

I have been using webMethods for between 10 and 12 years.

The pricing and licensing costs for webMethods are very high, which is the only reason that we might switch to another product.

As we use webmethods, we continue to look for and research other products that are in the market. We have not decided if we are moving away from it yet, and there is no specific timeframe for making that decision, but we will continue to research alternatives.

Overall, it's a great product.

I would rate this solution a seven out of ten.

Our primary use case is for communication between different systems and automation of business processes.

It has enabled us to integrate some systems which needed a form of translation.

The most valuable components of the solution are API management and EDI.

The Flow language mapping tool could be a little easier to use. The interface needs improvement.

The technical support served its purpose. We do not need to use it much.

We used a different solution and we switched because it was a product that was being phased out.

We considered other solutions along with webMethods Integration Server, including BizTalk and Tibco. There were other solutions but they were outside our planned budget.

I would rate this product as an 8 or a 9 out of ten.

webMethods is primarily used to integrate applications. While one can always do the same by building APIs (Java, .NET, etc.), webMethods provides a robust, scalable, and easy to manage platform to do so.

The need is primarily felt when integrating multiple application for a large enterprise. To list a few, one can use webMethods to integrate web-based, file-based, database-based applications. Of course, this is just the tip of the iceberg. It has multiple modules for specific integration types, like a Trading Networks module for business to business integrations, business process models for graphical representations for executing business processes. One can also build small Web-based application using CAF and DSP.

Given that you have one integration API in place, it takes very minimal effort to scale it to any other application that might want to use the same. Its flow-based development environment is a breeze and makes it really easy to re-use most of the existing components and build up a new API.

The second most important aspect is managing the components. It’s fairly easy to view, move, and mange access across different components. Different component types are categorized and can be viewed in a web based administration console.

I would say the core Web-based integrations work the best with webMethods. They are the most efficient and robust implementations one can do with webMethods. There have always been some ups and downs in its specialized modules, but I have found its core integration platform the most reliable.

The stability of the various modules of the product suite have been a bit of a concern lately. Though their support team is always easy to reach out to, I would prefer it not come to that.

• Capability to handle almost all e-business standards: RosettaNet, EDI, ebXML Messaging Service, SWIFT, FIX, and CIDX
• Web-based user interface: Makes administration and monitoring much easier
• Segregation of user tasks: Controlled user permissions and gives better control over the TN environment
• Clear view of transactions: Makes analysis and monitoring easier
• Capability to set up Trading Partner Agreements (TPAs): Makes business secure and more efficient

• We could set up all trading partners in one place with different data transfer protocols
• Makes the middleware environment more efficient
• Helps the admin team: Has a clear view on transactions and their processing status without digging into actual implementations

Configuration and interaction of trading partners in the TN with an ActiveTransfer product.

I have been using this solution for nine years.

New deployer could handle almost all deployment related task for TN components.

We had some minor issues with the EDIINT module which were resolved in the newer version.

We did not encounter any issues with scalability.

I would rate the technical support at quite a high level.

We did not use any other solution previously.

The setup was straightforward.

It is an add-on product to the webMethods product suite. The capability it offers is at a very good price.

We did not evaluate any other options as we already had the webMethods product suite. It was more logical to go for the SAG product.

It gives value for your money. It is easy to implement and maintain.

Typically, webMethods Server and Mediator is used as an ESB. webMethods platform is used to build an EAI platform, enabling communication between many internal systems and third-party operators.

In my opinion, the best advantages are: 

• platform scaling
• graphical data mapper (Designer and webMethods Developer in oldest versions)
• integration BPM process layer with services
• service management via packages.

Business monitoring (BAM) needs improvement because the analytics and prediction module very often has performance problems.

Additionally, this product has too many gaps. You find them after update installations. This should be covered by automatic testing.

Very often there have been stability issues, but typically the source of problems was in the IS configuration or deployed services. Many of problems exist only in AX system (IBM JRE).

No scalability issues. Typically, you can not scale the solution if it is not well designed (architecture, service layers, data processing).

I had some problems with the webMethods support team. They provide fixes very often but sometimes they do not work properly.

Yes, even currently I am using other suppliers' products. The main reason for this situation is that the solution was chosen by the company, and changing technologies is very expensive.

Pricing has to be negotiated with the local Software AG representative. SAG can always prepare an appropriate pricing model for every client.

I think this is a very good and mature solution, but you have to be aware of the pricing. You can use an open-source solution and spend the money saved on licensing for a custom implementation.

We use webMethods Trading Networks mostly for B2B use cases.

webMethods Trading Networks is a stable solution.

The solution could be improved in the VTA part.

The solution should include REST API calls.

I have been using webMethods Trading Networks for more than 20 years.

webMethods Trading Networks is a scalable solution. We mostly recommend the solution to big companies.

The solution's initial setup is straightforward.

Since webMethods Trading Networks is much like proprietary software, users should try it on the trial version first and do some POC.

Overall, I rate webMethods Trading Networks a nine out of ten.

Ease of implementation and flexibility to hold the business logic are the most valuable features.

We have used webMethods because of its ubiquitous nature to talk to various technology platforms. Also, the solution had a finite life, webMethods provided a quick integration solution since it is relatively easier to implement, and also, it can hold the business logic in itself.

The client was planning to go in for a separate data exchange platform/Business Information Warehouse as a large-scale global project slated to be alive after five years.

It helped to improve the efficacy of production planning to the market demands and it has improved the quality due to faster information on quality issues.

Mostly, an improvement is needed in the product's documentation.

The documentation deficiencies were in the following areas; since it has been a while, I could recall the top instances where the escalation reached to my level.

wM SAP Adapter User Guide - Example, like Message Broker setup was unclear, leading to issues during Testing and we had refer the internet forums to understand that there is a Message Broker Cleanup utility and that needs to be setup as well.

Release Notes: Used to cover only the latest update for the SAP changes. What has been done to the older version (SAP R/3 4.6, etc.) were not mentioned.

I have used this solution for nearly a year.

In 2008, the technical support's response time was much longer than expected.

There was an implementation issue, i.e., some of the preconditions were not clearly mentioned, so we had to dig through multiple options to troubleshoot and find the right steps.

It was an Enterprise license and I am not sure of the current status.

We evaluated TIBCO.

Put the business first, consider the business architecture and requirements before deciding to go with webMethods. Today, there are multiple open-source, cheaper solutions like Talend available and we can consider those as well.