webMethods.io Reviews

Our customers use webMethods Integration Server to integrate their retail solution, the frontend with the backend. 

The solution's ease-of-use is its most valuable feature, in which complex issues may be resolved. The visibility with Java is not so easy. However, the solution allows a person to know where his application is in the ecosystem, which application he is using, what the protocol is and the number of requests. The solution makes identification easy. 

The installation process is very complex, there being many products, each having its own. The deployment should be simplified. 

We have been using webMethods Integration Server for more than 12 years. I have been working with it over the past 12 months and continue to do so. 

The solution is very stable.

The solution is scalable. 

The installation process is very complex, there being many products, each having its own. The deployment should be simplified. Other than this, I feel it to be a good tool.

Java's visibility is not so easy and fairs unfavorably with that of the solution.

I'm an integrator and use the product to provide solutions to vendors.

The solution is a good ESB tool.

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

All of them are helpful.

It facilitates

• communication between a lot of applications
• maintainability and security and
• facilitates the integration of new applications.

Software AG should investigate the reporting of products like Spotfire from TIBCO.

Two years.

No problem with stability in versions 6 and 7.

No problem with scalability in versions 6 and 7.

I have not encountered a situation that requires technical support.

Yes, I've used TIBCO products like BW, BPM, and Spotfire. I switched because the fist project was finished and the company just had products of the TIBCO type.

I only use the product in the company where I work. The company bought the product so I don't have any idea.

Product is easy to use and work on, very interesting and very helpful.

This is a middleware tool from Software AG, so when there is a need for EAI/ESB, or B2B; the use cases and implementations are plenty and can vary according to business and enterprise architecture.

For example, an internal application like SAP sends data which is received and transformed by webMethods to EDI, XML, or another user-requested format, and sent to an external business partner (via jms/FTP/WS call).

One to many, or many to one transformation and delivery is the simplest example.

• Integration
• Transformation
• Easy development
• Connectivity and adapters
• The variety of tools that are part of the webMethods product suite

Licensing is an issue since all products do not have central licensing. UM has a different license, IS has a different license, etc. This differs from client to client.