SAP Integration Suite vs. WSO2 API Manager

The case of the SAP Integration Suite shows outstanding capability in handling huge data, and especially when handling corporate portfolio data with multiple owners. But we have noticed that in the cases of moving data from the older banking system, it is necessary to further refine the system. It does an excellent job of the current credit scoring.

WSO2 is a unique product that provides pre-integrated components like Gateway, Integrator, identity management, etc. Hence it is best suited when the requirement is not just only publish the APIs but also to secure and transform the APIs. WSO2 can be an overhead if only Gateway is required, as there are other very lightweight gateways available in the market.

Incentivized

• Broad Connectivity: SAP Integration Suite excels in connecting diverse systems, including SAP and non-SAP applications, databases, and third-party services.
• Pre-built Integrations and Templates:The suite provides a library of pre-built integrations and templates for common business scenarios.
• User-Friendly Design Tools:
• API Management:

Incentivized

• API Security
• API Transformation
• API Monetization

Incentivized

• Could be even more business friendly with programming language abstracted
• Ability to simulate the integration flow instead of a real run
• Have some kind of an AI-assistant suggesting the optimal design of an integration flow as it's being built (best practice assistant)

Incentivized

• Installation of this product is a hell. You need to be an expert to get this running together with WSO2 Analytics. It uses a really confusing method of "port + 1" to connect extra products. I guess this was meant to provide a handy way to add new WSO2 products. In reality you'll need to scroll through numerous config files to set this straight. If you use this out of the box, everything will work all right. But the moment you add SSL certificates, DNS names and you'll need special ports to configure your firewall, this product becomes unmaintainable.
• The "Store" provides a nice way to group API's. However, the "Publisher" does not... if you have more than 30 API's searching for API's becomes really annoying.
• The number of configs in this product is huge. As a developer myself, I've never seen (and definitely never created) a product that needed that much config files. Installation and maintenance of products should be stupidly simple, since no developer nor infrastructure person wants to learn something that "just" needs to be a tool.. opposed to being a whole new area of expertise. After using WSO2 API Manager for a while, we wanted to change the admin password... this should be simple enough, like just change the password in "Carbon." But nope. The whole WSO2 environment crashed. We just gave up. Too dangerous.
• Why so many different "products"? Publisher, Store, Carbon, and numerous hidden interfaces. Analytics, ESB whatever... No wonder there are so many config files and port issues. Make it simple!!!

Incentivized

SAP Integration Suite is very helpful to us in many ways to manage purchase procedures, stocks, and data of vendors and suppliers. Also, it helps to manage data for service providers. SAP Integration Suite has the tool to conduct training and evaluation. Unique features like the cloud can provide access from any place and by any device is very helpful.

Incentivized

It is a user-friendly platform that enables fast setup for new subaccounts, launchpad and applications.

Incentivized

Support is hard to reach and takes a long time to get a response.

Incentivized

Work with an SAP implementation partner, if possible.

Incentivized

We used to have a in house application in Camel and Karaf as a middleware, and after we migrate to S4HANNA we decide to give a try and move to the cloud with SAP Integration Suite, knowing the capabilities and the needs that we have in the company and the projects that were running on premise in our middleware.

Incentivized

Nevatech Sentinet: The easiest API Manager available. No knowledge of how the product works internally needed! It works with C# (not java... with all it's config files... really? Java developers?). Great way to categorize API's into groups (domains). All of which is drama in WSO2. But Sentinel is really expensive... Mulesoft: Nice and clean. Again, no expert knowledge needed of how the product works internally. Like using word... or any other application, except WSO2. Have java developers never heard of exposing configurations through a user inyterface?? Mulesoft, however is really expensive. Azure: Not cheap!! And a chaotic interface too. But it pays! If you have a Microsoft account already, this is your next step. We chose WSO2 4 years ago because it was free... but we're moving to azure now. And we're very happy with that decision.

Incentivized

• Ability to have multiple integrations across different SAP systems or modules and be able to actively monitor in one place
• APIs already exist for the different fields in SAP products and are easy to locate
• Can set email notifications to aid with monitoring and alert business process owners of issues

Incentivized

• Positive impact on continuity and API standardization.

Incentivized