> ## Documentation Index
> Fetch the complete documentation index at: https://docs.flexagon.com/llms.txt
> Use this file to discover all available pages before exploring further.

# activateIntegration

> Activates an Integration on the OIC server. This operation is included in the and operations, so it is not needed if one of those operations is alread

Activates an Integration on the OIC server.

> [!NOTE]
>
> This operation is included in the [importIntegration](https://docs.flexagon.com/flexdeploy-11-1-documentation/flexdeploy-plugin-guides/flexdeploy-oracle-integration-cloud-plugin-guide/importintegration.md) and [packageDeploy](https://docs.flexagon.com/flexdeploy-11-1-documentation/flexdeploy-plugin-guides/flexdeploy-oracle-integration-cloud-plugin-guide/packagedeploy-oic.md) operations, so it is not needed if one of those operations is already present in the workflow.
>
> Either **FDOIC\_CLOUD\_ACCOUNT\_CODE** Target property value or **FDOIC\_INP\_CLOUD\_ACCOUNT\_CODE** plugin input value should exist. When both exist, the plugin input value will take precedence. See [Creating/Editing a Cloud Account and Provider](https://docs.flexagon.com/flexdeploy-11-1-documentation/flexdeploy-users-guide/integrations/cloud-account-and-provider.md) for details on how to setup a Cloud Account for OIC.

# Target Properties

<table><colgroup><col /><col /><col /><col /></colgroup><tbody><tr><th>**Property Name**</th><th>**Property Code**</th><th>**Required**</th><th>**Description**</th></tr><tr><td>OIC Account</td><td>`FDOIC_CLOUD_ACCOUNT_CODE`</td><td>No</td><td>The OIC account with all the required properties like Base URI, Username and Password for connecting to an OIC Instance.</td></tr></tbody></table>

# Project Properties

<table><colgroup><col /><col /><col /><col /></colgroup><tbody><tr><th>**Property Name**</th><th>**Property Code**</th><th>**Required**</th><th>**Description**</th></tr><tr><td>Integration Identifier</td><td>`FDOIC_INTEGRATION_IDENTIFIER`</td><td>Yes</td><td>The identifier (code) of the integration being activated.This may not be the same as the name of the integration.Prefix with PROJECTID- to refer to an integration in a project.</td></tr></tbody></table>

# Inputs

<table><colgroup><col /><col /><col /><col /></colgroup><tbody><tr><th>**Input Name**</th><th>**Input Code**</th><th>**Required**</th><th>**Description**</th></tr><tr><td>OIC Account</td><td>`FDOIC_INP_CLOUD_ACCOUNT_CODE`</td><td>No</td><td>The OIC account with all the required properties like Base URI, Username and Password for connecting to an OIC Instance.Typically, this will not be used because the value will come from the property FDOIC\_CLOUD\_ACCOUNT\_CODE instead.</td></tr><tr><td>OIC Integration Version</td><td>`FDOIC_INP_INTEGRATION_VERSION`</td><td>No</td><td>Optional version of the integration, leave blank for latest. (e.g. 01.02.0000)</td></tr><tr><td>OIC Version Logic</td><td>`FDOIC_INP_VERSION_LOGIC`</td><td>No</td><td>If `FDOIC_INP_INTEGRATION_VERSION` is blank, then this input determines how the latest version is determined, either by the last updated in the system, or the highest version number.</td></tr><tr><td>Enable Tracing</td><td>`FDOIC_INP_ENABLE_TRACING`</td><td>No</td><td>When tracing is enabled, integration activity can be viewed in the Activity Stream. (Boolean)</td></tr><tr><td>Enable Payload Tracing</td><td>`FDOIC_INP_ENABLE_PAYLOAD_TRACING`</td><td>No</td><td>When tracing is enabled, integration activity can be viewed in the Activity Stream. (Boolean)</td></tr><tr><td>Send to Oracle Recommends</td><td>`FDOIC_INP_SEND_TO_ORACLE_RECOMMENDS`</td><td>No</td><td>Contribute integration mappings to Oracle Recommends. (Boolean)(Note for only OIC Gen2)</td></tr><tr><td>Allow to Run Again</td><td>`FDOIC_INP_CAN_REPLAY`</td><td>No</td><td>When replay is enabled, an instance of the integration can be replayed during runtime. (Available only for REST Adapter-triggered and AS2 Adapter-triggered integrations.)\
(Note for only OIC Gen3)</td></tr><tr><td>Enable Payload Validation</td><td>`FDOIC_INP_ENABLE_PAYLOAD_VALIDATION`</td><td>No</td><td>When enabled, inbound JSON payload syntax is validated during the activation of REST Adapter trigger-based integrations.\
(Note for only OIC Gen3)</td></tr><tr><td>Activation Retry Count`(Since 11.1.0.4)`</td><td>`FDOIC_INP_ACTIVATION_RETRY_COUNT`</td><td>No</td><td>The number of times to poll for integration activation status before failing. Each attempt waits 10 seconds. Default is 10 (100 seconds). Increase this value for integrations that take longer to activate</td></tr></tbody></table>

# Artifacts

This operation doesn’t consume or produce any artifacts.

# Endpoint Selection

This operation will select all available endpoints associated to the Target.

# Endpoint Execution

This operation will execute on any one of the selected endpoints and will be random in the determination of which one.

# Special Considerations for OIC Gen3

OIC Gen3 allows you to configure the log level, which can be set to one of three types: Production, Audit, and Debug. These settings can be easily adjusted using the existing plugin inputs. To configure the log levels, use the following configuration.

<table><colgroup><col /><col /><col /></colgroup><tbody><tr><th>**Log**</th><th>`FDOIC_INP_ENABLE_TRACING`(`tracingEnabledFlag`)</th><th>`FDOIC_INP_ENABLE_PAYLOAD_TRACING`(`payloadTracingEnabledFlag`)</th></tr><tr><td>Production</td><td>false</td><td>false</td></tr><tr><td>Debug</td><td>true</td><td>true</td></tr><tr><td>Audit</td><td>true</td><td>false</td></tr></tbody></table>