Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Panel

Table of Contents

...

Template NameExtension NameExtension Version
UDMG File Transferue-mft-transfer1.3.1

Refer to the changelog Changelog for version history information.

...

  • Universal Agent for Windows x64 Version 7.3.0.0 and later with python Python options installed.
  • Universal Agent for Linux Version 7.3.0.0 and later with python Python options installed.

Software Requirements for Universal Controller

...

FieldInput typeDefault valueTypeDescription
ActionRequiredPUTChoiceAction performed upon the task execution.
Available actions:
  • GET
  • PUT
  • MGET
  • MPUT
  • LIST
ProtocolRequiredSFTPChoice
The transfer protocol.
Available values:
  • SFTP
  • HTTP
  • HTTPS
  • PeSIT
  • PeSIT-TLS
Note
titleNote

The protocol serves as a filter for the Partner list. The actual protocol for the file transfer is the one that is configured on UDMG for the selected Partner


MFT ServerRequired-TextUDMG Server URL. This is the URL for the REST API endpoint, the port is configured in the UDMG Server configuration file.
For example: http://udmg.stonebranch.com:8080/api
MFT CredentialsRequired-CredentialsUDMG Server Credentials. The Credentials definition should be as follows.
  • User Name as "Runtime User".
  • User Password as "Runtime Password".
The user must have read permissions for rules and partners, read/write permission for transfers
Source FileRequired-TextThe name of the source file, or the search pattern:
  • PUT: local file
  • GET: remote file
  • MPUT: wildcard pattern for local files
  • MGET: wildcard pattern for remote files
  • LIST: wildcard pattern for remote files

Target File

Introduced in version 1.1.0

Optional-TextThe name of the file on the target system after the transfer,
  • PUT: remote file
  • GET: local file
  • MPUT/MGET/LIST: not used, the field is not displayed.
PartnerRequired-Dynamic ChoiceDynamically fetched list of partner names.
The list is restricted to the partners that support the selected Protocol. The user can select the required partner name from a drop-down list.
RuleRequired-Dynamic ChoiceDynamically fetched list of transfer rules.
The list is restricted to the rules that are assigned to the selected Partner. The user can select the required rule from a drop-down list.
Partner AccountRequired-TextThe name of the account to use for the connection to the selected Partner.
The account credentials are configured on UDMG.

Wait for Transfer Completion

Introduced in version 1.2.0

RequiredTrueBoolean

By checking this field, the extension monitors the completion of the transfer on UDMG before completing its execution.

  • Actions PUT/GET: Wait for the single transferred transfer to be completed.

  • Actions MPUT/MGET/LIST: Wait for the child file transfers to be completed or not. The extension will always wait for the parent process to be completed successfully, regardless of this configuration attribute.

Polling Interval

Optional5IntegerThe amount of time (in seconds) the task will wait before polling to check the transfer status.
Valid values from 1.

Max Files to Monitor

Introduced in version 1.2.0

Required100Integer

The number of files, above which no monitor will be done, apart from the successful trigger of the file transfer.

In practice, this means that for the actions MGET & MPUT, if a wildcard transfer results in more child transfers than the number indicated, the extension will not check the transfer status of these files, and proceed to completion with a special return code (see corresponding section in this document).

Task Examples

...

Image Added

Image Added

Scenario A

Example for sending a file to a HTTPS server.

...

Scenario A

The partner configuration on UDMG

...

Image Removed

...

.

Image AddedImage Added

Scenario B

Example for downloading a file from an SFTP server.

...

Scenario B

The partner configuration on UDMG

...

Image Removed

...

.

Image AddedImage Added

Scenario C

Example for downloading multiple files from an SFTP server.

Image Removed

...

Scenario D

Example for listing files from an SFTP server.

Image Removed

Task Execution

Dynamic Commands

Command NameAllowed Task Instance StatusDescription
PauseRUNNING

Issue the pause command on the UDMG transfer.

For a wildcard transfer (MPUT or MGET), the pause command is issued for all child transfers on UDMG. Only the eligible children, in status PLANNED or RUNNING, are considered. Failure on one transfer does not block the execution for of the other transfers.

ResumeRUNNING

Issue the resume command on the UDMG transfer.

For a wildcard transfer (MPUT or MGET), the resume command is issued for all child transfers on UDMG. Only the eligible children, in status INTERRUPTED or PAUSED, are considered. Failure on one transfer does not block the execution for of the other transfers.

