Import a Trading Partner into the B2B repository along with all of its associated Agreements and dependencies such as Listening Channel and documents. B2bImportTradingPartner also accepts a config file for property replacement.

Environment/Instance Properties

Property Name	Property Code	Required	Description
B2B Server Host	`FDB2B_SERVER_HOST`	Yes	Host Name for the B2B Server. Under the default SOA installation, it will share the same host as the managed SOA servers.
B2B Server Port	`FDB2B_SERVER_PORT`	Yes	Port for the B2B Server
Oracle SOA Home	`FD_ORACLE_SOA_HOME`	Yes	Oracle SOA Home, indicates where SOA Suite is installed.

Project Properties

Property Name	Property Code	Required	Description
B2B Trading Partner	`FDB2B_TP_NAME`	Yes	The name of the Trading Partner to be imported to the B2B Repository.

Inputs

Input Name	Input Code	Required	Description
Config File	`FDB2B_INP_CONFIG_FILE`	No	Config file to be used to replace environment specific properties.
Activate Agreement	`FDB2B_INP_ACTIVATE_AGRMT`	No	Boolean to indicate whether or not to activate the Agreements on deployment.
Overwrite Data	`FDB2B_INP_OVERWRITE_DATA`	No	Boolean to indicate whether or not to overwrite any conflicting data on deploy.
B2B User	`FDB2B_B2B_USER`	No	User that performs the given operation

Outputs

Output Name	Required	Description

Artifacts

This operation consumes the Trading Partner zip produced in the export step as well as any config file to be used for property replacement. This is not exposed to workflow developer.

Endpoint Selection

This operation will select all available endpoints associated to the environment instance.

Endpoint Execution

This operation will execute on any endpoint from the endpoint selection.

Special Considerations

This operation uses a config file located in the artifacts repository to perform property replacement. Leaving the input FDB2B_INP_CONFIG_FILE blank will bypass any property replacement and deploy the Trading Partner and Agreements as they were upon export.

Browser not supported