Likelihood to Recommend It is really helpful for managing [the] scaling of systems with need and utilizing resources when needed. Also, DevOps support for deployment plans is quite useful when deploying applications. Monitoring systems with graphQL and utilizing them in APIs is quite helpful when used in Microservices systems to identify system capabilities and user utilization of applications.
Read full review 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.
Read full review Pros Graphically representation in GraphQL Scaling system DevOps management Read full review 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. Read full review Cons Quota enforcement can be simplified Caching mechanism for API with akamai can be improved Gateway configuration can be simplified as details are not much elaborate Read full review 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. Read full review Support Rating The team is proactive and takes the issue up for resolution, they follow continuous development and release.
Read full review Alternatives Considered Akamai [API Gateway] helps better in terms of representation of graphQL and its consumption in monitoring system making a package for deployment speed with monitoring and scaling application with all services and utilizing most of a system without much knowledge of other aspects. Also, [a] user-friendly system helps people to handle [the] system with necessary options
Read full review 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.
Read full review Return on Investment Decrease in time required for deployment and monitoring by significant amount causing less support resources needed Scaling applications on month-end at high usage time has reduced TAT time for issues and no of issues occurring Quota enforcement has allowed [managing] multiple systems and their needs in respective stakeholders hands and reduced infra teams involvement in [the] management of reoccurring problems Read full review 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. Read full review ScreenShots Oracle Integration (OIC) Screenshots