OpenText 360 for SharePoint vs webMethods.io comparison

"The fact that it allows for the internal sharing of information is very good."

"OpenText 360's best features are platform independence and its performance when searching large numbers of documents."

"In terms of its most valuable features, this solution, in general, will provide all you need and it's very convenient to use. We can share our details to collaborative platforms. We can give access to users. It's pretty flexible."

"This solution has good connection and we do not need to migrate everything in order to protect the repository."

"The most valuable feature of OpenText 360 for SharePoint is its performance. The solution is one of the best in the market if you search the internet."

"We concentrate on the legal industry, such as legal libraries. It's the most structured solution we have used and implemented for five years."

"It's all now on cloud subscription, so you can use all the features without worrying about making the system updates patches."

"The fact that you can see and create something that fits your business is the most valuable thing in this platform. It is a customizable product, so it fits your needs."

"A product with good API and EDI components."

"webMethods API Portal is overall very valuable. It is now a comprehensive API catalogue that serves various purposes, including API assessment and evaluation."

"It has a good integration server, designer, and a very good API portal."

"This solution has given us a competitive advantage because we have better automation and insight."

"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 most valuable feature of the webMethods Integration Server is its reliability. It has a lot of great documentation from the service providers. Additionally, it is easy to use."

"Clients choose webMethods.io API for its intuitive interface, promoting seamless interaction and quick communication between systems."

"The stability is good."

"Its licensing needs to be simplified. Currently, its licensing is very complex. It contains a number of pieces, and you have to be an expert in reading all the conditions in the license. They should simplify the licensing and make it easier to understand. It would make a customer's life easier."

"They need to come with more out of the box solutions, rather than depending on customers to develop them."

"I would like for there to be even more integrations in the next release and I believe that the price could go down a bit."

"Integration is an area where the solution lacks."

"An area for improvement would be how the platform handles large volumes of documents. It also doesn't provide a very good, robust backup and restore capacity. In the next release, I would like the search technology to be improved."

"OpenText 360 is generally stable, though there are sometimes issues with document size or format."

"The graphical user interface had to be more user-friendly. It's not as intuitive."

"If I have to really create an internal knowledge management portal, if I have to compare SharePoint and WordPress, WordPress is far, far better in regard to the SharePoint option."

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

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

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

"Forced migration from MessageBroker to Universal Messaging requires large scale reimplementation for JMS."

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

"Support is expensive."

"Technical support is an area where they can improve."

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

"On-premises version is expensive"

"Pricing is a part of the enterprise agreement that we have."

"The solution has a very complex pricing model."

"OpenText 360's price varies depending on how long you've been a customer, how many licenses you have, and which products you use."

"SharePoint uses a subscription model."

"It has a reasonable price."

"There is a license needed to use OpenText 360 for SharePoint and we pay annually. The price of the solution could be less expensive."

"Its price is reasonable, but its licensing is very complex. This platform contains a number of pieces, and you have to be an expert in reading all the conditions in the license. They should simplify its licensing."

"Initialy good pricing and good, if it comes to Enterprise license agreements."

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

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

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

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

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

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

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