Cancelation

...

  • If the transfer has no children (PUT, GET, LIST action):

    • Fetch the UDMG transfer status and update the output-only fields.

    • Proceed to resume the UDMG transfer only when its status is ERROR, otherwise

    • Continute Continue the monitoring until the UDMG transfer is completed.

  • If the transfer has children (MPUT, MGET action): resume the execution of all of the eligible child transfers on UDMG (in status  ERROR). Failure on one transfer does not block the execution for the other transfers.

...

FieldTypeDescription
Transfer IDTextThe identifier of the transfer on UDMG.
Transfer StatusText

The current status of the transfer.
One of PLANNED, RUNNING, PAUSED, INTERRUPTED, DONE, CANCELLED or ERROR.

Used for Task instance Extension Status.

Transfer Start TimeTextThe date and time the transfer has started (UDMG Server time).
Transfer End TimeText

The date and time the transfer has ended (UDMG Server time).

For a wildcard transfer, this is when the listing of matching files and the registration of the child transfers is completed.

Transfer StepTextThe current processing step of the transfer.
One of NONE, PRE TASKS, DATA, POST TASKS, ERROR TASKS or FINALIZATION.

Transfer Progress

Modified in version 1.2.0

TextThe progress of the data transfer in in human-readable format.
  • size in KB, MB, or GB for a Single Transfer,.
  • "x out of y files" for a Wildcard Transfer.
Error CodeText

The UDMG transfer error code.

See the table below.

Error MessageTextThe error message (if an error occurred).
Transfer Task NumberTextThe task number of the task in the processing step.
Only for the Transfer Steps 'PRE TASKS', 'POST TASKS', and 'ERROR TASKS'.
Local FileTextLocal file path.
Remote FileTextRemote file path.

Transfer UUID

Introduced in version 1.1.0

TextThe UUID of the transfer on UDMG.

These fields are also available as task instance variables, with the ops_mft_ prefix:

...

Error CodeDescription
TeOkThis is the code used by default. It indicates that there is no error
TeUnknownIndicates an unknown error (the details of the error can give more information).
TeInternal

Indicates that an internal error occurred in the UDMG Server (lost connection to the database, etc.)

TeUnimplementedIndicates that the partner wanted to use a valid functionality, but which is not implemented by the UDMG Server.
TeConnectionIndicates that the connection to a remote partner cannot be established. This is the most general error code. A more specific code, if available, should be used.
TeConnectionResetMeans "connection reset by peer"
TeUnknownRemoteIndicates that the requested remote partner is not known in the UDMG Server database. For security reasons, the external use of this error code (returning this error to a client) is discouraged for incoming connections in favor of TeBadAuthentication, at the risk of leaking information (here, the account exists, but authentication failed).
TeExceededLimitIndicates that the transfer cannot be processed because the defined limits have been reached (number of connections, number of transfers, etc.)
TeBadAuthenticationIndicates a connection error caused by incorrect authentication data (user, password, certificate, etc. Details of the error can provide more information).
TeDataTransferIndicates that an error occurred during data transfer. This is a general error and a more specific code, if available, should be used.
TeIntegrityIndicates that the integrity check has failed.
TeFinalizationIndicates that an error occurred during the finalization of the transfer.
TeExternalOperationIndicates that an error occurred during the execution of pre-transfer, post-transfer, or error processing.
TeStoppedIndicates that the transfer was stopped.
TeCancelledIndicates that the transfer was cancelledcanceled.
TeFileNotFoundIndicates that the requested file was not found.
TeForbiddenIndicates that the remote partner is not allowed to perform an action.
TeBadSizeIndicates an error related to the size of the file (it exceeds a quota, there is not enough space left on the destination disk, etc.)
TeShuttingDownIndicates that the UDMG Server is shutting down

...

