OIC Account

FDOIC_INP_CLOUD_ACCOUNT_CODE

No

The OIC account with all the required properties like Base URI, Username and Password for running OIC Instance.

Overwrite Integrations

FDOIC_INP_REPLACE_INTEGRATION

No

Overwrite integrations with the same name and version when importing.
The default value of this property allows using a project property to control this on a per-project basis.

OIC Connection Plan File

FDOIC_INP_CONNECTION_PLAN

No

Optional connection configuration file to run during import.  The default is 'connectionPlan.properties' in the FD_ARTIFACTS_DIR. 

Allows absolute path or relative to the artifacts directory.

This is used for replacing values in the connections.json file.

That file must be present in order to have values replaced in it.

Will be pre-processed by the plugin to transform any defined replacement properties based on the deployed environment.

Deploy Delay between Integrations

FDOIC_INP_PARTIAL_DEPLOY_DELAY

No

Specify deploy delay in seconds between integrations. Default is 0, which means no delay. Use this delay only if you see issues with Oracle Integration Cloud deployments.

Update Connections Mode

FDOIC_INP_UPDATE_CONNECTION_MODE

Yes

@since 6.5.0.12

Input to determine whether connections should be updated after deployment. Defaults to ALL.

If value is set to ALL, every applicable connection is updated.

If value is set to SPECIFIC, only connections specified in FDOIC_INP_UPDATE_CONNECTION_LIST will be updated.

If value is set to NONE, none of the connections are updated after a deployment.

Update Connection List

FDOIC_INP_UPDATE_CONNECTION_LIST

No

@since 6.5.0.12

Comma-separated list of connection IDs to update after deployment. This input is only considered when FDOIC_INP_UPDATE_CONNECTION_MODE is set to SPECIFIC.

Attachment Override Directory

FDOIC_INP_ATTACHMENT_OVERRIDE_DIRECTORY

No

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.

Start Schedules

FDOIC_INP_START_SCHEDULES

No

@since 6.5.0.3

If true, the file attribute Start Schedules is used to determine if any schedules should be initiated after integration deployment. If false, schedules will not be started regardless of the file attribute value.

This is useful to start schedules based on workflow execution variables. I.E. Starting schedules if FD_ENVIRONMENT_CODE is Production.

Enable Tracing

FDOIC_INP_ENABLE_TRACING

No

@since 6.5.0.3

If true, the file attribute Enable Tracing is used to determine if integration activity can be viewed in the Activity Stream. If false, tracing will be disabled regardless of the file attribute value.

This is useful to enable tracing based on workflow execution variables. I.E. Enable tracing if FD_ENVIRONMENT_CODE is Production.

Enable Payload Tracing

FDOIC_INP_ENABLE_PAYLOAD_TRACING

No

@since 6.5.0.3

If true, the file attribute Enable Payload is used to determine if the payload should be traced. If false, payload tracing will be disabled regardless of the file attribute value.

This is useful to enable payload tracing based on workflow execution variables. I.E. Starting schedules if FD_ENVIRONMENT_CODE is Production.