Skip to main content
The Oracle Integration Cloud (OIC) plugin manages integrations, connections, libraries and lookups running in the Oracle Integration Cloud.  The plugin makes it fast, easy, and consistent to move integrations and associated objects through multiple environments.
  • Minimum Java 8 must be used on the endpoint

​
Blog Posts

​
Key Features

  • Supports Oracle Integration Gen 2 and Oracle Integration 3 instances
  • Simple configuration.
  • Use package deployment functionality to deploy selected integrations.
  • Ability to manage connections with integrations or independently.
  • Property replacement on connection properties by environment.
  • Ability to sync shared objects, such as lookups and libraries.
  • Ability to manage continuous integration of an OIC Instance
  • Ability to run an integration
  • Ability to deactivate/activate an integration
  • Ability to work with OIC Projects (Gen 3). This refers to entire Project deployment and not individual components of the Project.
    • Deploy
    • Update Connection Properties
    • Download Connection plans
    • Activate / Deactivate integrations
    • Start/Stop/Pause/Resume Schedules
    • Sync to SCM
  • Ability to build and deploy individual project integrations, including associated components such as connections, lookups, and libraries. This does not support sourcing from SCM due to Oracle API limitations.
  • Ability to manage B2B objects (Documents, Schemas, Host Profile, Trading Partners), including Trading Partner Identifier Plans and Trading Partner Config Plans for environment-specific overrides.
  • Connections that are shared by various projects are not supported.
  • Connections that require the Provide Consent action are not fully automated by FlexDeploy at this time. FlexDeploy can deploy the connection and configure its properties, but it does not perform the interactive OAuth consent process.
    • If the connection already has valid consent and the deployment does not invalidate the existing authorization, additional consent may not be required.
    • If consent is required after deployment, it must be completed manually in Oracle Integration Cloud before the connection can be successfully used. Until consent is completed, deployment of integrations that use the connection will fail.

​
FlexDeploy Project Recommendations

Integrations, Lookups, Connections, Libraries, and Projects are all supported using Package-based projects, so simply use one project to manage all file types. Export from Cloud or source from SCM.

​
Plugin Operations

See OIC - How to replace endpoints in attachments.

​
Notes

This plugin does not support basic auth for any operations that utilize the REST API. This is restricted by Oracle.

​
Edge Cases and Limitations

  • Shared project connections — Connections shared across multiple OIC projects are not supported for project or project-integration deployment.
  • Provide Consent connections — FlexDeploy can deploy and configure connection properties, but interactive OAuth consent must be completed manually in OIC when required.
  • Project integrations vs full projects — Individual project integrations can be built and deployed without deploying the entire project. Project integrations are discovered from the OIC instance only (not from SCM) and are packaged as .car files. See OIC Object Type - Integration (Project Integrations).
  • IAR files — Standalone integration .iar artifacts should not be modified outside OIC.
  • B2B transport linked integrations — Deploying a B2B transport reactivates the originally linked auto-created integration version. If a newer manually activated version has a running schedule, deployment can fail with B2B-05108 until the schedule is stopped. See packageDeploy (OIC).
  • Cloud account authentication — Use OAuth (Resource Owner or JWT Assertion). Basic auth is not supported for REST API operations.

​
Additional Information

​
Supported File Types

​
Troubleshooting

​
TimeoutException During Discover Process

In environments containing a large number of Oracle Integration Cloud (OIC) objects, the Discover operation may exceed the configured REST Read Timeout and result in a timeout exception. To resolve this issue, increase the REST Read Timeout value. Navigate to: Administration → System Settings → General → REST Read Timeout image-20260611-150256.png Add or update a timeout entry matching your OIC endpoint and specify a larger timeout value (in milliseconds). Save the changes and retry the Discover operation. Click to know more about these settings

​
Integration activation takes too long (FDOIC-00009)

Some integrations take longer than the default wait to reach an activated state before tracing or related post-activation steps. Increase the Activation Retry Count input (FDOIC_INP_ACTIVATION_RETRY_COUNT) on packageDeploy, importIntegration, or activateIntegration. Each attempt waits 10 seconds; the default is 10 (about 100 seconds).

​
B2B transport deploy fails with B2B-05108

When a newer version of a transport-linked integration has a running schedule, OIC cannot deactivate it during transport deployment. Stop the schedule on the newer integration version in OIC, then retry the Trading Partner / transport deployment.

​
Connection locked during update

If connection updates fail because the connection is locked in OIC, increase Connection Retry Count (FDOIC_INP_CONNECTION_RETRY_COUNT) on the deploy operation (default is 10).