Integration Styles in OIC Gen 3

Introduction

Integration Styles in OIC Gen 3 are fundamental to designing scalable and reliable integrations between enterprise applications. Modern organizations use multiple systems such as Oracle Fusion ERP, HCM, SCM, CRM platforms, and third-party SaaS applications. These systems must exchange data seamlessly, and Oracle Integration Cloud Generation 3 (OIC Gen 3) provides multiple integration patterns to support this requirement.

In real enterprise implementations, integrations do not always behave the same way. Some integrations must run in real time using APIs, while others run on schedules for batch processing, and some are triggered automatically by business events generated by applications.

For example:

• When a new employee is created in a third-party HR system, the integration must immediately create the employee in Oracle Fusion HCM.

• Retail systems may upload invoice files nightly that need to be processed in Oracle Fusion ERP.

• A supplier update in Oracle Fusion Procurement may trigger notifications to downstream procurement systems.

These different scenarios require different integration styles in OIC Gen 3.

In this article, we will explore:

• What integration styles are in OIC Gen 3

• When to use each integration pattern

• Real-world enterprise integration scenarios

• Architecture patterns used in Oracle projects

• Step-by-step creation of integrations

• Best practices used by experienced Oracle consultants

What Are Integration Styles in OIC Gen 3?

In Oracle Integration Cloud Generation 3, an integration style defines how an integration is triggered and how messages flow between source and target systems.

When developers create a new integration in OIC, the first step is selecting the integration style. This determines several aspects of the integration:

• How the integration is triggered

• Whether the integration runs synchronously or asynchronously

• Whether the integration processes real-time messages or batch data

• How orchestration logic is handled within the integration

Major Integration Styles in OIC Gen 3

Selecting the correct integration style is an important design decision that impacts performance, scalability, and maintainability.

Real-World Integration Use Cases

In enterprise Oracle implementations, integration styles are selected based on business processes and data patterns.

Use Case 1 — Employee Creation from External HR System

Many organizations maintain employee records in external HR systems but require employees to be synchronized with Oracle Fusion HCM.

Integration Flow:

1. HR system sends employee information through a REST API.

2. Oracle Integration Cloud receives the request.

3. Integration logic transforms the incoming data.

4. Oracle Fusion HCM REST API creates the employee record.

Integration Style Used:

App Driven Orchestration

Use Case 2 — Nightly Invoice Import

Retail companies often generate invoices from multiple store systems that must be imported into Oracle Fusion ERP.

Integration Flow:

1. Stores upload invoice files to an integration server.

2. A scheduled integration runs every night.

3. Invoice data is validated and transformed.

4. Oracle Fusion ERP invoice import process is triggered.

Integration Style Used:

Scheduled Orchestration

Use Case 3 — Supplier Update Notifications

When a supplier record changes in Oracle Fusion Procurement, other systems may need to be notified automatically.

Integration Flow:

1. Oracle Fusion emits a business event.

2. Oracle Integration Cloud receives the event.

3. Integration sends updates to external procurement platforms.

Integration Style Used:

Event Driven Integration

Architecture of Integrations in OIC Gen 3

Oracle Integration Cloud Gen 3 provides a scalable architecture that allows organizations to integrate cloud and on-premise applications.

Key Components of OIC Gen 3

Typical Integration Flow

A standard integration architecture typically follows this flow:

Source System → Adapter → Integration Flow → Data Mapping → Target System

Example:

Salesforce → REST Adapter → OIC Gen 3 → Transformation → Oracle Fusion ERP

This architecture allows organizations to build secure and scalable integration frameworks.

App Driven Orchestration in OIC Gen 3

App Driven Orchestration is the most widely used integration style in Oracle Integration Cloud.

In this pattern, integrations are triggered by external systems through REST or SOAP APIs.

How App Driven Integrations Work

1. An external application sends a request to OIC using REST or SOAP.

2. OIC receives the request through an adapter.

3. Integration logic processes the request.

4. Data transformation occurs using the mapper.

5. The target system API is invoked.

Key Characteristics

• Supports real-time processing

• Works with REST and SOAP APIs

• Supports synchronous and asynchronous communication

• Allows complex orchestration logic

Example Use Cases

• Creating employees in Oracle Fusion HCM

• Creating invoices in Oracle Fusion ERP

• Processing orders in Oracle Fusion SCM

• Synchronizing customer data between CRM and ERP systems

Scheduled Orchestration in OIC Gen 3

Scheduled Orchestration integrations run automatically at predefined time intervals.

These integrations are commonly used for batch processing scenarios.

Typical Batch Integration Scenarios

• Payroll file processing

