OIC Training
OIC Training
1
Copyright © Abjayon. All rights reserved. | Confidential
Cloud Computing
2
Copyright © Abjayon. All rights reserved. | Confidential
Integration Challenges
3
Copyright © Abjayon. All rights reserved. | Confidential
SOA VS OIC
SOA OIC
Typically deployed on-premises, offering complete control Cloud-based, allowing for more effortless scalability and
over infrastructure but requiring hardware and maintenance. reduced infrastructure management.
Designed for citizen integrators and business users,
More complex and requires experienced integration offering a more user-friendly interface for designing and
developers to design and implement integrations. deploying integrations.
Provides a wide range of adapters for connecting to various Offers pre-built adapters to connect to popular cloud
systems, both on-premises and in the cloud. applications and services.
Scalability is determined by the on-premises hardware and Offers the scalability benefits of the cloud, with
infrastructure. resources dynamically allocated based on demand.
Supports various integration styles, including synchronous
and asynchronous messaging, orchestration, and Emphasizes simplified integrations, often utilizing RESTful
choreography. APIs and lightweight integrations.
Licensing costs and hardware requirements can be significant Subscription-based pricing model, potentially offering
for on-premises deployments. more cost-effective options for smaller organizations.
4
Oracle Cloud Integration
5
OIC Subscription Models
6
OIC Role
OIC Role Description
ServiceAdministr A user with the ServiceAdministrator role is a super user who can manage and
ator administer the features provisioned in an Oracle Integration instance.
ServiceDeveloper A user with the ServiceDeveloper role can develop the artifacts specific to the
features provisioned in an Oracle Integration instance.
ServiceMonitor A user with the Service Monitor role can monitor the features provisioned in
an Oracle Integration instance.
ServiceDeployer A user with the Service Deployer role can publish the artifacts developed in a
feature.
ServiceUser A user with the ServiceUser role has privileges to utilize only the basic
functionality of a feature such as access to the staged and published
applications.
ServiceInvoker •A user with the ServiceInvoker role can invoke any integration flow in
an Oracle Integration instance that is exposed through SOAP/REST APIs or a
scheduled integration.
ServiceViewer A user with the ServiceViewer role can navigate to all Integration resource pages
and view details. The user cannot edit any resources or navigate to the
administrative setting pages.
7
OIC Pros
•Lightweight & Simple Integrations
Ideal for straightforward integrations without complex requirements.
•Wide Range of Adapters & Connectors
Pre-built adapters for seamless integration with applications, databases, and services.
•Pre-built Integration Flows & Templates
Library of reusable components like flows, templates, and recipes to speed up development
and reduce time-to-market.
•Built-in Monitoring & Analytics
Real-time insights into performance, error rates, and system latency for proactive optimization
and troubleshooting.
•Enterprise-Grade Security
Protects sensitive data with encryption, identity management, access controls, and audit trails,
ensuring compliance with regulatory standards.
8
OIC: Application Integration
9
INTEGRATION TYPES
• Application
• Schedule
• Event
10
Integration Pattern Described
Pattern Description
Application Create an application integration (previously known as app-driven orchestration) that uses an event or a business object to
trigger the integration. For example, you create an integration with an Oracle Service Cloud (RightNow) Adapter as a trigger and
an Oracle CX Sales and B2B Service Adapter as an invoke. The Oracle Service Cloud (RightNow) Adapter subscribes to an event
from the Oracle CX Sales and B2B Service application to trigger the integration. Application integrations include many actions
for performing specific tasks, such as the following:
•Switch actions to create multiple routing expressions.
•For-each actions for looping over repeating elements.
•Assign actions for assigning values to scalar variables.
•Ad-hoc mappings on switch actions branches.
•Callback actions (to end a process and respond back to the sender) and end actions (to end a process without responding back
to the sender) in asynchronous integrations.
Schedule Create an integration that uses a schedule to trigger the integration instead of an adapter. For example, you add an initial
invoke adapter to read a trigger file and a second FTP adapter to download the file for further processing. After designing this
integration, you schedule when to run it.
Event Create and select events for publishing and subscribing to in integrations. You define the events in JSON-formatted files.
Note: If you created integrations using the Publish to OIC and Subscribe to OIC integration patterns (often called pub/sub) in
Oracle Integration Generation 2, these capabilities and more are available in Oracle Integration 3. To create an integration that
publishes an event, create an application integration. To create an integration that subscribes to published events, create an
event integration.
11
Integration Development and Management Workflow
12
Integration Concepts
• Trigger
• Invoke
13
• Mapping: Most integrations include one or more mappings, which
specify the source and destination of the data that the integration
moves
14
• Lookups: A lookup associates the value that an application uses for
an item with the value used by other applications for the same
item. A lookup is a table, and it can define one or more terms or
values for two or more applications.
15
• Packages: A package is a structure in which you can group one or
more integrations. Packages let you easily import and export a
group of integrations in Oracle Integration.
16
• Business Identifiers for Tracking Fields in Messages
17
• Actions
Assign: Enables us to assign variables in Integrations.
Function Call: Enables us to call JavaScript functions in Integrations.
Logger: Enables us to put the logger in between of the integration to print some variables values
in logs.
Map: Allows us to add some ad-hoc maps in Integrations.
Notification: Allows us to enable email notification in Integrations.
Scope: Enables you to manage a collection of child actions and invokes that can have their own
fault handlers.
Stage File: Enables us to read/writes files in scheduled integration at some temporary location
in ICS.
Switch: Enable us to add switch activity for defining routing expression branches in Integrations.
For Each: Enables you to loop over a repeating element and execute one or more actions within
the scope of the for-each action. This blog shows, how to use For Each action.
While: Enables you to loop over actions or invoke connections as long as a specific condition is
met.
Raise Error: Enables you to send failed messages to the error hospital for further analysis.
Fault Return: Enables you to return a faut
18
Demo
19
Object Storage
20
Error Management
• https://notetoself.dev/2021/07/15/oic-exception-handling-and-notifications-a-summary/
21
Accelerator
22
Installation Steps for Accelerator
23
How to Configure Accelerator Resources
• Accelerators and recipes come inside a package. Whenever you install an Oracle
accelerator or a recipe, the next step is configuring all dependent resources inside this
package for integrations.
• Dependent resources include connections, lookups, libraries, and certificates (PGP
keys).
• Connections, certificates, lookups and libraries are easily editable. But you must have
administrator privileges to edit certificates.
• You also have the privilege to replace connections and certificates in some packages.
But you cannot replace them under the following cases:
• If integration inside the package is active or locked.
• If connections and certificates are included in a business or technical accelerator.
• You have the privilege to update integration property values for any integration where
properties are defined.
24
Hybrid Integration
Hybrid integration enables you to have flows hosted on Oracle Integration that:
• Access SOAP/REST endpoints exposed by applications such as Oracle E-Business Suite, Siebel, and JD Edwards,
and any on-premises home grown SOAP/REST APIs
• Access non-HTTP-based endpoints such as databases, JMS, AQ, local file systems, SAP, and others
These capabilities enable you to implement use cases such as the following:
• Send requests from a cloud application (for example, send a create service order request from an Oracle Service
Cloud application) to an on-premises E-Business Suite application
• Synchronize bulk data extracts of a product from a product data hub in Oracle ERP Cloud with an on-premises
Oracle database or an Oracle Database Cloud Service instance
• Synchronize customers that are added/updated in an on-premises SAP application with SaaS applications such as
Oracle CX Sales and B2B Service Adapter, Oracle CPQ, Oracle Service Cloud, and Salesforce.com
Oracle Integration provides a component called the connectivity agent to facilitate hybrid integrations
25
Manage the Agent Group and the On-Premises Connectivity Agent
• Connectivity Agent Overview: Facilitates hybrid integrations between Oracle Integration and on-
premises/private network applications. Extends Oracle Integration's reach beyond internet-
accessible systems.
• Features: Multithreading support for efficient message processing. Secure message exchange
between diverse environments.
• Setup Requirements: Create agent group in Oracle Integration. Then install on-premises
connectivity agent.
• Integration Capabilities: Integrates on-premises applications with Oracle services and Supports
private cloud communication.
• Benefits: Flexibility in integrating diverse IT environments and maintains security and data
residency compliance.
• Use Cases: Legacy system integration and Real-time data exchange between cloud and on-
premises.
26
Security in OIC DEMO(Emicool)
• OAUTH 2.0
• Create a Client application and use the Oracle
provided Server application of your OIC instance
and then assign the client application to the user
in Server application along with the appropriate
user role. Have covered in detail in document.
• API Gateway
• The API Gateway service enables you to publish
APIs with private endpoints that are accessible
from within your network, and which you can
expose with public IP addresses if you want them
to accept internet traffic
27
Sample OIC Integrations
• Emi-cool
• Bank Integration
• SCM Integration
• Email Notification
• Update Lookup
• PRPA
• ERP Integrations
• OFSC Integrations
• Connects Oracle Utilities application suite with Oracle ERP and Oracle Field
Service.
• Oracle Utilities can initiate or be invoked via web services through Oracle
Integration.
• Both inbound and outbound services are exposed using the Oracle Utilities
service catalog.
• Integrates with on-prem Oracle Utilities applications via the connectivity agent.
• Handles synchronous request/response and one-way request patterns for SOAP
and REST endpoints.
29
Configuring the connection for ccs / mscs / wacs using oracle utility
adapters(other side configuration for adapter )
SOAP Example:
https://us-phoenix-1.stg.utilities-cloud.oracleindustry.com/c863f1/test/wac/soap/api/iws/Serv
iceCatalog?wsdl
30
OIC Integration Migration
1. Single Integration Migration : You just need to Export the Integration from current Instance and
Import it to new OIC Instance
2. Multiple Integration Migration : Now suppose you want to migrate multiple integration in
single go then you can achieve it by Package Migration. You can group integrations into a
package. When you import or export the package to or from Oracle Integration Instance, all
integrations in that package are imported or exported.
Steps in Doc.
31
THANK YOU
32
Copyright © Abjayon. All rights reserved. | Confidential