IBM MQ Advanced for Developers container image

Available images

IBM MQ images are stored in the IBM Container Registry:

• IBM MQ Advanced for Developers 9.4.0.16: icr.io/ibm-messaging/mq:9.4.0.16-r2
• IBM MQ Advanced for Developers 9.4.4.0: icr.io/ibm-messaging/mq:9.4.4.0-r4

Quick reference

• License:
  • mq.ibm.com/v1beta1: Current license versions and Apache License 2.0. Note that 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 CPU architectures:
  • amd64
  • s390x
  • ppc64le

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

All of the environment variables from the IBM MQ Advanced container image are available, plus the following additional variables:

MQ_ADMIN_PASSWORD

Specify the password of the admin user.

Must be at least 8 characters long.

There is no default password for the admin user.

From IBM MQ 9.4.0, this variable is no longer provided. The example YAML in this topic shows how you can provide the admin password by mounting a secret.

MQ_APP_PASSWORD

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

There is no default password for the app user.

From IBM MQ 9.4.0, this variable is no longer provided. The example YAML in this topic shows how you can provide the app password by mounting a secret..

MQ_DEV

Set false to stop the default objects being created.

Example queue manager YAML that describes how to specify passwords for admin and app users

For users of the admin and app user IDs, you must provide passwords when deploying a queue manager using the Development license. Here is an example queue manager YAML that shows you how to do this with the IBM MQ Operator.

oc create secret generic my-mq-dev-passwords --from-literal=mqAdminPassword=passw0rd --from-literal=mqAppPassword=passw0rd

apiVersion: mq.ibm.com/v1beta1
kind: QueueManager
metadata: 
  name: qm-dev
  annotations: com.ibm.mq/write-defaults 
  spec: 'false'
spec:
  license:
    accept: true
    license: L-HYGL-6STWD6
    use: Development
  web:
    enabled: true  
  queueManager:
    env:
      - name: MQ_DEV
        value: "true"
      - name: MQ_CONNAUTH_USE_HTP
        value: "true"
    files:
      - secret:
          items:
            - item: mqAdminPassword
            - item: mqAppPassword
          name: my-mq-dev-passwords
          defaultMountPath: /run/secrets
    storage: 
      queueManager:
        type: persistent-claim
    name: QUICKSTART
  version: 9.4.4.0-r4