• Daily financial data synchronization

• File-based integrations

• Data migration tasks

Example Scenario

A payroll application generates employee salary files every night.

A scheduled integration runs at 1 AM to process the payroll file and update employee records in Oracle Fusion HCM.

Scheduling Options

Scheduled integrations are particularly useful when large volumes of data must be processed periodically.

Basic Routing Integration

Basic Routing integrations are designed for simple message routing scenarios.

In this pattern:

1. A request is received from a source system.

2. Oracle Integration Cloud routes the message directly to the target system.

3. Minimal transformation or orchestration occurs.

Advantages of Basic Routing

• Faster development

• Simpler integration design

• Minimal configuration

Example Scenario

A CRM system sends customer data that must be forwarded directly to an ERP system without additional processing.

Basic Routing integrations are ideal when the integration logic is simple and does not require complex workflows.

Event Driven Integration in OIC Gen 3

Event-driven integrations respond automatically when business events occur in applications.

Oracle Fusion applications generate events such as:

• Employee created

• Supplier updated

• Invoice approved

• Purchase order created

Oracle Integration Cloud can subscribe to these events and trigger integrations automatically.

Example Event-Driven Scenario

When a new employee is created in Oracle Fusion HCM:

1. Oracle Fusion emits an event.

2. OIC receives the event notification.

3. Integration triggers downstream processes.

4. Identity management systems create user accounts.

Event-driven architectures enable organizations to build reactive systems that respond immediately to business changes.

Prerequisites for Building Integrations in OIC Gen 3

Before building integrations, ensure the following prerequisites are available.

Step-by-Step: Creating an App Driven Integration

Step 1 – Navigate to Integration Console

Navigator → Integrations → Create Integration

Select App Driven Orchestration.

Step 2 – Define Integration Details

Enter the following details:

Click Create.

Step 3 – Configure REST Trigger

Add a REST Adapter as the trigger.

Define the request payload structure.

Example request payload:

Step 4 – Add Business Logic

Inside the integration canvas:

• Add mapping logic

• Perform payload transformation

• Implement conditional routing if required

Example: Map employee fields to Oracle Fusion HCM REST API attributes.

Step 5 – Configure Target Connection

Add the Oracle HCM Adapter.

Example endpoint:

Provide authentication credentials.

Step 6 – Map Fields

Step 7 – Activate Integration

Click:

Actions → Activate

After activation, the integration endpoint becomes available.

Testing the Integration

Testing ensures integrations behave correctly before production deployment.

Example Test Payload

Expected Result

• Employee record created in Oracle Fusion HCM

• Integration instance status shows Succeeded

Validation Steps

1. Monitor the integration instance.

2. Verify API response.

3. Confirm employee record in HCM.

Common Implementation Challenges

Authentication Errors

Cause: Incorrect credentials configured in adapters.

Solution: Verify authentication policies and credentials.

Mapping Errors

Cause: Incorrect data mapping between source and target systems.

Solution: Validate mapper configuration and data types.

Timeout Errors

Cause: Slow response from external APIs.

Solution:

• Increase timeout configuration

• Optimize integration logic

Best Practices for Designing Integrations

Experienced Oracle consultants follow these best practices.

Choose the Correct Integration Style

• Use App Driven integrations for real-time APIs

• Use Scheduled integrations for batch processing

Build Modular Integrations

Break large integrations into smaller reusable components.

Implement Error Handling

Use:

• Scope activities

• Fault handlers

• Notification mechanisms

Monitor Integration Performance

Use OIC monitoring features to track:

• Failed integrations

• Processing time

• Integration throughput

Summary

Understanding Integration Styles in OIC Gen 3 is essential for designing scalable integrations between enterprise applications.

Different integration patterns support different integration scenarios:

• App Driven Orchestration for real-time API integrations

• Scheduled Orchestration for batch data processing

• Basic Routing for lightweight message routing

• Event Driven Integrations for reactive architectures

Choosing the correct integration style ensures integrations are reliable, maintainable, and scalable.

For deeper technical documentation and architectural guidance, refer to the official Oracle documentation:

https://docs.oracle.com/en/cloud/paas/integration-cloud/index.html

Frequently Asked Questions

What is the most commonly used integration style in OIC Gen 3?

App Driven Orchestration is the most commonly used integration pattern because it supports real-time API integrations.

When should Scheduled Orchestration be used?

Scheduled integrations should be used when data must be processed periodically, such as nightly batch jobs or file-based integrations.

Can multiple integration styles be used in one implementation?

Yes. Large enterprise implementations often use multiple integration styles depending on whether integrations are real-time, batch-based, or event-driven.