OIC Export Import Guide

Share

Introduction

Oracle Integration Cloud Export Import is a critical capability used by consultants to migrate integrations, packages, and configurations across environments in Oracle Integration Cloud. In real-world projects, you rarely build everything directly in production—most work happens in DEV, moves to TEST, and finally to PROD. This is where export/import becomes essential.

From my experience in multiple enterprise implementations, improper handling of export/import is one of the top reasons for deployment failures. This guide walks you through how to use this feature effectively in OIC Gen 3 (aligned with Fusion 26A standards) with practical insights you won’t find in basic documentation.

What is Oracle Integration Cloud Export Import?

Oracle Integration Cloud Export/Import is a feature that allows you to:

  • Export integrations and packages from one OIC environment
  • Import them into another environment
  • Maintain consistency across lifecycle stages (DEV → TEST → PROD)

What Gets Exported?

When you export from OIC, you typically include:

  • Integrations (App Driven / Scheduled / Basic)
  • Packages
  • Lookup values
  • Libraries
  • Certificates (optional handling)
  • Connections (metadata only, not credentials)

Key Point from Real Projects

Export/Import is not just a technical activity—it’s part of your deployment strategy. Mature teams align this with CI/CD pipelines and release governance.

Key Features of OIC Export Import

1. Package-Based Deployment

Instead of exporting individual integrations, you can group them into packages.

2. Dependency Handling

OIC ensures dependent objects are included:

  • Lookups
  • Libraries
  • Child integrations

3. Version Management

Each export maintains version details, helping track releases.

4. Selective Import

You can choose what to import:

  • Overwrite existing integrations
  • Skip duplicates
  • Import selectively

5. Environment Isolation

Supports secure movement between:

  • DEV
  • TEST
  • PROD

Real-World Integration Use Cases

Use Case 1: DEV to TEST Migration

A retail client builds integrations in DEV:

  • Order creation from eCommerce → ERP
  • Inventory sync → SCM

Once tested internally, the team exports a package and imports it into TEST for UAT.

Use Case 2: Production Deployment

A banking client prepares a monthly release:

  • 10 integrations bundled into a package
  • Approved via governance

Export from TEST → Import into PROD with controlled deployment window.

Use Case 3: Backup and Rollback Strategy

In a healthcare project:

  • Before making changes, teams export current integrations
  • Store artifacts in Git repository

If issues arise → re-import previous version

Architecture / Technical Flow

Here’s how export/import works conceptually:

  1. Developer creates integrations in DEV
  2. Integrations grouped into packages
  3. Export generates .iar file (Integration Archive)
  4. File transferred to target environment
  5. Import process reads metadata and deploys artifacts
  6. Connections reconfigured manually (credentials)

Important Insight

Export files do NOT store passwords or secrets. This is a deliberate security design.

Prerequisites

Before performing export/import, ensure:

1. Access Requirements

  • OIC Administrator or Developer role

2. Environment Readiness

  • Target environment (TEST/PROD) must be active
  • Required connections must exist

3. Connection Alignment

  • Same connection names across environments
  • Endpoint URLs updated accordingly

4. Certificates

  • SSL certificates should be pre-configured in target environment

Step-by-Step Build Process

Step 1 – Create a Package

Navigation:

Navigator → Design → Packages

Steps:

  1. Click Create Package
  2. Enter:
    • Name: FIN_AR_INTEGRATIONS
    • Identifier: Auto-generated
  3. Add integrations:
    • Add Order Integration
    • Add Invoice Integration

Click Save

Step 2 – Add Integrations to Package

  1. Open the package
  2. Click Add Integration
  3. Select required integrations
  4. Ensure dependencies are included

💡 Tip: Always validate dependencies before export to avoid runtime failures.

Step 3 – Export the Package

Navigation:

Navigator → Design → Packages → Actions → Export

Steps:

  1. Select the package
  2. Click Export
  3. Download .iar file

Example file:

FIN_AR_INTEGRATIONS_1.0.iar

Step 4 – Transfer File to Target Environment

Options:

  • Manual upload
  • CI/CD pipeline (recommended for enterprise)

Step 5 – Import into Target Environment

Navigation:

Navigator → Design → Integrations → Import

Steps:

  1. Click Import
  2. Upload .iar file
  3. Choose options:
    • Overwrite existing: Yes/No
    • Import all dependencies

Click Import

Step 6 – Reconfigure Connections

After import:

  1. Navigate to Connections
  2. Update:
    • Username/password
    • Tokens
    • Endpoint URLs

💡 Real Tip: This is where most failures happen—never skip this step.

Step 7 – Activate Integrations

  1. Open imported integration
  2. Click Activate

Testing the Technical Component

Example Test Scenario

Integration: Create Invoice in ERP

Test Payload

{ “InvoiceNumber”: “INV1001”, “Amount”: 5000, “Customer”: “ABC Corp” }

Expected Results

  • Integration executes successfully
  • Invoice created in ERP system
  • Response status: SUCCESS

Validation Checks

  • Check OIC tracking instance
  • Validate ERP transaction
  • Confirm no faults in logs

Common Errors and Troubleshooting

1. Connection Not Found

Error: Connection reference missing

Solution:

  • Ensure same connection name exists in target environment

2. Activation Failure

Error: Missing credentials

Solution:

  • Re-enter credentials in connections

3. Lookup Missing

Error: Lookup not found

Solution:

  • Ensure lookup included in package

4. Version Conflict

Error: Integration already exists

Solution:

  • Use overwrite option carefully

5. Endpoint Mismatch

Error: API call fails post import

Solution:

  • Update endpoint URLs for environment

Best Practices

1. Always Use Packages

Never export individual integrations in large projects.

2. Maintain Naming Standards

Example:

DEV: ERP_CONN_DEV TEST: ERP_CONN_TEST

3. Use Version Control

Store .iar files in:

  • Git
  • Artifact repository

4. Automate Deployments

Use CI/CD tools:

  • Jenkins
  • OCI DevOps

5. Validate Before Import

Checklist:

  • Connections ready
  • Certificates configured
  • Dependencies verified

6. Separate Config from Logic

Avoid hardcoding:

  • URLs
  • Credentials

Use:

  • Lookups
  • Parameters

Real Consultant Insight

In one project, a team imported 25 integrations into PROD without validating connections. Result:

  • 18 integrations failed instantly
  • Production outage for 3 hours

After that, they implemented a pre-import checklist and reduced failures to zero.

Summary

Oracle Integration Cloud Export Import is not just a feature—it’s a core deployment mechanism in integration projects. When used correctly:

  • Ensures smooth environment migration
  • Reduces deployment errors
  • Supports scalable integration lifecycle

In OIC Gen 3, the process is streamlined, but still requires disciplined execution—especially around connections, dependencies, and testing.

For deeper reference, consult Oracle’s official documentation:
https://docs.oracle.com/en/cloud/saas/index.html

FAQs

1. Does export include connection passwords?

No. For security reasons, credentials are not exported. They must be reconfigured in the target environment.

2. Can we export a single integration without a package?

Yes, but it’s not recommended for enterprise projects. Packages ensure dependency management.

3. How do we automate export/import in OIC?

You can use REST APIs and integrate with CI/CD tools like Jenkins or OCI DevOps to automate deployments.


Share

Leave a Reply

Your email address will not be published. Required fields are marked *