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.
Run IBM MQ Managed File Transfer agents in a container .
See here for an earlier implementation of MFT on cloud.
See the Run as Docker container documentation for details on how to run the image docker container.
See the Run in OCP documentation for details on how to run the image in 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 toview
. - 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
andverbose
are the supported values withinfo
being default. Contents of agent's output0.log is displayed if MFT_LOG_LEVEL is set toverbose
.
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
See the instructions here to build your own agent container image.
Step-by-step guide to using agent container.
- Private key and trust stores are not yet supported for Protocol Bridge Agents. Hence only a userid and password combination must be used for connecting to FTP/SFTP/FTPS servers.
For issues relating specifically to the container image or Helm chart, please use the GitHub issue tracker. If you do submit a Pull Request related to this Docker 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, 2021