webMethods.io Reviews

webMethods provides the ESB backbone for us since more than 8 years without any hick ups

High throughput and excellent scalability.

Programming model with flow is hopelessly outdated. Forced migration from MessageBroker to Universal Messaging requires large scale reimplementation for JMS

ESB is rock solid. Products on top of Integration Server have much less stability.

No. Absolute top.

Webmethods ESB works, but support is layered an requires escalation every so often

We used IBM MQ Series and migrated due to licensing issues.

Significant topics with bespoke programming model (FLOW language), difficult to find experts and if, they are expensive. Wouldn't do it again.

Mixed team with vendor.

N/A

Initialy good pricing and good, if it comes to Enterprise license agreements.

It's a rather mature solution with lot's of design choices we would not accept in 2017. We are in fact considering to leave to other products.

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.

There are actually a lot of valuable features. Terracotta is a very good component that enables us to arrange data caching and look at the solid state. Also, the API gateway is a very good component that can handle relevant caching and integrations and also load permitting. There is a message term for this. There are many components that we are currently using and all of them are very important. Also, we will use the DPM for workflow management and digital user transformation in the future.

I think they need to improve the API gateway to be able to replace F5 for example. Also, handling the certificates and their implications with other applications needs some improvement.

We need more dashboards and reporting engines that can provide detailed information for management. In short, we need better analytics.

It is stable, but it depends on the development team, not the platform itself. The platform itself is stable and has been used before by a lot of big companies and entities, but the old integration services are not related or tightly coupled with the platform itself. If you don't have good developers that can implement a good architecture or a good design, you will have issues.

It is easy to scale. We can really scale it up. We have had no issues with this.

Right now, we have an establishment of one organizer per platform but our plan is to use it as the only, single point of integration. The entire enterprise, all applications through all departments, and all IT will use the platform.

We are planning to increase the usage of the platform continuously over the next five years.

Currently, we have an incident open with them, but I think we need to give them more clarifications about it. There may be an issue with the product itself or perhaps it is from the implementation side. We couldn't reach a conclusion yet. We are supported 24 hours a day, it's full support.

Overall we are satisfied with the support because the main advantage is actually that you find someone to help you in time. Anything after is solvable; you will reach a solution. The ability to find someone dedicated is the main advantage.

I have an establishment of the IT department and the solution team but we were migrating from an old architecture and old application integration. It wasn't a platform, but rather a mix of solutions including webMethods but an older version. Now we have migrated from this older version to our new version. But we are migrating among a different integration solution.

Some parts were straightforward, but installing the platform was a little complex, especially since we use Linux instead of Windows. Opening ports, network restrictions, managing the network, and managing the users and components were all a little bit complex.

We did it on our own here, in our company. We have installed it over about four environments: development, SIT, production, and pre-production. All of this has taken about one month to finish.

It is expensive, but we reached a good agreement with the company. It is still a little bit expensive, but we got a better deal than the previous one.

My advice is to put more focus on implementation rather than on the platform itself. This is more important than the platform because finding someone that knows how to fit the components is more important than having very good components that no one knows how to use.

I would rate this as eight out of ten, because of the scope we have already implemented. We didn't face many complex issues or troubles.

I've been developing with SAG webMethods in Telco industries for integrating provisioning (CRM) end-to-end Billing, BSS and OSS, Banks/Insurance/Finance integrating bancassurance, provisioning, Switching&Allocation and Government Instance (Oil and gas) integrating B2B oil company to government reporting.

Time effective by cutting down development time and resource efficient to developer burden, enhance agility and integration between end-to-end applications, platform

The Integration Server

It's obvious that the heart of the product lies here. It's comprised of all aspects of ESB (Enterprise Gateway, Adapter, TN, Java) and BPM (task, rules engine).

Universal Messaging

Universal Messaging is a Message Orientated Middleware product that covers JMS, MQTT, AMQP.

Universal Messaging design supports both broker-based and umTransport communication, and thus comprises client and server components. The server component has specific design features to support each of these classifications of client, as well as Scheduling and Triggers, Plugins, Federation, Clustering, and Low Latency IO.

The Java Service section, which is probably needs more different manners for a new developer. It doesn't represent OOP very well, just a method and proprietary interface for input parameter called IData, which consists of Maps (key, value). You can still be creating classes under the shared section of the methods. But also the documentation of webMethods Java API it doesn't cover much clarity for the usage

Regarding the Stateful session inbound to ESB (Integration Server). It seems that the Stateful session sometimes doesn't die out when the transaction is finished, but waits until the timeout expires (although quite often it doesn't even died even after timeout expires, which eventually would flooding the server).

You have to buy another license for clustering named Terracotta which also had several different license, basically it was acting as a multicast and a cache, so if one of your node is processing something it would write into Terracotta, and then the other node would recognize some process going on so it wouldn't try to do the same processes which would be make double transaction for instance. It also can be use for data cache so you could have better performance fetching frequently data called rather than query it somewhere else e.g Database or REST Resources

Around 6 on a scale of 1 to 10. They don't help much enough actually, if there's any bug we have to wait for another patching rather than get emergency help

No, they won the PoC in the beginning. And mentioned as Leader in Gartner

Quite complex in setting up the BPM environment, the UDDI service (Centrasite), and also the API Management. But nonetheless there's documentation for each product 

I've been in vendor/consultant so I have enough experience to do it my own in-house.

I never done the accounting, I'm an engineer ?

I suppose webMethods aim for large-scale enterprises which is why the price is high, but with high output and better outcomes.

Some of the licensing is "component-ized," which is confusing to new users/customers.

Yet you can also choose between perpetual or periodically terms, in case you do not want to be bothered to buy another version once the newer version released you should consider periodic license.

Yes, TIBCO (was good enough IMHO) and Oracle Fusion Middleware (it's quite complicated IMHO).

I have to say that all SoftwareAG products are tightly proprietary, which means you can't just download and install for study purposes or to play around with them. You have to call their partner/product representative just to download the trial, which is quite different from their competitors. That makes the product unfamiliar to mid-low enterprises.

Also, their products are "componentized" in terms of licensing and tightly coupled, which means that some components may be licensed while some are a prerequisite to other components. So it could be that you have to buy two to get one and a half (pretty amazing isn't). But overall it is a great product.

Another thing is that made me bit upset was that the certification/training in South East Asia (which is my region) is not "individual friendly," meaning that if you want to get developer certified, you have to join to one of their partner companies or bulk order.

We use the solution in the API gateway services. 

I like the tool's scalability. 

webMethods.io Integration's installation is complex. It should also improve integration and connectors. 

I have been working with the solution for more than ten years. 

The tool's support is good. 

Positive

I have used Apigee before webMethods.io Integration. 

The installation took about four to six weeks to complete. You don't need a big team to handle the deployment. We relied on one system architect to handle it. The tool's maintenance is also not difficult. 

webMethods.io Integration's pricing is high and has yearly subscription costs.  

This solution suits enterprises and I would rate it an eight out of ten. 

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.

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.

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.