Exit CodeStatus Classification CodeStatus Classification DescriptionStatus Description
0SUCCESSSuccessful ExecutionSUCCESS
1FAILFailed ExecutionFAIL: < Error Description >
2AUTHENTICATION_ERRORBad credentialsCredentialsAUTHENTICATION_ERROR: Account cannot be authenticated.
3AUTHORIZATION_ERRORInsufficient PermissionsAUTHORIZATION_ERROR: Account is not authorized to perform the requested action.
10CONNECTION_ERRORBad connection data or connection timed outCONNECTION_ERROR: < Error Description >
11CONNECTION_ERRORExtension-specific connection errorCONNECTION_ERROR: 404 page not found
20DATA_VALIDATION_ERRORInput fields Validation ErrorDATA_VALIDATION_ERROR: 400 bad request:
21TRANSFER_STATUS_ERRORTransfer Execution ErrorTRANSFER_STATUS_ERROR: Transfer failed with error code: TeUnknown
22TRANSFER_STATUS_ERRORTransfer Execution ErrorTRANSFER_STATUS_ERROR: Transfer failed with error code: TeInternal
23TRANSFER_STATUS_ERRORTransfer Execution ErrorTRANSFER_STATUS_ERROR: Transfer failed with error code: TeUnimplemented
24TRANSFER_STATUS_ERRORTransfer Execution ErrorTRANSFER_STATUS_ERROR: Transfer failed with error code: TeConnection
25TRANSFER_STATUS_ERRORTransfer Execution ErrorTRANSFER_STATUS_ERROR: Transfer failed with error code: TeConnectionReset
26TRANSFER_STATUS_ERRORTransfer Execution ErrorTRANSFER_STATUS_ERROR: Transfer failed with error code: TeUnknownRemote
27TRANSFER_STATUS_ERRORTransfer Execution ErrorTRANSFER_STATUS_ERROR: Transfer failed with error code: TeExceededLimit
28TRANSFER_STATUS_ERRORTransfer Execution ErrorTRANSFER_STATUS_ERROR: Transfer failed with error code: TeBadAuthentication
29TRANSFER_STATUS_ERRORTransfer Execution ErrorTRANSFER_STATUS_ERROR: Transfer failed with error code: TeDataTransfer
30TRANSFER_STATUS_ERRORTransfer Execution ErrorTRANSFER_STATUS_ERROR: Transfer failed with error code: TeIntegrity
31TRANSFER_STATUS_ERRORTransfer Execution ErrorTRANSFER_STATUS_ERROR: Transfer failed with error code: TeFinalization
32TRANSFER_STATUS_ERRORTransfer Execution ErrorTRANSFER_STATUS_ERROR: Transfer failed with error code: TeExternalOperation
33TRANSFER_STATUS_ERRORTransfer Execution ErrorTRANSFER_STATUS_ERROR: Transfer failed with error code: TeWarning
34TRANSFER_STATUS_ERRORTransfer Execution ErrorTRANSFER_STATUS_ERROR: Transfer failed with error code: TeStopped
35TRANSFER_STATUS_ERRORTransfer Execution ErrorTRANSFER_STATUS_ERROR: Transfer failed with error code: TeCancelled
36TRANSFER_STATUS_ERRORTransfer Execution ErrorTRANSFER_STATUS_ERROR: Transfer failed with error code: TeFileNotFound
37TRANSFER_STATUS_ERRORTransfer Execution ErrorTRANSFER_STATUS_ERROR: Transfer failed with error code: TeForbidden
38TRANSFER_STATUS_ERRORTransfer Execution ErrorTRANSFER_STATUS_ERROR: Transfer failed with error code: TeBadSize
39TRANSFER_STATUS_ERRORTransfer Execution ErrorTRANSFER_STATUS_ERROR: Transfer failed with error code: TeShuttingDown
90CHILD_TRANSFERS_NOT_MONITORED_WARNINGAPI LimitationsCHILD_TRANSFERS_NOT_MONITORED_WARNING: Too many child transfers, skipped monitoring their completions completion status
100TRANSFER_STATUS_CANCELUnexpected Transfer StatusTRANSFER_STATUS_CANCEL: Unexpected CANCELLED status

...

The Extension output contains the attribute result which contains the following sub-attributes:

AttributeTypeDescription
mft_transferobjectThe details of the main transfer record (the single transfer or the parent transfer in case of Wildcard Transfer).
mft_transfer.transfer_idstringThe identifier of the transfer on UDMG.
mft_transfer.statusstringThe current status of the transfer
One of PLANNED, RUNNING, PAUSED, INTERRUPTED, DONE, CANCELLLED CANCELED or ERROR.
mft_transfer.startstringThe date and time the transfer has started (UDMG Server time)
mft_transfer.stopstring

The date and time the transfer has ended (UDMG Server time).

For a wildcard transfer, this is when the listing of matching files and the registration of the child transfers is completed.

