IBM MQ Managed File Transfer transfers files between systems in a managed and auditable way, regardless of file size or the operating systems used. You can use Managed File Transfer to build a customized, scalable, and automated solution that enables you to manage, trust, and secure file transfers. Managed File Transfer eliminates costly redundancies, lowers maintenance costs, and maximizes your existing IT investments.

IBM MQ Managed File Transfer agent is now available as a container image also in IBM Container Registry (icr.io/ibm-messaging/mqmft). The image can be deployed in a OpenShift Cluster as a standard deployment or running using podman runtime.

It must be noted the IBM MQ Managed File Transfer agent image is a Developer Only image and hence must not be used in production environment.

See here for an earlier implementation of MFT on cloud.

See here for details on how to run the image container with Podman runtime.

See here for details on how to deploy the image in an OpenShift Container Platform.

Note that in order to use the image, it is necessary to accept the terms of the IBM MQ license.

• LICENSE - Required. Set this to accept to agree to the MQ Advanced for Developers license. If you wish to see the license you can set this to view.
• MFT_AGENT_CONFIG_FILE - Required. Path of the json file containing information required for setting up an agent. The path must be on a mount point. For example a configMap on OpenShift. See the agent configuration doc for a detailed description of attributes.
• MFT_AGENT_NAME - Required. Name of the agent to configure.
• BFG_JVM_PROPERTIES - Optional - Any JVM property that needs to be set when running agent JVM.
• MFT_LOG_LEVEL - Optional - Level of information displayed. info and verbose are the supported values with info being default. Contents of agent's output0.log is displayed if MFT_LOG_LEVEL is set to verbose.
• MFT_AGENT_TRANSFER_LOG_PUBLISH_CONFIG_FILE - Optional - Publishing transfer logs to logDNA. Specify a JSON file containing URL and injestion key. See here for more details on the json structure.
• MFT_AGENT_START_WAIT_TIME - Optionl. An agent might take some time to start after fteStartAgent command is issued. This is the time, in seconds, the containor will wait for an agent to start. If an agent does not within the specified wait time, the container will end.
• MFT_MOUNT_PATH - Optional. Environment variable pointing to path from where agent will read files or write to.
• SFTP_EITHER_PRIVATEKEY_OR_PASSWORD - Optional - Defaults to "False". When set to "True", logs an error if both Private Key and Password are specified for a SFTP authentication.

Agent in the container will create agent configuration and log files under the fixed directory /mnt/mftdata. This folder can be on a persistent volume as well, in which case the volume must be mounted as /mnt/mftdata mount point in to the container

1. The image built with MQ 9.4.4 Managed File Transfer Redistributable binaries.
2. Fixes for issue(s) found in internal testing and reported from field via public git issues.

For issues relating specifically to the container image, please use the GitHub issue tracker. If you do submit a Pull Request related to this container image, please indicate in the Pull Request that you accept and agree to be bound by the terms of the IBM Contributor License Agreement.

The Dockerfiles and associated code and scripts are licensed under the Apache License 2.0. Licenses for the products installed within the images are as follows:

• IBM MQ Advanced for Developers (International License Agreement for Non-Warranted Programs). This license may be viewed from an image using the LICENSE=view environment variable as described above or by following the link above.
• IBM MQ Advanced (International Program License Agreement). This license may be viewed from an image using the LICENSE=view environment variable as described above or by following the link above.

Note: The IBM MQ Advanced for Developers license does not permit further distribution and the terms restrict usage to a developer machine.

© Copyright IBM Corporation 2020, 2025