Introduction

In enterprise cloud integration projects, developers frequently need to reuse existing integrations with minor modifications. Instead of creating integrations from scratch every time, Cloning of Integrations in Oracle Integration Cloud (OIC) provides a fast and reliable way to replicate an existing integration and modify it for a new requirement.

In Oracle Integration Cloud Gen 3, cloning integrations has become an essential productivity feature used by implementation consultants to accelerate development, maintain consistency, and reduce configuration errors. When organizations implement Oracle Fusion applications such as HCM, ERP, or SCM, integrations often share similar patterns. For example, multiple integrations might process employee data, supplier data, or financial transactions with slight differences in logic.

Rather than redesigning everything manually, consultants can clone an existing integration, rename it, adjust mappings, update endpoints, and deploy the modified integration.

This article provides a detailed consultant-level explanation of Cloning of Integrations in OIC, including architecture, use cases, configuration steps, testing, troubleshooting, and best practices used in real-world implementations.

What is Cloning of Integrations in OIC?

Cloning of integrations in Oracle Integration Cloud (Gen 3) refers to the process of creating a duplicate copy of an existing integration within the same OIC instance.

The cloned integration includes:

• All orchestration logic

• Mappings

• Adapters

• Variables

• Tracking fields

• Fault handlers

• Business identifiers

However, the cloned integration is created as a separate integration artifact, allowing developers to modify it independently.

Key Characteristics

This feature is especially useful when multiple integrations follow a common pattern.

Real-World Integration Use Cases

1. Multiple Fusion Modules Using Similar Integrations

A customer may need integrations for multiple modules.

Example:

Instead of creating three integrations manually, consultants clone the first integration and modify the payload mappings.

2. Environment-Specific Integration Versions

In large projects, separate integrations may be required for:

• Production

• Testing

• Sandbox environments

Consultants clone an existing integration and update:

• Endpoint URLs

• Authentication credentials

• Target systems

3. Customer-Specific Custom Integrations

In multi-tenant implementations, different clients might need slightly different business logic.

Example:

A base integration can be cloned and customized per client.

Architecture / Technical Flow

Understanding how cloning works internally helps integration developers avoid design issues.

Original Integration Flow

After Cloning

Key points:

• Cloned integrations inherit the entire flow

• Adapters remain configured

• Endpoint connections remain the same (can be modified later)

• All mappings remain intact

Prerequisites

Before cloning integrations in Oracle Integration Cloud Gen 3, ensure the following prerequisites are met.

1. Required Roles

User must have:

• ServiceDeveloper

• ServiceAdministrator

These roles allow:

• Viewing integrations

• Cloning integrations

• Modifying configurations

2. Integration Must Be Activated or Saved

The integration you want to clone must:

• Exist in the OIC environment

• Be saved or activated

3. Valid Connections

If the integration uses adapters such as:

• REST Adapter

• SOAP Adapter

• FTP Adapter

• Oracle ERP Adapter

• Oracle HCM Adapter

Ensure the connections exist in the environment.

Step-by-Step Process: Cloning of Integrations in OIC

This section explains the complete cloning process used by integration consultants.

Step 1 – Login to Oracle Integration Cloud

Open the Oracle Integration Cloud Gen 3 console.

Login using valid credentials.

Step 2 – Navigate to Integrations

From the OIC homepage:

This page lists all available integrations.

Step 3 – Locate the Integration to Clone

Search for the integration using:

• Integration name

• Integration type

• Tags

Example:

Step 4 – Open the Integration Actions Menu

Next to the integration name, click the three-dot menu (Actions).

You will see options like:

• Edit

• Activate

• Clone

• Export

• Delete

Select:

Step 5 – Provide Details for the Cloned Integration

OIC will prompt for the following fields.

Example:

Click Clone.

Step 6 – Open the Cloned Integration

After cloning, the integration appears in the list.

Open it and review:

• Trigger adapter

• Mapping