mft_transfer.stepstringThe current processing step of the transfer
One of NONE, PRE TASKS, DATA, POST TASKS, ERROR TASKS or FINALIZATION.
mft_transfer.transfer_progresstextThe progress of the data transfer in in human-readable format
  • size in KB, MB, or GB for a Single Transfer,
  • "x out of y files" for a Wildcard Transfer.
mft_transfer.error_codestringThe error code of the transfer (if an error occurred).
mft_transfer.error_msgstringThe error message (if an error occurred).
mft_transfer.task_numberstringThe task number of the task in the processing step.
Only for the steps 'PRE TASKS', 'POST TASKS', and 'ERROR TASKS'.
mft_transfer.local_filestringLocal file path.
mft_transfer.remote_filestringRemote file path.

mft_transfer.transfer_uuid

Introduced in version 1.1.0

stringThe UUID of the transfer on UDMG.

mft_transfer.transfer_info

Introduced in version 1.1.0

object

The transfer information fields. 

Set of metadata associated to with the transfer on the UDMG Server.

The fields Fields with the udmg_ prefix are set internally by the UDMG server.

The fields Fields with the udmg_ue prefix are set by the UDMG File Transfer task.

mft_transfer.transfer_info.udmg_ue_task_uuid

Introduced in version 1.2.0

stringThe UUID of the UDMG File Transfer task.
It can be used to easily correlate the UC task executions and the corresponding UDMG file transfers.

mft_transfer.transfer_info.udmg_xfer_wildcard

Introduced in version 1.2.0

boolean

Indicator that this is a wildcard transfer.

Only for MPUT and MGET.

mft_transfer.transfer_info.udmg_xfer_cmd

Introduced in version 1.3.0

string

'list' is and an indicator that this is a wildcard list command.

Only for LIST.

mft_transfer.transfer_info.udmg_xfer_childIDs

Introduced in version 1.2.0

array

A list of UDMG transfer IDs that are created in the context of this file file transfer. For each file matched matching the filename input, one file transfer process is created in UDMG.

Only for MPUT and MGET.

mft_transfer.transfer_info.udmg_xfer_files

Introduced in version 1.2.0

array

The list of files that matched the user input. Each of these files is transferred with a separate file transfer execution, which transfer ids IDs can be found in “udmg_xfer_childIDs“ list.

Only for MPUT and MGET.

mft_transfer_files_summary

Introduced in version 1.2.0

objectSummary counters
mft_transfer_files_summary.donenumberNumber of file transfers with success.
mft_transfer_files_summary.errornumberNumber of file transfers in error state.
mft_transfer_files_summary.cancellednumberNumber The number of file transfers that are cancelledcanceled.

errors

Introduced in version 1.2.0

arrayList of errors for the child transfers.

An example of the Extension Output for an a single download from SFTP is presented below.

...

An example of the Extension Output for an a wildcard download from SFTP with 3 matching files is presented below.

...

An example of the Extension Output for an a wildcard list from SFTP with 2 matching files is presented below.

...

STDERR provides additional information to User the user about the task instance execution. Verbosity is increased with the Task Log Level, The Debug and Trace levels can lead to extensive details and is only recommended for troubleshooting.

...

FieldDescription
idThe identifier of the transfer on UDMG
status

The current status of the transfer
One of PLANNED, RUNNING, PAUSED, INTERRUPTED, DONE, CANCELLLED, or ERROR

localFilepathThe path of the file on the local disk
startThe date and time the transfer has started (UDMG Server time)
stop

The date and time the transfer has ended (UDMG Server time)

filesizeThe size of the file in byte bytes (or -1 when unknown)
progressThe progress of the data transfer in bytes
remoteIDThe UUID of the transfer on UDMG
errorCodeThe UDMG transfer error code.
errorMessageThe error message (if an error occurred)

step

The current processing step of the transfer
One of NONE, PRE TASKS, DATA, POST TASKS, ERROR TASKS or FINALIZATION
taskNumberThe task number of the task in the processing step.
Only for the Transfer Steps 'PRE TASKS', 'POST TASKS', and 'ERROR TASKS'
remoteFilepathThe path to the file on the remote partner
ruleThe name of the transfer rule
isSendIndicates whether the transfer is a send (true) or a receive (false)
requestedThe name of the server/partner that requested the transfer
requesterThe name of the account that requested the transfer

An example of the STDOUT for an a wildcard download from SFTP with 3 matching files is presented below.

...

An example of the STDOUT for an a wildcard list from SFTP with 2 matching files is presented below.

