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. |
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 B2B Trading Partner |
| No | Overwrite B2B Trading Partner with the same name when importing. |
Deploy Transports |
| No | Deploy transport definitions for this Trading Partner. |
Deploy Inbound Agreements |
| No | Deploy inbound agreements and associated backend integrations. |
Deploy Outbound Agreements |
| No | Deploy outbound agreements for this Trading Partner. |
Overwrite Integrations |
| No | Overwrite integrations with the same name and version when importing. |
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 |
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. |
OIC Trading Partner Identifier Plan File |
| No | optional input to specify a different Trading Partner Identifier Plan file name. Default ‘TradingPartnerIdentifiersPlan.properties’. |
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 |
OIC Trading Partner Config Plan File
|
| No | Optional input to specify a different Trading Partner Config Plan file name. Default ‘TradingPartnerConfigPlan.properties’ |
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.B2B Transport Deployment Behaviour
During an overwrite import of a B2B trading partner, FlexDeploy:- Undeploys existing transports, then inbound/outbound agreements
- Imports the trading partner
- Deploys transports and agreements again (when those deploy options are enabled)
DEPLOYED or FAILED. Oracle allows undeploy in both of those states. Other transport statuses are skipped.
When a transport is deployed, OIC activates the auto-created integration versions permanently linked to that transport.
If a user manually creates and activates a newer version of an auto-created integration, deploying the transport will reactivate the original linked version and deactivate the newer version.
- If the newer version has no running schedule: The transport deployment can deactivate the newer version and activate the original version successfully.
-
If the newer version has a running schedule: OIC cannot deactivate the newer version while its schedule is running. The transport deployment fails with
B2B-05108. Stop the schedule on the newer version (or remove that version), then retry the deployment.
Key points
- OIC B2B transports are permanently linked to their originally created integrations.
- Only one version of an integration can be active at a time.
- Avoid creating new versions of transport-linked integrations; the transport continues to use the originally linked version.