Skip to main content
This operation creates a template B2B Trading Partner Identifier Plan file using the current B2B Trading Partner identifiers and control number settings found on the target OIC instance. The generated plan file can be used during the importTradingPartner or packageDeploy operations to override environment-specific Trading Partner identifier values and control number settings after deployment. Its purpose is to allow environment-specific B2B Trading Partner configuration to be managed outside of the exported Trading Partner artifacts. This eliminates the need to manually update Trading Partner identifiers or control numbers when deploying to different environments.

​
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 connecting to an 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 connecting to an OIC Instance.

Typically, this will not be used because the value will come from the property FDOIC_CLOUD_ACCOUNT_CODE instead.

Trading Partner List

FDOIC_INP_B2B_TRADING_PARTNER_LIST

No

CSV list of Trading Partner ids to include in the plan file. Leave blank to include all non-project Trading Partners. (ex: TRADING_PARTNERID1,PROJECTID:TRADING_PARTNERID2)

Project List

FDOIC_INP_B2B_PROJECT_LIST

No

CSV list of project ids to include Trading Partners from. Leave blank to include Trading Partners from all projects (ex: PROJECT1,PROJECT2)

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.

If neither the Trading Partner Identifier List nor the Project List is provided, Trading Partner Identifier Plans are created for all Trading Partners, including both global and project Trading Partners. If only one of the lists is provided, Trading Partner Identifier Plans are created only for the Trading Partners specified by that list. If both lists are provided, Trading Partner Identifier Plans are created for the Trading Partners specified in both lists.

​
Artifacts

This operation doesn’t consume or produce any artifacts.

​
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

​
B2B Trading Partner Identifiers Plan Format

The B2B Trading Partner Identifier Plan closely follows Java Properties syntax with the notable exception that spaces do not delimit the key/value pairs. Two types of entries are supported
Identifier Format%TradingPartnerId%.%IdentifierId%.%IdentifierType%=%value%Control Number Format%TradingPartnerId%.(interchangeControlNumberStart|groupControlNumberStart|transactionControlNumberStart)=%value%If the Trading Partner belongs to a Project, prefix the Trading Partner with the Project Id.%ProjectId%:%TradingPartnerId%.%IdentifierId%.%IdentifierType%=%value%or%ProjectId%:%TradingPartnerId%.interchangeControlNumberStart=%value%

Line Field

Description

TradingPartnerId

The Trading Partner identifier on the OIC.

ProjectId

Optional Project identifier for project-specific Trading.

IdentifierId

The unique identifier ID assigned by OIC.

IdentifierType

The identifier type as displayed in the OIC UI (for example, AS2 Identifier or EDI Interchange ID)

value

The replacement value. This may be plain text or a FlexDeploy property.|

Sample Properties

​
B2B Trading Partner Identifier Plan Processing

In the sample above, we are replacing the AS2 Identifier for the AVINSH_CORP Trading Partner with the FlexDeploy property ${{B2B_ID_VALUE}}. This means that B2B_ID_VALUE is configured as a FlexDeploy property (most likely a Target property) and can have a different value for each OIC environment. This allows Trading Partner identifiers and control number settings to be updated dynamically for each environment without modifying the exported Trading Partner artifacts. The properties should be added to a deploy workflow that is used for the importTradingPartner or packageDeploy operations. The workflow must then be associated with the appropriate OIC Target Group using the FlexDeploy topology screens.

​
Empty Properties

Only identifier and control number entries that need to be overridden should be included in the Trading Partner Identifier Plan file. If a line is present with no value (as shown above), the corresponding Trading Partner identifier or control number setting will be updated to an empty value.