Likelihood to Recommend If you are truly using IBM API Management for an API gateway, you will be ok. if you start trying to build custom scripts to transform messages complex in nature, it will soon become unmanageable.
Read full review E-commerce Integration:Scenario: An e-commerce business utilizes SAP Integration Suite to integrate its online storefront with back-end systems. This includes connecting order processing, inventory management, and customer relationship systems to ensure a smooth and efficient order fulfillment process.Real-time Analytics and Reporting:Scenario: A retail organization utilizes SAP Integration Suite to enable real-time analytics by integrating data from multiple sources. This includes POS systems, online sales platforms, and customer feedback applications, providing timely insights for informed decision-making.
Read full review Pros Import APIs - We have an existing inventory of APIs and services, so having an easy import process was required. IBM provides the ability to import Swagger so the process was quick and easy. Service Offerings - Can create plans to control various model offerings for varying clients depending on the need. You are not locked into a tier structure and can customize if a need arises. API Usage - visibility into the use of an API with a wealth of reporting information allows you to support an API from a production use to trending and forecasting any future growth. Read full review The drag-and-drop interface, as well as SAP regular improvements to its pre-packaged content, are also excellent features. The security features (such as the cloud connection for sending data to the local system, as well as encryption and scrambling) are really beneficial. Unlike other tools I've tested, the SAP connectivity package offers access to third-party cloud apps. Prototyping may be completed more quickly, and the team can determine whether or not to proceed with the integration depending on the feedback process. Read full review Cons Troubleshooting deployment pipeline - identifying issues with your api based on restrictions through a deployment pipeline is difficult. If a quality assurance environment is less stringent than a production environment, making sure your api is accessible and configured appropriately is tough. Code level scripting is limited to javascript and xslt. so if any complex fanning needs to occur, you are limited in tooling. Administration is more cumbersome than it needs to be. There are roles/profiles that are defined, but to use a group email for the approval or use of an api needs to managed better. A more thorough thought process needs to be defined - which I think IBM is tackling as an improvement. Read full review There are some loopholes there by which some problems appears, may be different usage in different modules, as i am working on PP module but we lack sometime with linkage of MM module. There are some loopholes there by which some problems appears, may be different usage in different modules, as i am working on PP module but we lack sometime with linkage of MM module. Read full review Likelihood to Renew 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.
Read full review Usability It's very easy to use and configure.
Read full review Support Rating Support is hard to reach and takes a long time to get a response.
Read full review Implementation Rating Work with an SAP implementation partner, if possible.
Read full review Alternatives Considered There are a lot of similarities between
Apigee Edge and IBM API Management. Some of the differences at the time of this posting is... 1) IBM APIM/C integrates better with other products. Dynatrace is used to track API and service specifics with the ability to offload those statistics for operational reporting. 2) If you are evolving from DataPower, IBM API Management is a logical choice to support additional REST APIs. 3) Generating keys is simple. Integration of those keys with a secure data vault is easy as well for your consumer.
Read full review I selected it because its now one of the best thing to do and to work. As we are currently working from home it makes the work easy and comfortable and yet the main usage will be in office the environment created will be simple. The UI logic is based on some calculations which will rely on some natural intuations of mind and when it comes to mind it is easy.
Read full review Return on Investment Centralizing on an API management platform was imperative. Being able to support SOAP UIs as well as REST APIs was required. Because of the tooling, service inventory and provisioning can be managed - regardless of the pricing and cost structures are used. Constructing plans that provide tiering options based on rate limits help in onboarding new consumers. The lesser cost in onboarding through an API gateway outweighs the cost of modifying/configuring an API to handle multiple clients. Defining guidance and onboarding practices while rolling out the product also helps in the adoption, reference architecture, and governance that can save your company money. Read full review In the long run will enable us to undeploy our on premise solution As long as integration suite doesn't support all capabilities PO has complete migration is hard Will probably be cheaper than our on premise solution when we are completely migrated Read full review ScreenShots SAP Integration Suite Screenshots