• Business logic

• Variables

• Fault handling

At this stage, the integration is an exact replica of the original.

Step 7 – Modify Integration Logic

Typical changes made after cloning:

Update Endpoints

Example:

Modify Data Mapping

Open the Mapper and update fields.

Example:

Update Business Logic

Sometimes the business logic changes.

Example:

Original logic:

Modified logic:

Step 8 – Save and Activate Integration

Click:

OIC validates:

• Mappings

• Adapter configurations

• Business identifiers

Once activated, the cloned integration becomes available for execution.

Testing the Cloned Integration

Testing is an essential part of integration implementation.

Test Scenario

Integration Name:

Source System:

Oracle Fusion HCM

Target System:

Data Warehouse API

Sample Test Payload

Example JSON payload sent to the integration:

Expected Processing

The integration performs:

1. Receives employee data

2. Validates mandatory fields

3. Maps data

4. Sends request to target system

Validation Checks

During testing verify:

Monitoring Execution

Navigate to:

Search for the integration instance and review:

• Payload

• Execution path

• Errors

Common Errors and Troubleshooting

Even experienced consultants face issues when cloning integrations.

1. Connection Not Found

Error:

Reason:

The connection used in the original integration does not exist in the current environment.

Solution:

Reassign the correct connection.

2. Adapter Configuration Error

Error:

Reason:

Endpoint configuration changed.

Solution:

Reconfigure the adapter.

3. Mapper Validation Errors

Error:

Reason:

Target schema changed.

Solution:

Update mapper fields.

4. Integration Activation Failure

Error occurs during activation due to:

• Missing tracking fields

• Invalid expressions

• Missing variables

Solution:

Review validation errors and correct configuration.

Best Practices for Cloning Integrations

Experienced Oracle Integration Cloud consultants follow specific practices when cloning integrations.

1. Use Meaningful Naming Conventions

Example:

Clear names simplify maintenance.

2. Update Business Identifiers

After cloning, update:

This improves monitoring and reporting.

3. Validate All Connections

Always verify:

• Authentication

• Endpoints

• Credentials

before activating the cloned integration.

4. Document Integration Changes

Maintain documentation such as:

5. Avoid Excessive Cloning

While cloning speeds development, excessive cloning creates:

• Duplicate logic

• Maintenance complexity

Instead, consider reusable integrations where possible.

Consultant Tips from Real Implementations

During large enterprise projects, cloning integrations is commonly used in the following scenarios:

Large HCM Data Integrations

When integrating employee, assignment, and payroll data, integrations often follow identical logic.

Consultants clone integrations and only adjust payload structures.

Multi-Country Deployments

Global companies deploy integrations per region.

Example:

Cloning helps maintain consistent architecture.

Rapid Prototyping

In early project phases, cloning helps developers quickly create proof-of-concept integrations.

Summary

Cloning of Integrations in Oracle Integration Cloud Gen 3 is a powerful feature that significantly improves development efficiency. By duplicating existing integrations, developers can quickly build new integrations while maintaining consistency across integration patterns.

In real-world enterprise implementations, cloning helps reduce development time, minimize errors, and standardize integration design across projects. However, it is important to validate connections, update mappings, and properly test cloned integrations before deploying them into production.

By following proper naming conventions, documentation practices, and validation checks, integration consultants can effectively use cloning to manage large-scale integration environments.

For additional technical documentation and advanced integration concepts, refer to the official Oracle documentation:

https://docs.oracle.com/en/cloud/saas/index.html

FAQs

1. Does cloning an integration copy the connections in OIC?

Yes. The cloned integration references the same connections used in the original integration. However, you can change the connection configuration if required.

2. Can we clone integrations across different OIC environments?

Direct cloning works only within the same environment. To move integrations across environments, you must use export and import packages.

3. Does cloning copy fault handling logic?

Yes. Fault handlers, scope handlers, and exception logic are copied exactly as they exist in the original integration.