[OpenShift Container Platform][Kubernetes][IBM Cloud Pak for Integration]

IBM MQ Advanced for Developers container image

A prebuilt container image is available for IBM® MQ Advanced for Developers. This image is available from the IBM Container Registry. This image is suitable for use with Docker, Podman, Kubernetes, and other container environments.

[Deprecated]Note: IBM MQ Advanced for Developers images were previously available from Docker Hub, but this is deprecated, and no further updates are available on Docker Hub.

Available images

IBM MQ images are stored in the IBM Container Registry:

  • IBM MQ Advanced for Developers 9.3.0: icr.io/ibm-messaging/mq:9.3.0.10-r2

Quick reference

  • License:
  • Where to file issues:
  • Supported architectures (versions from IBM MQ Advanced for Developers 9.3.0.0):
    • amd64
    • s390x
    • ppc64le
  • Supported architectures (versions up to and including IBM MQ Advanced for Developers 9.2.5.0):
    • amd64
    • s390x

Usage

Run IBM MQ Advanced for Developers in a container.

See the usage documentation for details on how to run a container.

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 supported

LANG
Set the language you want the license to be printed in.
LICENSE
Set accept to agree to the IBM MQ Advanced for Developers license conditions.
Set view to view the license conditions.
[Deprecated]LOG_FORMAT
DEPRECATED: Superseded by MQ_LOGGING_CONSOLE_FORMAT.
Change the format of the logs that are printed to the container's stdout location.
Set basic to use a simple human-readable format. This is the default value.
Set json to use JSON format (one JSON object on each line).
MQ_ADMIN_PASSWORD
Change the password of the admin user.
Must be at least 8 characters long.
Default value is passw0rd.
MQ_APP_PASSWORD
Change the password of the app user.
If set, this causes the DEV.APP.SVRCONN channel to become secured and only allow connections that supply a valid user ID and password.
Must be at least 8 characters long.
Default value is blank (no password required) for IBM MQ clients, and passw0rd for HTTP clients.
MQ_DEV
Set false to stop the default objects being created.
MQ_ENABLE_METRICS
Set true to generate Prometheus metrics for your queue manager.
[MQ 9.3.2 Feb 2023]MQ_LOGGING_CONSOLE_SOURCE
Specify a comma-separated list of sources for logs that are mirrored to the container's stdout location.
Valid values are qmgr and web.
Default value is qmgr.
[MQ 9.3.2 Feb 2023]MQ_LOGGING_CONSOLE_FORMAT
Replaces LOG_FORMAT.
Change the format of the logs that are printed to the container's stdout location.
Set basic to use a simple human-readable format. This is the default value.
Set json to use JSON format (one JSON object on each line).
[MQ 9.3.2 Feb 2023]MQ_LOGGING_CONSOLE_EXCLUDE_ID
Specify a comma-separated list of message IDs for log messages that are excluded.
The log messages still appear in the log file on disk, but are not printed to the container's stdout location.
Default value is AMQ5041I,AMQ5052I,AMQ5051I,AMQ5037I,AMQ5975I.
MQ_QMGR_NAME
Set the name you want your queue manager to be created with.
[Deprecated]MQ_TLS_KEYSTORE
DEPRECATED: see Supplying TLS certificates.
Allows you to supply the location of a PKCS#12 keystore containing a single certificate that you want to use in both the web console and the queue manager.
Requires MQ_TLS_PASSPHRASE.
When enabled, the channels created are secured using the TLS_RSA_WITH_AES_128_CBC_SHA256 Cipher Spec. Note that you need to make the keystore available inside your container. You can do this by mounting a volume to your container.
[Deprecated]MQ_TLS_PASSPHRASE
DEPRECATED: see Supplying TLS certificates.
The passphrase for the keystore is referenced in MQ_TLS_KEYSTORE.

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