CentraSite vs webMethods.io comparison

"The governance is powerful, and you can look up services very easily, which may reduce some development cycle time."

"Currently, we're using this solution for the integration server which helps us to integrate with the mainframe."

"The tool helps us to streamline data integration. Its BPM is very strong and powerful. The solution helps us manage digital transformation."

"EDI is robust and integration with SAP is good."

"The main assets are its flow language, debugging, and Broker. Flow language is far better and more flexible for debugging."

"Within the new version, webMethods API Gateway gives us an end-to-end lifecycle from the creation of the API up into the development, deployment, and promotion into production/live. The current end-to-end lifecycle of the API gives us enough authority and governance of the API. We know what are currently live services, what is in the testing stage of development, and what version that has been commissioned. So, the full life cycle itself gives us full authority and governance of the API."

"With webMethods, the creation of servers and the utilization of Trading Networks facilitate B2B integration. It resolves any related issues effectively."

"I like the stability of the webMethods Integration Server."

"The messaging part is the most valuable feature."

"The setup is mild. It's not so simple and not very difficult. You can make it happen with some configuration, but it's not easy for non-professional people."

"t doesn't represent OOP very well, just a method and proprietary interface called IData."

"When it comes to scaling, it requires more RAM and more machines."

"We'd like for them to open up to a more cloud-based solution that could offer more flexibility and maybe a better rules engine or more integration with rules engines."

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

"The logging capability has room for improvement. That way, we could keep a history of all the transactions. It would be helpful to be able to get to that without having to build a standalone solution to do so."

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

"A potential drawback of webMethods.io API is its adaptability to legacy systems, which can vary in compatibility."

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

"Most of my clients would like the price of the solution to be reduced."

"Sometimes we don't have a very clear idea what the licensing will entail at first, because it can be very customizable. On one hand, this can be a good thing, because it can be tailored to a specific customer's needs. But on the other hand it can also be an issue when some customer asks, "What's the cost?" and we can't yet give them an accurate answer."

"The pricing is a yearly license."

"It is worth the cost."

"Its cost depends on the use cases."

"Pricing is the number-one downfall. It's too expensive. They could make more money by dropping the price in half and getting more customers. It's the best product there is, but it's too expensive."

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

"The vendor is flexible with respect to pricing."