IBM MQ MFT Agent for Developers container image

A prebuilt container image is available for IBM® MQ MFT Agent for Developers. The image published on IBM Container Registry (irc.io) can be used with Podman, Docker, and OpenShift® Container Platform environments.

Attention: IBM MQ MFT Agent for Developers images were previously available from Docker Hub, but this is deprecated, and no further updates are available on Docker Hub.

Available images

The latest version of IBM MQ MFT Agent for Developers is published on IBM Container Registry: icr.io/ibm-messaging/mqmft:latest

Quick reference

License:
- IBM MQ Advanced for Developers and Apache License 2.0. The IBM MQ Advanced for Developers license does not permit further distribution, and the terms restrict usage to a developer machine.
Where to file issues:
- GitHub
Available for the following platform:
- Linux® on amd64

Building a container image

See Building a container image for information on how to build your own agent container image with the IBM MQ Redistributable Managed File Transfer package on amd64 architectures.

Usage

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

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

To be able to use the image, you must accept the terms of the IBM MQ license by setting the LICENSE environment variable.

Environment variables

LICENSE: Set accept to agree to the IBM MQ Advanced for Developers license conditions.; Set view to view the license conditions.
MFT_AGENT_CONFIG_FILE: Required.; The path of the JSON file containing the information required for setting up an agent. The path must be on a mount point. For example, a configMap on OpenShift. See Additional MFT agent configuration files for a detailed description of the attributes.
MFT_AGENT_NAME: Required.; The name of the agent to configure.
BFG_JVM_PROPERTIES: Optional.; Any JVM property that needs to be set when running the agent JVM.
MFT_LOG_LEVEL: Optional.; The level of information displayed. The supported values are info and verbose. The default is info. Contents of agent's output0.log is displayed if MFT_LOG_LEVEL is set to verbose.
MFT_AGENT_START_WAIT_TIME: Optional.; An agent might take some time to start after the fteStartAgent command is issued. This is the time, in seconds, that the container waits for an agent to start. If an agent does not start within the specified wait time, the container ends.
MFT_MOUNT_PATH: Optional.; An environment variable pointing to the path from where the agent reads or writes files.
MFT_COORD_QMGR_CIPHER: Required.; The name of the CipherSpec to be used for securely connecting to the coordination queue manager.
MFT_CMD_QMGR_CIPHER: Required.; The name of the CipherSpec to be used for securely connecting to the command queue manager.
MFT_AGENT_QMGR_CIPHER: Required.; The name of the CipherSpec to be used for securely connecting to the agent queue manager.

For more information about the default developer configuration supported by the IBM MQ Advanced for Developers image, see the default developer configuration documentation.

Location of agent configuration files

The 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.