Summary of "2. Components in OIC | Agent, Adapters, Connections, Lookup, Package, Library and Integration"

Overview

This video explains core OIC (Oracle Integration Cloud) components in depth, focusing on what each one does and how they work together to build integrations.

Adapters

Adapters are endpoints for integration solutions that enable direct interaction with business applications.
They perform the actual connection, handle application resources, and manage transactions securely, including secure exception/transaction handling.
They support secure configuration of connections using authentication such as username/password and other credentials.
Examples mentioned:
- Oracle Cloud ERP adapters
- ATP (Oracle Autonomous Transaction Processing) adapter
- FTP file adapter
- Oracle Business Suite adapter
- REST adapter
- SOAP adapter
- Oracle Database adapter
Oracle provides many adapter types (example given: 77 adapters).

Agent

Agents connect OIC to on-premise applications and are used specifically for cloud-to-local system integrations.
They bridge access to on-prem sources such as local databases or local file servers.
Example on-premise systems referenced: EBS, SFP (as stated in subtitles).
Purpose: the agent helps create connectivity between on-premise apps and Oracle Cloud.

Connections

Connections define how OIC communicates with external systems.
Communication may be via file/FTP and other protocols, as well as social media and other services (examples listed: LinkedIn, Facebook, Twitter, Gmail, WhatsApp).
A connection is created using an adapter, and configuration includes:
- credentials (username/password)
- URL/host/port (as applicable)

Lookups

Lookups provide mapping and reusable integration logic.
They create a single reusable mapping table for terms that are represented differently across applications, enabling consistent translation throughout the integration.
Examples:
- Country code ↔ country name
- Gender values such as M ↔ Male and F ↔ Female

Libraries

Libraries store reusable functions/scripts and related logic.
Used for operations such as validation or other reusable processing steps.
Functions are configured in library editors and used in the orchestration canvas.
Mentioned capability: export/import metadata.

Packages

Packages group related integrations.
Useful for moving integrations between environments:
- Export multiple related integrations together
- Import them as a set into another environment (e.g., dev → prod)
Example scenario: exporting five integrations in one package rather than one-by-one.

Integration (main application/process)

The video positions Integrations as the business process applications that use connections and other components to automate business requirements.
Essentially: integrations implement the end-to-end workflow.