SAS Access vs webMethods.io comparison

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

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

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

"ActiveTransfer lets us maintain the file in the staging area before we transfer it. After that, we can remove the file to make sure that the reconciliation process is done. Sometimes we will zip and unzip the files, but if we have a GKB file, we often ignore it."

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

"The most valuable feature is stability."

"The tool supports gRPC."

"From a user perspective, the feature which I like the most about Integration Server is its designer."

"What I like the most about the solution is that it comes with ready-made tools like handling security tokens and OAuth."

"When it comes to the user interface, I'm already really used to it. I cannot say anything against it. For me, it's easy to use."

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

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

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

"I'd like to see the admin portal for managing the integration server go up a level, to have more capabilities and to be given a more modern web interface."

"This solution could be improved by offering subscription based licensing."

"I would like the solution to provide bi-weekly updates."

"The solution has big instances when deployed under microservices or in a containerized platform. They need to improve that so that it is competitive with other integration solutions, like Redis and Kafka. Deployments under microservices with those solutions are much more lightweight, in the size of the runtime itself, compared with Software AG."

"Version control is not very easy. The packages and the integration server are on Eclipse IDE, but you can't compare the code from the IDE. For example, if you are working on Java code, doing version control and deployment for a quick comparison between the code isn't easy. Some tools or plug-ins are there, such as CrossVista, and you can also play with an SVN server where you have to place your package, and from there, you can check, but you have to do that as a separate exercise. You can't do it from the IDE or webMethods server. You can't just right-click and upload your service."

"This product is for larger companies. Compared to TIBCO I think webMethods is better in terms of ease of use and support."

"Business monitoring (BAM) needs improvement because the analytics and prediction module very often has performance problems."

"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 price of webMethods Integration Server isn't that high from an enterprise context, but open-source ESB solutions will always be the cheapest."

"webMethods.io is expensive. We have multiple components, and you need to pay for each of them."

"The vendor is flexible with respect to pricing."

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

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

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

"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 a cost-effective solution."