Imports an integration as a .iar artifact into the Oracle Integration Cloud. The operation will activate the newly deployed integration after deployment is finished. Any connections will also be imported. They will be processed by the updateConnections operation as part of this operation, so it isn't necessary to have additional steps in your workflow. Lookups included in the integration export will also be imported.
| Info |
|---|
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 for details on how to setup Cloud Account for OIC. |
Target Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
OIC Account |
| No | The OIC account with all the required properties like Base URI, Username and Password for running OIC Instance. |
...
Input Name | Input Code | Required | Description | ||
|---|---|---|---|---|---|
OIC Account |
| No | The OIC account with all the required properties like Base URI, Username and Password for running OIC Instance. | ||
Overwrite Integrations |
| No | Overwrite integrations with the same name and version when importing. | ||
OIC Connection Plan File |
| 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. | ||
Enable Tracing |
| No | When tracing is enabled, integration activity can be viewed in the Activity Stream.
| ||
Enable Payload Tracing |
| No | Should the payload be traced.
| ||
Send to Oracle Recommends |
| No | Contribute integration mappings to Oracle Recommends.
| ||
Integration Retry Count |
| No | @since 7.0.0.3 The number of times an integration will be retried incase of failures. Default is 5. | ||
Connection Retry Count |
| No | @since 7.0.0.3 The number of times an connection will be retried incase of failures due to connection being locked. Default is 10. | ||
Update Schedules |
| No | @since 7.0.0.3 Update schedule parameter for Simple or iCal recurrence. | ||
Schedule Override Directory |
| No | @since 6.5.0.14 Specify directory to override integration schedules by environment. Use FD_ENVIRONMENT_CODE to indicate folder for current environment. The subfolder of this folder must be various Integration Ids(Use iar file name as Integration Id). Integration iar archive file has schedules stored as xml file in icspackage/schedule folder which can be copied to prepare override files. |
Artifacts
This operation consumes artifacts from the artifacts repository.
...