Exports a list of transfers and the associated artifacts, including the config plan, 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 your mft source is checked out from the SCM using the file plugin.
When 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 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.
MFT Server Host
The host name for MFT (e.g.
|MFT Server Port|
|Yes||The managed server port number for MFT.(e.g. |
|Weblogic Admin Password|
|Yes||Weblogic Admin Password|
|Weblogic Admin User|
|Yes||The user name for the WLS admin server.|
|Oracle Middleware Home (MW_HOME)|
|Yes||The oracle middleware home (which has subfolders such as |
oracle_common, wlserver, coherence*, etc.) (e.g. /u01/oracle/products/fmw)
Rename After Export
The artifacts wil be renamed to the name of the artifact after export
|Transfers To Export|
|No||Comma separated list of transfers to export. If left empty, all transfers will be exported.|
This operation doesn’t consume or produce any artifacts.
This operation will select all available endpoints associated to the environment/instance.
This operation will execute on any one of the selected endpoints and will be random in the determination of which one.