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. |
Project Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
Integration Identifier |
| No | The identifier (code) of the integration being deployed |
Overwrite Integrations |
| No | Overwrite integrations with the same name and version when importing. Note that if you modify the |
Inputs
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 definedreplacement properties based on the deployed environment. |
Start Schedules |
| No | Should any schedules for the imported integration be started after deployment? Activate Integration should be true or this will not take effect. |
Include Run As User |
| No | Enable this to include the username in the schedule start request. This is applicable only when schedule start is enabled. |
Activate Integration |
| No | Should the integration be activated after deployment. |
Enable Tracing |
| No | When tracing is enabled, integration activity can be viewed in the Activity Stream. Will only apply if instance is also being activated |
Enable Payload Tracing |
| No | Should the payload be traced. Will only apply if instance is also being activated |
Send to Oracle Recommends |
| No | Contribute integration mappings to Oracle Recommends. Will only apply if instance is also being activated |
Integration Retry Count |
| No | The number of times an integration will be retried incase of failures. Default is 5. |
Connection Retry Count |
| No | The number of times an connection will be retried incase of failures due to connection being locked. Default is 10. |
Update Schedules |
| No | Update schedule parameter for Simple or iCal recurrence. |
Schedule Override Directory |
| No | 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. |
Allow to Run Again |
| No | 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.) |
Enable Payload Validation |
| No | When enabled, inbound JSON payload syntax is validated during the activation of REST Adapter trigger-based integrations. |
Activation Retry Count
|
| No | 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. |
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.Log |
|
|
|---|---|---|
Production | false | false |
Debug | true | true |
Audit | true | false |
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
Retrying
- If any connection the integration uses is locked, the plugin will retry up to 10 times with 30 seconds of quiet time in between attempts. If after 10 attempts, it is still unable to update the connection then an error will be thrown. This is a common case when multiple integrations are deploying at the same time that share the connection.
- The entire import operation will be retried up to 5 times with a 30 second delay. These retries are independent of the connection retries mentioned above.