Introduction
Adapters in Oracle Integration Cloud (OIC Gen 3) are the backbone of any integration. If you have worked on real-time or batch integrations across Oracle Fusion applications, third-party systems, or legacy applications, you already know that adapters in Oracle Integration Cloud eliminate the complexity of handling protocols, security, and connectivity.
In real-world projects, 70–80% of integration effort revolves around connecting systems—REST APIs, SOAP services, FTP servers, databases, or SaaS applications. Adapters simplify this by acting as prebuilt connectors that handle communication, transformation triggers, and connectivity seamlessly.
This article explains adapters in Oracle Integration Cloud from a consultant’s implementation perspective, including architecture, use cases, configuration steps, and troubleshooting.
What are Adapters in Oracle Integration Cloud?
Adapters in Oracle Integration Cloud are prebuilt, reusable connectivity components that allow integrations to communicate with external systems without writing low-level code.
Instead of manually handling:
- HTTP calls
- Security tokens
- Payload formatting
- Protocol handling
OIC adapters encapsulate all of this into a configuration-driven interface.
Key Understanding
Think of adapters as:
- Triggers (Inbound Adapters) → Start an integration
- Invokes (Outbound Adapters) → Call external systems
Key Features of OIC Adapters
1. Prebuilt Connectivity
Adapters support multiple systems:
- SaaS (ERP, HCM, SCM)
- On-premise apps
- Databases
- File systems
2. Protocol Abstraction
No need to handle:
- REST headers
- SOAP envelopes
- FTP commands
3. Security Handling
Adapters manage:
- OAuth 2.0
- Basic Auth
- API Keys
- Certificates
4. Metadata-Driven Integration
Adapters auto-generate:
- Request/response schemas
- WSDL or Swagger-based structures
5. Connectivity Agent Support
For on-premise systems, adapters work with:
- Connectivity Agent (OIC Gen 3)
Types of Adapters in Oracle Integration Cloud
1. REST Adapter
Used for:
- Calling external REST APIs
- Creating REST endpoints
Example: Integrating Oracle Fusion HCM with a third-party payroll system.
2. SOAP Adapter
Used for:
- SOAP-based web services
- Legacy enterprise systems
Example: Calling Fusion Financials invoice services.
3. FTP Adapter
Used for:
- File-based integrations
- Batch data processing
Example: Loading payroll files into Oracle HCM.
4. Database Adapter
Used for:
- Reading/writing to databases
- Calling stored procedures
Example: Syncing data from an on-prem Oracle DB.
5. ERP / HCM / SCM Cloud Adapters
Used for:
- Direct integration with Fusion apps
Example:
- Create employee in HCM
- Create invoice in ERP
6. File Server Adapter (Gen 3 Enhancement)
Used for:
- Cloud-native file storage integration
Real-World Integration Use Cases
Use Case 1: Employee Data Sync (HCM → Payroll)
- Trigger: HCM Cloud Adapter
- Invoke: REST Adapter
- Flow:
- Employee created → OIC triggered
- Data transformed
- Sent to external payroll
Use Case 2: Invoice Import (FTP → ERP)
- Trigger: FTP Adapter
- Invoke: ERP Adapter
Scenario: Daily invoice files uploaded via SFTP are processed and imported into ERP.
Use Case 3: Order Integration (E-Commerce → SCM)
- Trigger: REST Adapter
- Invoke: SCM Adapter
Scenario: Online orders are pushed into Oracle SCM for fulfillment.
Architecture / Technical Flow
Flow Explanation
- Adapter acts as trigger
- Integration processes data
- Data mapped using mapper
- Adapter invokes target system
- Response handled
Prerequisites
Before working with adapters:
1. Access to OIC Instance
- Active Gen 3 environment
2. Required Credentials
- API credentials
- FTP details
- Database access
3. Connectivity Agent (if on-prem)
- Installed and configured
4. Endpoint Details
- REST URL / WSDL / Host
Step-by-Step Build Process
Let’s build a REST to ERP integration.
Step 1 – Create Connection
Navigation: Home → Integrations → Connections → Create
Select Adapter: REST Adapter
Provide Details:
- Name:
REST_EMPLOYEE_API - Role: Trigger or Invoke
- Base URL: API endpoint
Security:
- OAuth / Basic Auth
Step 2 – Configure Connection
- Test connection
- Upload certificates if required
Step 3 – Create Integration
Navigation: Home → Integrations → Integrations → Create
Select:
- App Driven Orchestration
Step 4 – Add Trigger Adapter
- Select REST connection
- Configure:
- Resource URI
- Methods (POST/GET)
Step 5 – Add Invoke Adapter
- Select ERP Adapter
- Choose business object
- Configure operation
Step 6 – Data Mapping
- Map:
- Source payload → Target payload
- Use:
- Mapper
- Functions
Step 7 – Activate Integration
- Validate
- Activate
- Get endpoint URL
Testing the Technical Component
Test Scenario
Input Payload (REST):
Expected Flow
- REST call triggers integration
- Data mapped to ERP structure
- Employee created in ERP
Validation
- Check instance tracking
- Verify response payload
- Confirm record in target system
Common Errors and Troubleshooting
1. Connection Test Failure
Cause:
- Wrong credentials
Solution:
- Revalidate authentication
2. 401 Unauthorized
Cause:
- OAuth misconfiguration
3. Schema Mismatch
Cause:
- Incorrect mapping
4. FTP Polling Issues
Cause:
- File naming mismatch
5. Timeout Errors
Cause:
- Network latency
Best Practices
1. Use Reusable Connections
Avoid creating duplicate connections.
2. Naming Conventions
Example:
REST_HCM_EMPLOYEE_TRIGGER
3. Secure Credentials
Use:
- Vault
- Secure properties
4. Handle Errors Gracefully
- Use scope + fault handler
5. Use Lookup Tables
Avoid hardcoding values.
6. Enable Tracking Fields
For monitoring and debugging.
Real Consultant Tips
- Always test adapter separately before full integration
- Maintain separate connections for DEV, TEST, PROD
- Use structured logging for debugging
- Prefer REST over SOAP when possible
- Use FTP adapter scheduling carefully to avoid duplicates
Summary
Adapters in Oracle Integration Cloud are essential for building scalable, secure, and efficient integrations. They eliminate complexity by providing prebuilt connectivity for various systems and protocols.
From REST APIs to ERP integrations, adapters enable consultants to focus more on business logic rather than connectivity challenges.
Mastering adapters is one of the most critical skills for any OIC consultant working on real-time and batch integrations.
For more details, refer to Oracle official documentation:
https://docs.oracle.com/en/cloud/saas/index.html
FAQs
1. What is the difference between trigger and invoke adapters?
Trigger adapters start an integration, while invoke adapters call external systems.
2. Which adapter is most commonly used in OIC?
REST Adapter is the most widely used due to modern API-based integrations.
3. Can we connect to on-prem systems using adapters?
Yes, using Connectivity Agent in OIC Gen 3.