> ## 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.

# updateConnections

> This operation is included in the operation. You don't need to put updateConnections or in your workflow after the operation. This page is the best so

> [!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) operation. You don't need to put updateConnections or [activateIntegration](https://docs.flexagon.com/flexdeploy-11-1-documentation/flexdeploy-plugin-guides/flexdeploy-oracle-integration-cloud-plugin-guide/activateintegration.md) in your workflow after the [importIntegration](https://docs.flexagon.com/flexdeploy-11-1-documentation/flexdeploy-plugin-guides/flexdeploy-oracle-integration-cloud-plugin-guide/importintegration.md) operation.
>
> This page is the best source of information about the way that connection information can be updated at deploy time.
>
> There is a blog article about replacements as well - [https://flexagon.com/2019/01/flexdeploy-loves-oic-manage-connection-property-replacement/](https://flexagon.com/2019/01/flexdeploy-loves-oic-manage-connection-property-replacement/)
>
> Either **FDOIC\_CLOUD\_ACCOUNT\_CODE** Target property value or **FDOIC\_INP\_CLOUD\_ACCOUNT\_CODE** plugin input value should exist. When both exists, 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 Cloud Account for OIC.

Updates connection properties in an OIC Instance.  Connection metadata should be in json format.  If properties have attachments, those attachments will be uploaded as well.  This operation is intended to work in tandem with exportConnections but it is not required.  This operation can be utilized as long as there is a connections.json file in `FD_ARTIFACTS_DIR`.  If there are attachments that need to be uploaded as well, they should be at the same level as the connections.json and follow the same directory format as seen in the attachments section [here](https://docs.flexagon.com/flexdeploy-11-1-documentation/flexdeploy-plugin-guides/flexdeploy-oracle-integration-cloud-plugin-guide/exportconnections.md).

# 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 running OIC Instance.</td></tr></tbody></table>

# Cloud Account 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 User</td><td>`FDOICACCT_USERNAME`</td><td>Yes</td><td>Username for the registered OIC account</td></tr><tr><td>OIC Password</td><td>`FDOICACCT_PASSWORD`</td><td>Yes</td><td>Password for the registered OIC account</td></tr><tr><td>OIC Base URI</td><td>`FDOICACCT_BASE_URI`</td><td>Yes</td><td>The REST Base URI of a running OIC Instance</td></tr><tr><td>OIC Identity Base URI</td><td>`FDOICACCT_IDENTITY_BASE_URI`</td><td>No</td><td>The Oracle Identity Cloud Service URL (IDCS). E.G. [[https://idcs-1a2bc3de.identity.oraclecloud.com](https://idcs-1a2bc3de.identity.oraclecloud.com)](https://idcs-1a2bc3de.identity.oraclecloud.com). Only required when using OAuth. For more information on configuring OAuth see [here](#).</td></tr><tr><td>OIC Client Id</td><td>`FDOICACCT_CLIENT_ID`</td><td>No</td><td>The Oracle Identity Client Id. Only required when using OAuth. For more information on configuring OAuth see [here](#).</td></tr><tr><td>OIC Client Secret</td><td>`FDOICACCT_CLIENT_SECRET`</td><td>No</td><td>The Oracle Identity Client Secret. Only required when using OAuth. For more information on configuring OAuth see [here](#).</td></tr><tr><td>OIC Client Scope</td><td>`FDOICACCT_CLIENT_SCOPE`</td><td>No</td><td>The Oracle Identity Client Scope. Only required when using OAuth. For more information on configuring OAuth see [here](#).</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>Stop On Deployment Error</td><td>`FDOIC_STOP_ON_DEPLOYMENT_ERROR`</td><td>No</td><td>Stop deploying package files if any error occurs. If unchecked all files will be deployed even if one or more files fails. This project property only applies to this operation.Defaults to true.</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 running OIC Instance.</td></tr><tr><td>OIC Connection Plan File</td><td>`FDOIC_INP_CONNECTION_PLAN`</td><td>No</td><td>Optional input to specify a different connection plan file name. Default 'connectionPlan.properties'. An absolute path can be specified otherwise it is relative to the artifacts directory.If left blank, then artifactsDir/connectionPlan.properties is assumed.</td></tr><tr><td>Activate Integration Mode</td><td>`FDOIC_INP_ACTIVATE_INTEGRATIONS_MODE`</td><td>No</td><td>Input to determine whether integrations should be re-activated after a connection is updated. Defaults to ALL.If value is set to ALL, every integration using this connection is re-activated.If value is set to SPECIFIC, only integrations specified in `FDOIC_INP_INTEGRATION_INCLUDE_LIST` will be re-activated.If value is set to NONE, none of the integrations are re-activated after the connection is updated.Note : Integration with status `ACTIVATED` will be considered.</td></tr><tr><td>Integration List</td><td>`FDOIC_INP_INTEGRATION_INCLUDE_LIST`</td><td>No</td><td>CSV list of integration IDs to re-activate. An integration ID is the integration identifier, a pipe, and then the version (e.g. HELLO\_WORLD|01.02.0001).</td></tr><tr><td>Attachment Override Directory</td><td>`FDOIC_INP_ATTACHMENT_OVERRIDE_DIRECTORY`</td><td>No</td><td>A directory which contains attachments to override. Any attachments contained in this directory will be copied over the existing attachments. Useful if you want to have different attachments per environment, you can use FD\_ENVIRONMENT\_CODE to achieve this. See the attachment overrides section for an example of this. Directory should be in the following format \<Connectionid>/\<PropertyName>/\<attachment>.Example : The folder structure should be \<Root>/\<Environment Code>/\<Connection Id>/\<Property Name>/\<Attachment File>There are situations where you may use same attachment for all environments, rather copying the attachment file structure to each environment folder, you can place them in the following folder structure \<Root>/**GLOBAL**/\<Connection Id>/\<Property Name>/\<Attachment File>.Attachments for connections placed under **GLOBAL **will be copied along with the files inside environment folder where the plugin execution runs, all files are then copied to the artifacts connection attachment folder. Files inside GLOBAL will be copied first and then files from environment folder will be copied.connectionPlan.properties now supports to use attachment override file for each instance for a connection.Ex, FLEX\_ATP\_DB is the connection id, uses wallet. In the connectionPlan.properties, you can define a workflow property and configure as below. The execution will search for the name in the override folder.FLEX\_ATP\_DB.secure.Wallet=\$\{\{FLEX\_ATP\_DB\_WALLET\_FILE\_NAME}}</td></tr><tr><td>Connection Retry Count</td><td>`FDOIC_INP_CONNECTION_RETRY_COUNT`</td><td>No</td><td>The number of times an connection will be retried incase of failures due to connection being locked. Default is 10.</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 consumes artifacts from the artifacts repository.

# 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

## Valid Artifact Directories

The below examples are all valid connection directory structures that will result in a successful execution.  Note that if you used exportConnections you do not need to worry about the directory structure.

> [!NOTE]
>
> ### Example 1
>
> 12343/12345/artifacts/HR\_SOAP\_CONNECTION/connections.json
>
> 12343/12345/artifacts/HR\_SOAP\_CONNECTION/attachments/HR\_SOAP\_CONNECTION/targetWSDLURL/hr.wsdl
>
> 12343/12345/artifacts/MY\_REST\_ENDPOINT\_INTERFAC/connections.json

> [!NOTE]
>
> ### Example 2
>
> 12343/12345/artifacts/myFolder/connections.json
>
> 12343/12345/artifacts/myFolder/attachments/HR\_SOAP\_CONNECTION/targetWSDLURL/hr.wsdl
>
> 12343/12345/artifacts/myFolder/attachments/EBS\_SOAP\_CONNECTION/targetWSDLURL/ebs.wsdl
>
> 12343/12345/artifacts/myFolder/connectionPlan.properties

> [!NOTE]
>
> ### Example 3
>
> 12343/12345/artifacts/connections.json
>
> 12343/12345/artifacts/connectionPlan.properties

## Connection Plans and Property Replacement

Prior to updating connections, the [connection plan file](https://docs.flexagon.com/flexdeploy-11-1-documentation/flexdeploy-plugin-guides/flexdeploy-oracle-integration-cloud-plugin-guide/createconnectionplan.md) is applied if present to to update environment specific properties.