Try our new research platform with insights from 80,000+ expert users

SAP Process Orchestration vs webMethods.io comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Jan 27, 2025

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

SAP Process Orchestration
Ranking in Business-to-Business Middleware
2nd
Average Rating
8.2
Reviews Sentiment
7.2
Number of Reviews
32
Ranking in other categories
No ranking in other categories
webMethods.io
Ranking in Business-to-Business Middleware
3rd
Average Rating
8.0
Reviews Sentiment
6.8
Number of Reviews
92
Ranking in other categories
Enterprise Service Bus (ESB) (3rd), Managed File Transfer (MFT) (10th), API Management (10th), Cloud Data Integration (7th), Integration Platform as a Service (iPaaS) (5th)
 

Mindshare comparison

As of March 2025, in the Business-to-Business Middleware category, the mindshare of SAP Process Orchestration is 8.9%, down from 13.3% compared to the previous year. The mindshare of webMethods.io is 9.4%, up from 7.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Business-to-Business Middleware
 

Featured Reviews

Laxman  Molugu - PeerSpot reviewer
Enhances operational efficiency with valuable prepackaged content and cost-effective pricing
For organizations that operate within an SAP ecosystem, SAP Process Orchestration is recommended due to its cost-effectiveness and the availability of valuable prepackaged content. It is important to consider the needs of your industry, as SAP Process Orchestration may not meet all requirements in consumer-oriented sectors. I'd rate the solution eight out of ten.
Michele Illiano - PeerSpot reviewer
Can function as an ESB along with the core product, with decent integration of message protocols
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. This is why, for most customers who have to deal with big files, I suggest that they use a product other than ActiveTransfer. I would like to note that this problem mainly concerns large files that undergo extra operations, such assigning, unassigning, or file translation. When these operations take place on large files, ActiveTransfer will use up a lot of resources. Within the product itself, I also believe that there is room for improvement in terms of optimization when it comes to general performance. I suspect that the issues underlying poor optimization are because it is all developed in Java. That is, all the objects and functions that are used need to be better organized, especially when it comes to big files but also overall. webMethods ActiveTransfer was born as an ESB to handle messages, and these messages were typically very short, i.e. small in size. A message is data that you have to send to an application, where it must be received in real-time and possibly processed or acknowledged elsewhere in the system as well. So, because it was initially designed for small messages, it struggles with performance when presented with very large files. All this to say, I suggest that they have an engineer reevaluate the architecture of the product in order to consider cases where large files are sent, and not only small ones. As for new features, compared to other products in the market, I think Software AG should be more up to date when it comes to extra protocol support, especially those protocols that other solutions have included in their products by default. Whenever we need to add an unsupported protocol, we have to go through the effort of custom development in order to work with it. Also, all the banks are obligated to migrate to the new standards, and big companies are all handling translations and operating their libraries with the new protocol formats. But webMethods ActiveTransfer doesn't seem to be keeping up with this evolution. Thus, they should aim to be more compliant in future, along the lines of their competitors such as IBM and Primeur.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"Process Orchestration fulfils the need for middleware to mediate types of connectivity."
"It is strategically focused to forecast a global integration platform for our business."
"SAP Process Orchestration is middleware where we are able to manage and interact with everything from a single location. One of the most beneficial areas is monitoring which is very easy because it is all in one place. There are many adapters added recently that can be used for new functionality. The solution is easy to operate and it is more mature than the cloud solution provided by SAP."
"In my opinion, SAP PO is the most mature suite of tools to integrate processes across SAP environments at this moment. It's really unbeatable because it allows you to integrate whatever scenarios you can imagine."
"The solution is stable."
"The solution's technical support is good."
"The performance of data processing has increased."
"SAP Process Orchestration provides extensive integrations with external partners, supports B2B operations, and has prepackaged content that saves development time."
"The tool is very powerful and user-friendly."
"The solution is scalable."
"It integrates well with various servers."
"The Software AG Designer has been great. It's very intuitive."
"Oracle's self-service capabilities, of which we make extensive use, is the most valuable feature."
"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 messaging part is the most valuable feature."
"I feel comfortable using this product with its ease of building interfaces for developers. This is a better integration tool for integrating with various applications like Oracle, Salesforce, mainframes, etc. It works fine in the integration of legacy software as well."
 

