SAS Access vs webMethods.io comparison

"The most valuable feature is you have native access to the external databases."

"The most valuable part of SAS/ACCESS is what it is made for: connecting to remote systems that are not part of your physical SAS environment."

"The most valuable aspect of the solution is the ease of access to the data in those databases."

"The product is very stable."

"We have a reusable code that we can replicate for any new interfaces."

"The MFT component of webMethods, for example, is easy to set up and convenient to use. It handles files very efficiently and it is easy to automate tasks with complex schedules. Monitoring is centralized to MWS which can be used to monitor other products as well (Trading Networks, BPM, MFT, etc.)"

"The product supports various types of digital documents, including XMLs and EDI."

"Some of the key features are the integration platform, query mechanism, message handling within the bus, and the rules engine. We've had a really good experience with webMethods Integration Server."

"The solution's ease-of-use is its most valuable feature, in which complex issues may be resolved."

"Our use case is for integration factory for SAP. It is mostly for SAP integration."

"The most valuable feature of webMethods Integration Server is all the capabilities it provides. We leverage most of the features, that they have offered to us. Our vendor has made some additional features on top of the webMethods Integration Server and we use all the features together."

"I can't really recall any missing feature or general improvement that is needed. We don't really add too many new kinds of databases and therefore our needs are already met."

"The solution can provide access to the newer databases that come out sooner."

"The pricing model needs to be reconsidered and adjusted."

"In terms of improvements, maybe on the API monetization side, having users able to create separate consumption plans and throttle all those consumption plans towards the run time could be better."

"We got the product via a reseller, and the support from the reseller has been less than desirable."

"The installation process should be simplified for first time users and be made more user-friendly."

"The product must add more compatible connectors."

"With respect to the API gateway, the runtime component, the stability after a new release is something that can be improved."

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

"One area that needs improvement is the version upgrade process. Many customers I've worked with encounter challenges when transitioning from their current version, such as x or 9, to a newer version. The process is not smooth, and they must shift their entire website."

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

"The pricing model is complex and is based on modular packages as well as the size of the applicable environment."

"The solution's pricing and licensing are expensive."

"The product is expensive."

"It is an expensive tool. I rate the product price a nine out of ten, where ten means it is very expensive."

"This is an expensive product and we may replace it with something more reasonably priced."

"This is not a cheap solution but, compared to other products such as those offered by IBM, the pricing is similar."

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

"It is a cost-effective solution."

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

"I am not involved in the licensing side of things."