CloverETL vs webMethods.io comparison

"No dependence on native language and ease of use.​​"

"Server features for scheduler: It is very easy to schedule jobs and monitor them. The interface is easy to use."

"Key features include wealth of pre-defined components; all components are customizable; descriptive logging, especially for error messages."

"Connectivity to various data sources: The ability to extract data from different data sources gives greater flexibility."

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

"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."

"The product is powerful, straightforward, and easy to use."

"webMethods platform is used to build an EAI platform, enabling communication between many internal systems and third-party operators."

"The solution is scalable."

"There were no complexities involved in the setup phase...The product is able to meet my company's API protection needs."

"Operationally, I consider the solution to be quite good."

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

"Its documentation could be improved.​"

"Needs: easier automated failure recovery; more, and more intuitive auto-generated/filled-in code for components; easier/more automated sync between CloverETL Designer and CloverETL Server."

"​Resource management: We typically run out of heap space, and even the allocation of high heap space does not seem to be enough.​"

"It would be nice if they had a change management system offering. We built our own deployer application because the one built into webMethods couldn't enforce change management rules. Integration into a change management system, along with the version control system, would be a good offering; it's something that they're lacking."

"Upgrades are complex. They typically take about five months from start to finish. There are many packages that plug into webMethods Integration Server, which is the central point for a vast majority of the transactions at my organization. Anytime we are upgrading that, there are complexities within each component that we must understand. That makes any upgrade very cumbersome and complicated. That has been my experience at this company. Because there are many different business units that we are touching, there are so many different components that we are touching. The amount of READMEs that you have to go through takes some time."

"The patching of infrastructure is not very smooth and improved authentication should be added in the next feature."

"The improvement needed is related to the model's position. As of now, it seems to be more of a conceptual idea rather than a widely implemented solution. For how long"

"There should be better logging, or a better dashboard, to allow you to see see the logs of the services."

"The on-premises setup can be difficult."

"In terms of improvement, it would be better if it adapted quicker to open standards. It took a while for API specification before the last version was available. The spec of version two was rather quick."

"In terms of scale, I would give it a four out of 10."

"The solution's development license is free for three to six months. We have to pay for other things."

"There are no hidden costs in addition to the standard licensing fees for webMethods. For corporate organizations, it's a very cheap or fairly priced product, but for growing or small businesses, it's quite expensive. These businesses would probably need to consider an enterprise services bus at some point. Thus, from a pricing point, it closes out non-cooperate businesses."

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

"The pricing is a yearly license."

"It's a good deal for the money that we pay."

"With our current licensing, it's very easy for us to scale. With our older licensing model, it was very hard. This is definitely something that I would highlight."

"The price of webMethods Integration Server isn't that high from an enterprise context, but open-source ESB solutions will always be the cheapest."

"Always plan five years ahead and don’t jeopardize the quality of your project by dropping items from the bill of materials."