Create Oracle OIC Instance

Introduction

Creating an Oracle Integration Cloud instance is the very first step in building enterprise-grade integrations across Oracle Fusion applications, third-party systems, and cloud platforms. Whether you’re integrating Oracle Fusion HCM with payroll systems, syncing ERP with external vendors, or building event-driven architectures, everything starts with properly provisioning an Oracle Integration Cloud (OIC Gen 3) instance.

In real-world projects, I’ve seen many consultants struggle not with integration logic—but with incorrect instance setup, wrong edition selection, or missing prerequisites. These early mistakes lead to rework, delays, and sometimes even production instability.

This guide explains how to create an Oracle Integration Cloud instance step-by-step, aligned with the latest Oracle Cloud 26A standards, using OIC Gen 3 architecture.

What is Oracle Integration Cloud Instance?

An Oracle Integration Cloud instance is a fully managed PaaS service in Oracle Cloud Infrastructure (OCI) that enables you to:

• Build integrations between cloud and on-premise systems
• Automate workflows
• Expose APIs
• Process files and events
• Monitor integrations centrally

Think of it as your central integration hub inside OCI.

Each instance includes:

Real-World Integration Use Cases

1. HCM to Payroll Integration

A client uses Oracle Fusion HCM but processes payroll in a third-party system like ADP.

• OIC extracts employee data using REST APIs
• Transforms data into payroll format
• Sends to external system via SFTP or API

2. ERP Invoice Automation

Invoices are received in CSV format from vendors.

• OIC reads files from Object Storage
• Maps to ERP invoice format
• Loads into Oracle Fusion ERP using FBDI

3. SCM Order Synchronization

Orders created in eCommerce systems need to sync with Oracle SCM.

• OIC exposes REST APIs
• Accepts order payloads
• Creates orders in Fusion SCM

Architecture / Technical Flow

Before creating the instance, understand where OIC fits in OCI.

High-Level Flow

1. OCI Tenancy (your cloud account)
2. Compartment (logical grouping of resources)
3. OIC Instance (created inside compartment)
4. Integrations deployed inside OIC
5. Connectivity to:
   • Oracle Fusion Apps
   • External APIs
   • On-premise via connectivity agent

Key Components in OIC Gen 3

• Service Instance → Your OIC environment
• Integration Designer → Build integrations
• Connections → Define endpoints
• Lookups → Value mapping
• Packages → Group integrations

Prerequisites

Before creating an OIC instance, ensure the following:

1. OCI Tenancy Access

You must have access to Oracle Cloud Infrastructure.

2. Required Permissions

Ensure your user has:

• Service Administrator role
• Compartment access
• Policy to manage integration instances

Example policy:

3. Compartment Creation

Create a compartment where OIC will reside.

4. Virtual Cloud Network (VCN)

Required for private endpoints or secure connectivity.

5. Subscription / License

You must have OIC subscription enabled.

Step-by-Step: Create Oracle Integration Cloud Instance

Step 1 – Login to OCI Console

Navigate to:

👉 https://cloud.oracle.com

Enter credentials and access OCI dashboard.

Step 2 – Navigate to Integration Cloud Service

Path:

Menu → Developer Services → Integration

This opens the OIC dashboard.

Step 3 – Click “Create Integration Instance”

Click:

👉 Create Instance

Step 4 – Provide Basic Details

Fill in the following fields carefully:

Edition Selection (Important)

👉 Consultant Tip: Always choose Enterprise Edition for real projects.

Step 5 – Configure Shape (OIC Gen 3)

OIC Gen 3 uses flexible shapes.

Options include:

• Small
• Medium
• Large

Recommendation:

Step 6 – Configure Network (Optional but Important)

Choose:

• Public endpoint → Quick setup
• Private endpoint → Secure enterprise setup

👉 Real projects typically use private endpoints.

Step 7 – License Type

Select:

• License Included
  OR
• Bring Your Own License (BYOL)

Step 8 – Enable Optional Features

You may enable:

• Visual Builder
• File Server
• Process Automation

👉 Enable only what is required to avoid cost overhead.

Step 9 – Review and Create

Click:

👉 Create

Provisioning takes:

⏱️ 20–40 minutes

Post-Creation Validation

Once the instance is created:

Step 1 – Open Instance

Click on instance name → Launch Integration.

Step 2 – Verify Dashboard

Check:

• Integration Designer
• Connections
• Monitoring

Step 3 – Create First Connection

Test with:

• Oracle HCM Adapter
• REST Adapter

Step 4 – Test Basic Integration

Create:

• Simple REST trigger
• Response payload

Testing the Technical Setup

Sample Test Scenario

Create a simple REST integration:

Request Payload

Expected Response

Validation Checklist

• Integration activated successfully
• No runtime errors
• Monitoring shows successful instance

Common Errors and Troubleshooting

1. Permission Issues

Error: Cannot create instance
Cause: Missing IAM policy
Fix: Add correct policies

2. Instance Stuck in Provisioning

Cause: Network misconfiguration
Fix: Validate VCN and subnet

3. Cannot Access Integration URL

Cause: Security rules or firewall
Fix: Open required ports

4. Wrong Edition Selection

Impact: Missing features like B2B
Fix: Recreate instance (cannot change later)

Best Practices from Real Projects

1. Use Separate Environments

Always maintain:

• DEV
• TEST
• PROD

2. Naming Standards

Use structured naming:

3. Enable Logging Early

Helps in troubleshooting integrations.

4. Use Compartments Properly

Separate resources by:

• Project
• Environment

5. Plan Scaling

Start small, scale based on:

• Integration load
• Transaction volume

6. Secure Connectivity

Use:

• Private endpoints
• Connectivity agent

Real Consultant Insight

In one implementation, a client created OIC in the wrong compartment without proper policies. This led to:

• Delayed access
• Integration failures
• Security issues

We had to recreate the instance, which delayed the project by 2 weeks.

👉 Lesson: Spend time planning your OIC setup—it saves weeks later.

Summary

Creating an Oracle Integration Cloud instance is not just a technical step—it’s a foundational decision that impacts your entire integration landscape.

Key takeaways:

• Choose the right edition (Enterprise recommended)
• Configure compartments and policies correctly
• Use OIC Gen 3 flexible shapes
• Plan environments properly
• Validate setup with test integrations

A properly configured OIC instance ensures:

• Scalable integrations
• Secure architecture
• Faster development lifecycle

FAQs

1. Can we change OIC edition after creation?

No. Once created, the edition cannot be changed. You must recreate the instance.

2. What is the difference between Gen 2 and Gen 3 OIC?

Gen 3 provides:

• Better scalability
• Flexible shapes
• Improved performance
• Native OCI integration

3. How long does it take to create an OIC instance?

Typically 20–40 minutes, depending on configuration.

For more official details, refer to Oracle documentation:
https://docs.oracle.com/en/cloud/saas/index.html