The purpose of this operation is to simplify getting MFT artifacts into an SCM, and typically this operation will be used in a utility workflow specifically built to populate SCM, rather than in the build workflow.
Exports a list of transfers and the associated source and target artifacts and the config plan from the MFT Design time to the export folder in the plugin execution's temp folder FD_TEMP_DIR/export . 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 automatically rename the file files to the name of the source, target, or transfer that it contains. This 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.
...
will then be the one that is checked into SCM if you add additional steps to the workflow. The name will be converted back to the Source, Target, or Transfer ID at deployment time automatically.
The plugin defaults to exporting Common Attributes like the UI would:
.
You can export with All Attributes using the input "All ConfigPlan Attributes."
Target Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
MFT Server Host |
| Yes | The host name for MFT (e.g. |
MFT Server Port |
| Yes | The managed server port number for MFT.(e.g. The Server port will be used when creating the t3 or t3s connection to the server host. This property works in conjunction with the Use SSL flag. |
MFT Use SSL |
| No | If checked, t3s will be used to connect to the MFT server. Otherwise, a t3 connection will be used instead. The Server port will be used either way, so if you check use SSL, specify the SSL port there. |
Weblogic Admin Password |
| Yes | Weblogic Admin Password |
Weblogic Admin User |
| Yes | The |
username for the WLS admin server. | |||
Oracle Middleware Home (MW_HOME) |
| Yes | The oracle middleware home (which has subfolders such as |
...
Project Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
Rename After Export |
| No |
If checked, the artifacts will be renamed to the name of the artifact after |
exporting. See the paragraphs above for more information on how and when the artifacts are renamed. |
Inputs
...
Output Name
...
Required
...
Description
...
Input Name | Input Code | Required | Description |
|---|---|---|---|
Transfers To Export |
| No | Comma separated list of transfers to export. If left empty, all transfers will be exported. |
Outputs
All ConfigPlan Attributes |
| No | If checked, all attributes will be added to the config plan. Otherwise only Common attributes will be added. See the image above for information about where the setting is present in the UI. This input was added in version 5.0.1.8. Prior to that it defaulted to false, exporting only the key (common) options in the config plan. |
Artifacts
This operation doesn’t consume or produce any artifacts.
Endpoint Selection
This operation will select all available endpoints associated to the environment/instancedelegates the selection of endpoints to the workflow developer.
Endpoint Execution
This operation will execute on any one delegates the selection of any or all of the selected endpoints and will be random in the determination of which oneto be executed on to the workflow developer.