SAP Process Orchestration vs TIBCO BusinessWorks comparison

"The most valuable features of SAP Process Orchestration are the standard APIs that we can use."

"The initial setup is easy."

"It is strategically focused to forecast a global integration platform for our business."

"It is a scalable solution."

"The standard adapter with EBA abilities is the most valuable feature. It has good process integration."

"SAP Process Orchestration provides extensive integrations with external partners, supports B2B operations, and has prepackaged content that saves development time."

"The most valuable feature is the seamless integration with backend systems."

"It provides essential features such as continuous monitoring of all interfaces are crucial for our needs."

"We use the solution to develop applications."

"The most valuable feature is the integration."

"Good TIBCO BusinessWorks features are the admin console and the ability to roll back to the previous version."

"The solution is very scalable. It can handle a lot. We have encryption plus integration servers running on that platform currently."

"BusinessWorks reduces development time, helping developers to focus on business logic."

"One of the most valuable features is that it's a simple development. It takes a short time to get services to work."

"The initial setup of TIBCO BusinessWorks was straightforward since we have used the solution in our organization for a long time."

"Good performance and reliability."

"The monitoring governance offered by SAP is too technical and needs to be geared more toward business users."

"I feel that support is an area that needs improvement. They need to improve the response time and address the customer's issues as soon as possible."

"Its administration management feature needs to be simpler to use."

"The responsiveness of technical support needs to be improved."

"The product roadmap suggests it will approach the end of support in several years, and a lot of innovations are now implemented by SAP not in SAP PO, but in SAP Integration Suite, hence, the platform is stable, but doesn't receive a lot of new features in recent updates."

"It is scalable, but there can be performance issues with high data volume or traffic, especially during month ends."

"It requires some maintenance."

"I think the main area that SAP PO should improve on is offering pre-delivered content like they do when you use SAP Cloud Platform Integration (CPI). SAP should not forget that they still have a lot of customers using Process Orchestration and they should focus more on providing pre-delivered content in SAP PO."

"This solution's cloud could be improved. I don't know whether it was because we didn't have the internal expertise or if it was the product itself, but since they came later—I think only two or three years into the cloud—after many other iPaaS that had been in the cloud for longer, I feel that maybe they haven't matured in terms of the cloud."

"The learning curve takes time compared to webMethods."

"The communication protocols could be improved."

"Its price can be improved. For medium enterprises, it is a very expensive tool. In the market, you won't get many resources for this solution. You won't find many developers in the market very easily. The latest version of TIBCO (6.4 or 6.x) is not very stable. It has got many issues. We have raised this with TIBCO, and they are taking a lot of time to come up with a fix, which is making us move away from this product. Some of the performance-tuning aspects are also missing in version 6. They should provide performance-related fixes, which will be helpful for the customers. If you are migrating from the current version to the container-supported version, it is quite expensive. The product has evolved, but it is very pricey. That's one of the challenges. They have provided all the features that are there in other products, but this is a platform upgrade. The platform has completely been changed from 5.x to 6.x, and we can't use the same environment. We can't run both versions on the same server as VM. The development environment is entirely different. In version 5.x, there was a proprietary designer. Now, it has common plug-ins developed on top of Eclipse."

"The initial setup is not easy."

"The solution’s customer support should be improved."

"The cost of the solution has room for improvement."

"The container-based image is too large and this makes auto-scaling difficult."

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

"The solution is highly-priced."

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

"The fee for maintenance is costly."

"There are fees in addition to the licensing."

"The price of SAP Process Orchestration was reasonable."

"We subscribe to annual licenses, and the competitive license cost is reasonable."

"The payments made for service are the only addition to the standard licensing fees that we pay for the solution."

"The solution is too expensive. It's one of the most expensive solutions out there, particularly because there are so many open-source competitors on the market. I don't know the exact numbers, however."

"TIBCO BusinessWorks is a very expensive solution."

"I give the cost of the solution a four out of ten."

"The product is not cheap."

"TIBCO BusinessWorks is expensive."

"The license is expensive, and I would rate it one out of ten."

"TIBCO licensing is yearly and very costly for a company like ours."