This operation is included in the importIntegration operation. You don't need to put updateConnections or activateIntegration in your workflow after the importIntegration 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/

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 their is a connections.json file in the temp directory. 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.

Creating New Connections

Oracle does not have an API for creating connections. Connections are created only when done manually or when an integration is imported. This operation is for updating connections only. As such, it is recommended that this operation be carried out after an import integration operation in your workflow.

Environment/Instance Properties

Property Name	Property Code	Required	Description
OIC Base URI	`FDOIC_CLOUD_INSTANCE_BASE_URI`	Yes	The REST Base URI of a running OIC Instance
OIC User	`FDOIC_USERNAME`	Yes	The user to connect to OIC as
OIC Password	`FDOIC_PASSWORD`	Yes	The password for the OIC User

Project Properties

Property Name	Property Code	Required	Description

Inputs

Input Name

Input Code

Required

Description

OIC Connection Plan File

FDOIC_INP_CONNECTION_PLAN

No

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.

Outputs

Output Name	Required	Description

Artifacts

This operation consumes artifacts from the artifacts repository.

Endpoint Selection

This operation will select all available endpoints associated to the environment/instance.

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.

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

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

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 is applied if present to to update environment specific properties.