...

  • Python code modifications should not be done.
  • Template Modifications
    • General Section

      • "Name", "Extension", "Variable Prefix", and "Icon" should not be changed.
    • Universal Template Details Section

      • "Template Type", "Agent Type", "Send Extension Variables", and "Always Cancel on Force Finish" should not be changed.
    • Result Processing Defaults Section

      • Success and Failure Exit codes should not be changed.
      • Success and Failure Output processing should not be changed. 
        • Success/Failure exit codes need to be respected.
        • In principle, as STDERR and STDOUT outputs can change in follow-up releases of this integration, they should not be considered as a reliable source for determining the success or failure of a task.

          Fields Restriction Section
          The setup of the template does not impose any restrictions, However with respect to . However, concerning the "Exit Code Processing Fields" section .

...

Document References

This document references the following documents.

Document LinkDescription
Universal TemplatesUser documentation for creating, working with, and understanding Universal Templates and Integrations.
Universal TasksUser documentation for creating Universal Tasks in the Universal Controller user interface.
CredentialsUser documentation for creating and working with credentials.
Resolvable Credentials Permitted PropertyUser documentation for Resolvable Credentials Permitted Property.

Anchor
Changelog
Changelog

Changelog

ue-mft-transfer-1.3.1 (2024-xx-xx)

Enhancements

  • Added: Compatibility with Python 3.11 (#35935).

ue-mft-transfer-1.3.0 (2023-09-29)

...

  • Breaking Change: "Polling Interval" minimum value is set to 1, a value of 0 could cause an infinite loop (#33815).

Enhancements

  • Added: new LIST action to retrieve the names of the files matching a wildcard pattern on a remote SFTP partner (#33358).
  • Added: Logging of dynamic command processing in the agent log with TRACE level (#32993).
  • Added: MGET/MPUT: error is raised when monitoring of child transfers is skipped because the list is greater than "Max Files To Monitor": CHILD_TRANSFERS_NOT_MONITORED_WARNING with exit code 90 (#33065).
  • Added: Support for throttling the MGET/MPUT monitoring with the environment variable UDMG_CLIENT_MAX_THROTTLE_RATE. It sets the maximum number of calls per second to the UDMG API during the monitoring phase. Default is 60 (#33432).
  • Changed: "Target File" only visible for GET & PUT actions (#33367).
  • Changed: After a dynamic command, the extension will terminate immediately if the transfer is already completed (#32989).
  • Changed: "Polling Interval" field is always visible, as it is still used to check for parent transfer completion (#32994).
  • Changed: MGET/MPUT: "Transfer Progress" is only updated when a child transfer is completed (DONE, ERROR, CANCELLED) (#33815).
  • Changed: Sorting of the "Action" list (#33064).

...

  • Breaking Change: Transfer Progress output only field is changed to text value (#32195)

Enhancements

  • AddSupport Wildcard Transfer (#32198, #32195, #32201)
    1. New actions "MPUT" and "MGET" for wildcard transfers:
      • support for wildcard in source file parameter,
      • creation of wildcard transfer on UDMG,
      • monitoring of child transfers on UDMG,
      • tabular report on STDOUT with final child transfer status,
      • short summary report in EXTENSION output,
      • PAUSE, RESUME, and CANCEL commands are propagated to child transfers
    2. "Transfer Progress" output field is redefined to show human readable value
      • size in KB, MB, or GB for single transfer,
      • "x out of y files" for wildcard transfer
    3. "Max files to monitor" parameter: limit the number of child transfers that are monitored by the task instances, 100 by default.
    4. "Wait for transfer completion" parameter: task instance only returns when the transfer is completed (with DONE or CANCELLED status) on UDMG.
      For wildcard transfers, only returns when all child transfers are completed. Activated by default.
  • Add: Refresh task instance output with re-run (#32463)
  • AddKeep UC task instance ID in UDMG file transfer metadata field udmg_ue_task_uuid (#30931)

ue-mft-transfer-1.1.0 (2023-01-31)

...

  • Breaking Change: minimum universal agent version set to 7.3

Enhancements

  • Addset target filename (rename file) (#31174)
  • Add: transfer status as UC 7.3 extension status field. (#31041)
  • Add: retry failed transfer with Task Re-run. (#29599)
  • Add: show UUID. (#30733)
  • Add: show transfer info fields. (#30930)
  • Add: support for PeSIT and PeSIT-TLS protocols (#31051)

...