Cons

"Process Orchestration doesn't provide authentication for data sent to us, meaning we have to rely on client certificate-based or basic authentication."
"The cloud capability features need improvement."
"The solution could be more scalable."
"The solution is not very scalable because it is at the end of its life."
"The solution needs to move to the cloud."
"It requires some maintenance."
"We encounter challenges while connecting to MQTT and MQDD adapters."
"Process Orchestration needs to provide secure connectivity as no one has any data information."
"The certifications and learning resources are not exposed openly enough. For instance, they have a trial version which comes with only a few basic features, and I think that community-wise they need to offer more free or open spaces where developers can feel encouraged to experiment."
"​Large file handling is pretty hard comparatively to other middleware tools."
"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 stability of the various modules of the product suite have been a bit of a concern lately. Though their support team is always easy to reach out to, I would prefer it not come to that."
"The high price of the product is an area of concern where improvements are required."
"The price should be reduced to make it more affordable."
"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."
"This is a great solution and the vendor could improve the marketing of the solution to be able to reach more clients."
 

Pricing and Cost Advice

"The solution is highly-priced."
"The product is not a low-priced solution, but I can say that it is competitively priced in the market."
"It is a very expensive solution. We only pay for the license."
"It's not an expensive solution."
"The pricing depends on what type of client you are with SAP and the contract you have. There is a licensing cost that needs to be paid."
"Normally, you will have to choose CPU-based licensing...I rate the tool price a five out of ten."
"There are fees in addition to the licensing."
"My company deals with different pricing models of the product, according to which we don't pay for the solution directly, but we do pay for the maintenance part."
"Pricing has to be negotiated with the local Software AG representative. SAG can always prepare an appropriate pricing model for every client."
"webMethods Trading Networks is a bit costly compared to others solutions."
"It is an expensive tool. I rate the product price a nine out of ten, where ten means it is very expensive."
"The vendor is flexible with respect to pricing."
"Pricing is the number-one downfall. It's too expensive. They could make more money by dropping the price in half and getting more customers. It's the best product there is, but it's too expensive."
"Some of the licensing is "component-ized," which is confusing to new users/customers."
"It is a cost-effective solution."
"It's a good deal for the money that we pay."
report
Use our free recommendation engine to learn which Business-to-Business Middleware solutions are best for your needs.
842,296 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Manufacturing Company
17%
Computer Software Company
15%
Financial Services Firm
7%
Energy/Utilities Company
6%
Financial Services Firm
14%
Computer Software Company
13%
Manufacturing Company
12%
Retailer
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about SAP Process Orchestration?
It provides essential features such as continuous monitoring of all interfaces are crucial for our needs.
What is your experience regarding pricing and costs for SAP Process Orchestration?
The main concern is the cost. If additional help is needed due to lack of skill, we have to pay for SAP support.
What needs improvement with SAP Process Orchestration?
There are two main areas for improvement: performance and cost. The cost is quite high, and if it were reduced, it might also improve the performance, potentially allowing us to access a more effic...
What do you like most about Built.io Flow?
The tool helps us to streamline data integration. Its BPM is very strong and powerful. The solution helps us manage digital transformation.
What is your experience regarding pricing and costs for Built.io Flow?
webMethods.io is expensive. We have multiple components, and you need to pay for each of them.
What needs improvement with Built.io Flow?
webMethods.io needs to incorporate ChatGPT to enhance user experience. It can offer a customized user experience.
 

Also Known As

SAP NetWeaver Process Integration, NetWeaver Process Integration
Built.io Flow, webMethods Integration Server, webMethods Trading Networks, webMethods ActiveTransfer, webMethods.io API
 

Overview

 

Sample Customers

Lenovo, Dansk Supermarked A/S, Ego Pharmaceuticals Pty. Ltd, Kaeser Kompressoren
Cisco, Agralogics, Dreamforce, Cables & Sensors, Sacramento Kings
Find out what your peers are saying about SAP Process Orchestration vs. webMethods.io and other solutions. Updated: February 2025.
842,296 professionals have used our research since 2012.