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 |
Project Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
| B2B Agreement Name | FDB2B_ |
AGRMT_NAME | Yes | The name of the |
Agreement to be |
exported from 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. |
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.
...