Exports a list of transfers and the associated artifacts from the MFT Design time to the export folder in the plugin execution's temp folder. You can copy these files from the ../temp/export/ folder to wherever you mft source is checked out from the SCM using the file plugin.
When a an artifact exports from MFT the name looks like: so_916dffd7-19fc-406e-9fac-12b46fe79d0f.xml, this makes it hard to determine which files to pick then deploying a transfer and its associated files, so the ExportTransfer operation will rename the file to the name you provided when you create the artifact for example: ABCTransfer.xml. These files are renamed back (to id.xml for example: so_916dffd7-19fc-406e-9fac-12b46fe79d0f.xml) during the build step.
The purpose of this operation is to simplify getting mft MFT artifacts into an SCM, and typically this operation will be used in a workflow specifically built to populate SCM, rather than in the build workflow.
Environment/Instance Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
MFT Server Host | FDMFT_SERVER_HOST | Yes | The host name for MFT (e.g. mftdev.company.com) |
| MFT Server Port | FDMFT_SERVER_PORT | Yes | The managed server port number for MFT.(e.g. 8001) |
| Weblogic Admin Password | FDWLS_ADMIN_PASSWORD | Yes | Weblogic Admin Password |
| Weblogic Admin User | FDWLS_ADMIN_USER | Yes | The user name for the WLS admin server. |
| Oracle Middleware Home (MW_HOME) | FD_ORACLE_MW_HOME | Yes | The oracle middleware home (which has subfolders such as oracle_common, wlserver, coherence*, etc.) (e.g. /u01/oracle/products/fmw) |
...
| Input Name | Input Code | Required | Description |
|---|---|---|---|
| Transfers To Export | TRANSFERS_TO_EXPORT | No | Comma separated list of transfers to export. If left empty, all transfers will be exported. |
Outputs
Output Name | Required | Description |
|---|---|---|
...