SAS Access vs webMethods.io comparison

"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 most valuable feature is you have native access to the external databases."

"In the API gateway, there is a new feature that allows us to filter logs within a payload. This has been a useful feature."

"The performance is good."

"I like the solution's policies, transformation, mediation, and routing features."

"The tool supports gRPC."

"webMethods Trading Networks is a good solution for interacting with outside of the organization. We can integrate the solutions with multiple outside the organization."

"It’s fairly easy to view, move, and mange access across different components. Different component types are categorized and can be viewed in a web based administration console."

"One valuable feature is that it is event-driven, so when new data is available on the source it can be quickly processed and displayed. Integration is definitely another useful feature, and B2B is one area where webMethods has its own unique thing going, whereby we can do monitoring of transactions, monitoring of client onboarding, and so on."

"The solution is scalable."

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

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

"I have noticed that webMethods ActiveTransfer has had problems when handling large files. For example, when we receive (and perform operations on) files that are larger than about 16 MB, the software starts losing performance."

"webMethods Integration Server could improve on the version control. I'm not sure if Web Method has some kind of inbuilt integration with Bitbucket or GitHub or some kind of version control system. However, that's one area where they can improve."

"Some things could be improved, especially how ActiveTransfer handles third-party file transfers. It would be nice to have a native file-watching mechanism for when you're scheduling jobs with a third-party scheduler. Currently, we are using an outside file watcher solution to check the files before the file transfer. It checks the location to see if the file is there. If the file is there, it will prepare it for transfer. If the file isn't available, it will send an email it can create a ticket send it now. We recommended adding this file watcher mechanism."

"Rapid application development has to be considered, especially for UI, where user interference is crucial."

"For code version control, you need to use some external software."

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

"Documentation needs tuning. There is a lot of dependency with SoftwareAG. Even with the documentation at hand, you can struggle to implement scenarios without SAG’s help. By contrast, IBM’s documentation is self-explanatory, in my opinion."

"Need to see more API portal features like monetizing APIs and private cloud readiness."

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

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

"The product is expensive."

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

"Currently, the licensing solution for this product is pretty straightforward. The way that Software AG has moved in their licensing agreements is very understandable. It is very easy for you to see where things land. Like most vendors today, they are transaction based. Therefore, just having a good understanding of how many transactions that you are doing a year would be very wise. Luckily, there are opportunities to work with the vendor to get a good understanding of how many transactions you have and what is the right limit for you to fall under."

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

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

"I do think webMethods is coming under increasing pressure when it comes to their price-to-feature value proposition. It's probably the single biggest strategic risk they have. They're very expensive in their industry. They've been raising the price recently, especially when compared with their competitors."

"The pricing and licensing costs for webMethods are very high, which is the only reason that we might switch to another product."