Create OIC Instance Guide

Introduction

Creating an Oracle Integration Cloud Instance is one of the first and most critical steps in building a modern integration landscape on Oracle Cloud. Whether you’re connecting Oracle Fusion HCM, ERP, SCM, or third-party systems, Oracle Integration Cloud (OIC) acts as the backbone for seamless integrations.

In real-world implementations, I’ve seen projects delayed simply because teams didn’t correctly provision or configure their OIC instance from the start. With the latest OIC Gen 3 architecture (as per Oracle Cloud 26A updates), provisioning has become more streamlined—but also more structured with dependencies on OCI components.

This blog will walk you through how to create an Oracle Integration Cloud Instance step-by-step, including architecture, prerequisites, real-world use cases, and consultant-level best practices.

What is Oracle Integration Cloud Instance?

An Oracle Integration Cloud Instance is a managed cloud service instance within Oracle Cloud Infrastructure (OCI) that enables:

• Application integrations (Fusion ↔ third-party)
• Process automation
• Visual integration flows
• REST/SOAP API exposure
• File-based integrations

Think of it as your central integration engine in Oracle Cloud.

In OIC Gen 3, the instance is tightly integrated with OCI services like:

• Identity and Access Management (IAM)
• Virtual Cloud Network (VCN)
• Logging & Monitoring
• API Gateway (optional)

Real-World Integration Use Cases

Let’s look at how Oracle Integration Cloud instances are used in actual projects:

1. Fusion HCM to Payroll Vendor Integration

• Employee data is extracted from HCM
• Transformed into vendor format
• Sent via SFTP/API to payroll provider

2. ERP Invoice Automation

• Supplier invoices uploaded via REST API
• Validated and pushed to Oracle Fusion ERP
• Status returned back to external system

3. SCM Order Integration with eCommerce

• Orders created in Shopify/Magento
• Synced to Oracle Fusion SCM
• Shipment updates pushed back to eCommerce

Architecture / Technical Flow

In OIC Gen 3, the architecture is simplified but more secure:

Flow Overview:

1. User creates OIC instance in OCI
2. Instance is linked with:
   • Compartment
   • VCN (optional but recommended)
   • IAM policies
3. Instance gets provisioned with:
   • Integration runtime
   • Process automation engine
   • Connectivity agents (optional)

Key Components:

Prerequisites

Before creating an Oracle Integration Cloud Instance, ensure the following:

1. OCI Account

You must have access to Oracle Cloud Infrastructure.

2. Compartment

Create or identify a compartment:

• Example: OIC_Integration_Compartment

3. IAM Permissions

Ensure policies like:

4. Network Setup (Optional but Recommended)

• Virtual Cloud Network (VCN)
• Subnets
• Internet Gateway / NAT Gateway

5. License / Subscription

Ensure your organization has OIC subscription enabled.

Step-by-Step Build Process

Now let’s go through the actual implementation steps as a consultant would do in a project.

Step 1 – Login to OCI Console

Navigate to:

👉 https://cloud.oracle.com

Login with your credentials.

Step 2 – Navigate to Integration Cloud

From the OCI dashboard:

Menu → Developer Services → Integration → Integration Instances

Step 3 – Create Integration Instance

Click:

👉 Create Integration Instance

Step 4 – Enter Basic Details

Fill the following fields:

Step 5 – Choose License Type

Options:

• Standard
• Enterprise

Consultant Tip:

• Use Enterprise if you need process automation + integrations
• Use Standard for basic integrations

Step 6 – Message Packs (Important)

Define message throughput:

Example:

• Dev → Small
• Prod → Medium/Large

Step 7 – Enable Optional Features

Depending on requirement:

• ✅ Process Automation
• ✅ Visual Builder (if needed)
• ❌ Skip if not required (to reduce cost)

Step 8 – Network Configuration

Choose:

• Public Endpoint (Quick setup)
• Private Endpoint (VCN) (Enterprise-grade security)

Real Project Recommendation: Always use Private Endpoint with VCN for production.

Step 9 – Tagging (Optional but Recommended)

Example:

• Environment: DEV
• Project: HCM_Integration

Step 10 – Create Instance

Click:

👉 Create

Provisioning time:

⏱️ ~20 to 40 minutes

Step 11 – Access the Instance

Once created:

• Click instance name
• Click Service Console

You’ll be redirected to:

👉 OIC Dashboard

Testing the Technical Component

After provisioning, validate your instance.

Test 1 – Login Check

• Access OIC dashboard
• Ensure no errors

Test 2 – Create Sample Integration

Create a basic REST integration:

• Trigger: REST Adapter
• Response: Static payload

Example response:

Test 3 – Activate Integration

• Activate the integration
• Invoke via Postman

Expected Result:

✅ HTTP 200 response
✅ Payload returned correctly

Common Errors and Troubleshooting

1. Instance Not Creating

Cause:

• Missing IAM permissions

Fix:

• Verify policies in OCI

2. Cannot Access OIC Console

Cause:

• Network restrictions

Fix:

• Check VCN / security rules

3. Message Pack Exhausted

Cause:

• High transaction volume

Fix:

• Upgrade message pack

4. Slow Performance

Cause:

• Under-provisioned instance

Fix:

• Increase capacity or scale

Best Practices (Consultant Insights)

1. Separate Environments

Always create:

• DEV
• TEST/UAT
• PROD

Never mix environments.

2. Naming Convention

Use standard naming:

Example:

• OIC_DEV_HCM
• OIC_PROD_FINANCE

3. Use Private Endpoints

• Avoid public exposure
• Secure integrations

4. Monitor Usage

Track:

• Message consumption
• Errors
• Latency

Use OCI Monitoring tools.

5. Enable Logging

Always enable:

• Activity logs
• Error tracking

6. Plan Capacity Early

In real projects, scaling later is painful.

Start with:

• Medium pack for UAT
• Large pack for production

Summary

Creating an Oracle Integration Cloud Instance is not just a technical step—it’s the foundation of your entire integration architecture.

From my implementation experience, the key success factors are:

• Proper planning of compartments and IAM
• Correct sizing of message packs
• Secure network configuration
• Clear environment separation

With OIC Gen 3 (26A), Oracle has simplified provisioning but added more enterprise-grade controls—making it even more important for consultants to understand the setup deeply.

FAQs

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

Typically 20–40 minutes, depending on configuration and region.

2. Can I change message pack after creation?

Yes, but it may require scaling and approval depending on subscription.

3. Is VCN mandatory for OIC?

No, but strongly recommended for production environments.

Additional Reference

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