OpenText 360 for SharePoint vs webMethods.io comparison

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

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

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

"We have manual processes, so the workflow enables us to automate a number of these processes."

"The product has a strong and easy integration with Teams."

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

"The collaborative environment for long-term archival or record management is great."

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

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

"High throughput and excellent scalability."

"What I found most valuable in webMethods Integration Server is that it's a strong ESB. It also has strong API modules and portals."

"Given that you have one integration API in place, it takes very minimal effort to scale it to any other application that might want to use the same. Its flow-based development environment is a breeze and makes it really easy to re-use most of the existing components and build up a new API."

"Oracle's self-service capabilities, of which we make extensive use, is the most valuable feature."

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

"It's a visual tool, so our transformations can be quickly implemented without a lot of fuss. The fact that we have an easy way to expose REST services is also very interesting. It offers the possibility to connect over GMS to synchronize message brokers."

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

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

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

"The user interface could definitely be improved."

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

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

"We have a very good time to market tool, and the development platform should be made user-friendly. Mostly, it's just support."

"Integration is an area where the solution lacks."

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

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

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

"The orchestration is not as good as it should be."

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

"The UI for the admin console is very old. It hasn't been updated for years and is pretty much the same one that we started with. This is something that could be refreshed and made more modern."

"The patching of infrastructure is not very smooth and improved authentication should be added in the next feature."

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

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

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

"SharePoint uses a subscription model."

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

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

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

"It has a reasonable price."

"The solution has a very complex pricing model."

"On-premises version is expensive"

"With our current licensing, it's very easy for us to scale. With our older licensing model, it was very hard. This is definitely something that I would highlight."

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

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

"The product is very expensive."

"The solution’s pricing is too high."

"It is worth the cost."

"Some who consider this solution often avoid it due to its high price."

"I signed a three-year deal with them. It is a yearly locked-in price for the next three years."