Skip to main content
Import a B2B Trading Partner into OIC.
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

FDOIC_CLOUD_ACCOUNT_CODE

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

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 B2B Trading Partner

FDOIC_INP_B2B_REPLACE_TRADING_PARTNER

No

Overwrite B2B Trading Partner with the same name when importing.

Re-activate B2B Document Associated Integrations

 

FDOIC_INP_B2B_TP_DEPLOY_TRANSPORTS

No

If the document is associated with active integrations, those integrations will be automatically deactivated before deployment. Enable this option to automatically reactivate them after deployment.

Deploy Inbound Agreements

FDOIC_INP_B2B_TP_DEPLOY_INBOUND_AGREEMENTS

No

Deploy inbound agreements and associated backend integrations.

Deploy Outbound Agreements

FDOIC_INP_B2B_TP_DEPLOY_OUTBOUND_AGREEMENTS

No

Deploy outbound agreements for this Trading Partner.

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.

Start Schedules

FDOIC_INP_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

FDOIC_INP_INCLUDE_RUN_AS_USER_FOR_START_SCHEDULES

No

Enable this to include the username in the schedule start request. This is applicable only when schedule start is enabled. since 9.0.0.9

Activate Integration

FDOIC_INP_ACTIVATE_INTEGRATION

No

Should the integration be activated after deployment.

Enable Tracing

FDOIC_INP_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

FDOIC_INP_ENABLE_PAYLOAD_TRACING

No

Should the payload be traced.

Will only apply if instance is also being activated

Send to Oracle Recommends

FDOIC_INP_SEND_TO_ORACLE_RECOMMENDS

No

Contribute integration mappings to Oracle Recommends.

Will only apply if instance is also being activated

Update Schedules

FDOIC_INP_UPDATE_SCHEDULES

No

Update schedule parameter for Simple or iCal recurrence.

Schedule Override Directory

FDOIC_INP_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

FDOIC_INP_CAN_REPLAY

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.)
(Note for only OIC Gen3)

Enable Payload Validation

FDOIC_INP_ENABLE_PAYLOAD_VALIDATION

No

When enabled, inbound JSON payload syntax is validated during the activation of REST Adapter trigger-based integrations.
(Note for only OIC Gen3)

OIC Trading Partner Identifier Plan File

FDOIC_INP_B2B_TP_IDENTIFIER_PLAN

No

Optional input to specify a different Trading Partner Identifier Plan file name. Default ‘TradingPartnerIdentifiersPlan.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.