b2bExportTradingPartner
- Karl Henselin
Exports a Trading Partner and all Agreements for the Trading Partner from the B2B repository. Similar to the exportB2BAgreement step, any and all dependencies are exported as well.
Target Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
B2B 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 |
| Yes | Port for the B2B Server |
Oracle SOA Home |
| Yes | Oracle SOA Home indicates where SOA Suite is installed. |
Project Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
B2B Trading Partner |
| Yes | The name of the Trading Partner to be exported from the B2B Repository. |
Inputs
Display Name | Input Code | Required | Description |
|---|---|---|---|
B2B User |
| No | User that performs the given operation |
Artifacts
This operation produces a zip file artifact containing zip files of the Agreements associated to the exported Trading Partner to the artifact repository. This is not exposed to workflow developer. Â
Endpoint Selection
This operation will select all available endpoints associated to the Target.
Endpoint Execution
This operation will execute on any endpoint from the endpoint selection.
Special Considerations
The import operation for Trading Partner accepts a config file for which to do property replacement with, as such, including an SCM export to pull in a config file in the same workflow as this export should be considered.
- style