OIC - Managing Integration Limits in Oracle Integration Cloud (OIC) Using Projects and Shared Connections

Use Case:

In Oracle Integration Cloud (OIC), you may encounter limits like:

• 100 Integrations per project
• 50 Connections per project

As your environment grows, hitting these limits can cause issues in maintenance, deployment, and governance.

So, how do you scale your OIC environment effectively?

Solution Overview:

To handle this, follow a modular design using multiple projects:

Best Practice Strategy:

1. Create multiple domain-specific projects (e.g., HR, Finance, Procurement) and assign the **serviceDeveloper** role to developers who need edit access.
2. Create a common project (e.g., CommonResources) that holds shared connections like HCM, ERP, REST, FTP.
3. Use shared connections from the common project in other integration projects.
4. We can also share integrtaions from COMMON project and then we can copy them into another project.
5. We can also invoke shared integrtaions as local integration call from other projects.

Step-by-Step Guide

1. Create a New Project in OIC:

• Go to OIC Home > Projects
• Click “+ Create Project”
• Give a name like FinanceProject, HRProject, or CommonResources
• Add description and tags (optional)
• Click Create
• Assign access edit, view and monitor role as expected.

2. Add Connections in Common Project:

• Open the CommonResources project
• Go to Connections
• Click “+ Create”, configure REST, SOAP, HCM, ERP, etc.
• Share with other projects.
• These will now be available as shared connections

3. Share Connection with Other Projects:

• Go to the destination project (e.g., HRProject)
• Click Connections > + Add Shared Connection
• Select from the list of connections created in CommonResources
• Click Add

Now, that connection is usable in your integrations in that project, without recreating it.

4. Assign ServiceDeveloper Role:

• Go to OIC Console > Identity & Access
• Click Users > Assign Roles
• Select user
• Assign OIC_ServiceDeveloper role
• This gives them full edit access to integrations, connections, and lookups in that project.

Benefits of This Approach:

• Avoid hitting integration/connection limits
• Easier access control and role assignment
• Better modularization of logic by domain
• Improved governance and maintainability

we can also copy one integration to another project as below:

Share the integration:

Copy to the project as required.