IBM API management enables creation and management of web application programming interfaces (API).
N/A
Oracle Integration (OIC)
Score 5.1 out of 10
N/A
The Oracle Integration Cloud Service is an iPaaS providing prebuilt integration flows between applications, including other Oracle products. The Integration Cloud Service is scaled for enterprises, with prebuilt codeless adapters for on-premises and SaaS systems and low-code automation capabilities.
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.
For all type of integration except those with a huge volume. It can deal with 20MB of transactions and processing of 1GB file when a file is being read using file or FTP adapters. It cannot be used for EDI as this support is not there. OICS is a perfect fit for other integration and is best when a customer has Oracle applications in the landscape. It is even greater if you have a requirement to create a custom form and make use of Process Cloud. All of these work very well together seamlessly. API needs can be handled by APIary.
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.
Auto-association of Oracle applications prepopulates the application connector select box and preconfigures Oracle Integration (OIC) using secure credential access for faster integration.
Various other system connectors are available to use readily.
User-intuitive experience--Connectors, integrators, and dashboard can be seen on one page.
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.
Currently, it is not retaining the logs for more than 3 days, which it needs to address.
We also need some functionality inside the interface to re-push the same transaction again so that it will be helpful while testing and fixing the issue.
Also, some log errors are not giving the correct details. Oracle needs to rectify those.
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.
The nearest thing I have used to OIC is UiPath, as it is often used as a tool to integrate software together. However, it is much more suited to legacy software which have little to no API endpoints. If the infrastructure already exists I understand why people use RPA for integration, however for when API's are easily accessible and you're using Oracle tools, OIC is better.
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.
Created a solution for unique business integration with minimal processing times
Saves my team about 7 hours per week because of how it communicates with all the information. Because it communicates faster, and because there's a lot of information to communicate with, another solution might not work.
