Oracle Integration has recently introduced new functionalities to extend its connection capabilities.
I’m especially talking about the enhanced Oracle Policy Automation adapter which is often used in integration projects when it’s required to extend SaaS applications.
The Oracle Policy Automation (OPA) adapter is available in Oracle Integration to address different scenarios allowing to OPA decisions to be invoked at any point of the integration flows. For example, when a Service Cloud Incident is created for a medical device manufacturer (for instance a hearing aid), an integration instance can be triggered by OPA used to find out what to do with this particular type of incident and routing properly the managed information. The integration layer (in this case OIC) performs all necessary actions saving the decision somewhere, invoking other processes / web services or pushing data to multiple applications Cloud and / or on-premise.
By using Oracle Integration we can easily integrate the OPA decisions logic into any enterprise application without the need to build a custom connector. There are some use cases where OPA is used in an integration scenario:
The Oracle Integration adapter today enables bidirectional communications allowing inbound and outbound communication patterns.
An Oracle Policy Automation (OPA) adapter is now available in Oracle Integration (OIC) to:
After accessing your Oracle Integration instance, you can select the OPA adapter available from the palette
therefore, you can configure that one with the role type required from your project (invoke, trigger or both).
Once the connection is created, you can reuse that one in every integration flow