Why use IBM MQ instead of Kafka or RabbitMQ?

IBM MQ is the canonical choice when your environment is built around enterprise messaging guarantees: transactional integrity, ordered delivery, message expiry handling, dead-letter queues, and integration with mainframe and middleware systems. Kafka is better for high-throughput event streaming; RabbitMQ is better for lightweight routing patterns. IBM MQ is right when you need its specific semantics — typically in financial services, insurance, healthcare, or mainframe-adjacent workloads.

Can on-premise IBM MQ applications talk to IBM MQ on Cloud?

Yes — that's a primary use case. You configure channels on both ends and they federate. Migration from on-premise to cloud typically starts with hybrid: cloud queue manager federated with on-premise, applications gradually shift their client connections. The MQSC dialect is identical.

IBM MQ on Cloud Config Builder

ServerlessIBM Cloud

Build IBM MQ on Cloud configurations with queue managers, queues, channels, topics, and subscriptions.

Last verified: May 2026

IBM MQ on Cloud Configuration

Build IBM MQ on Cloud configurations with queue managers, queues, channels, topics, subscriptions, and user permissions.

Required Fields

instanceNamequeueManagersqueueManagers[0].name

{
  "instanceName": "prod-mq-instance",
  "plan": "default",
  "region": "us-south",
  "resourceGroup": "prod-resources",
  "version": "9.3",
  "queueManagers": [
    {
      "name": "PROD_QM1",
      "size": "medium",
      "location": "us-south",
      "highAvailability": true,
      "queues": [
        {
          "name": "ORDER.REQUEST",
          "type": "local",
          "maxDepth": 50000,
          "maxMessageLength": 4194304,
          "persistence": "persistent",
          "deadLetterQueue": "ORDER.REQUEST.DLQ"
        },
        {
          "name": "ORDER.RESPONSE",
          "type": "local",
          "maxDepth": 50000,
          "persistence": "persistent"
        },
        {
          "name": "ORDER.REQUEST.DLQ",
          "type": "local",
          "maxDepth": 100000,
          "persistence": "persistent"
        }
      ],
      "channels": [
        {
          "name": "APP.TO.QM1",
          "type": "SVRCONN",
          "sslCipherSpec": "ANY_TLS12_OR_HIGHER",
          "maxInstances": 100,
          "authenticationMethod": "token"
        }
      ],
      "topics": [
        {
          "name": "ORDER/EVENTS",
          "topicString": "order/events",
          "maxMessageLength": 1048576,
          "durable": true
        }
      ],
      "subscriptions": [
        {
          "name": "ORDER_ANALYTICS_SUB",
          "topicString": "order/events",
          "destination": "ORDER.ANALYTICS.QUEUE"
        }
      ]
    }
  ],
  "networking": {
    "privateEndpoint": true,
    "publicEndpoint": true,
    "tlsVersion": "1.2"
  },
  "users": [
    {
      "name": "app-user",
      "permissions": [
        { "type": "queue", "name": "ORDER.*", "access": "readwrite" },
        { "type": "topic", "name": "ORDER/**", "access": "subscribe" }
      ]
    }
  ]
}

Generated Output

Output will appear here...

About This Tool

IBM MQ on Cloud is the managed version of IBM's enterprise messaging product — queue managers, queues, channels, topics, and subscriptions, with the same guarantees as on-premise IBM MQ. The IBM MQ on Cloud Config Builder generates queue manager configurations and the associated queue, channel, topic, and subscription objects. Output covers both Terraform resources and the MQSC scripts your application teams will use.

Real-World Scenario

A bank's enterprise integration team is migrating off-mainframe applications to IBM Cloud, but they need IBM MQ semantics for transactional integrity. You spec out an MQ on Cloud queue manager with the same queue and channel structure as the existing on-premise setup. After provisioning, applications are migrated client-by-client to point at the cloud queue manager. The on-premise MQ stays online during transition and is decommissioned only after all applications cut over.

When to Use This Tool

•Provisioning a queue manager for a new application that needs IBM MQ semantics — guaranteed delivery, ordered messages, transactional persistence.
•Adding queues to an existing queue manager for a new service integration with the right message persistence and queue depth limits.
•Setting up a topic-based publish/subscribe configuration for an event distribution pattern.
•Configuring server-connection channels with proper TLS and authentication for client applications.

Pro Tips

TIP

Set queue depth limits appropriate to your downstream consumer's processing rate. Unbounded queue depth invites runaway storage usage during a consumer outage.

TIP

Use distinct queue managers for distinct trust domains. Sharing a queue manager between two organizations or two compliance scopes creates audit headaches; the cost of an extra queue manager is small compared to the cost of co-locating workloads that shouldn't be.

How It Works Under the Hood

The builder collects queue manager name, region, plan, and a list of queues, topics, and channels with their attributes (persistence, max depth, TLS settings). Output covers both Terraform resources (for the queue manager itself and the MQ on Cloud service binding) and MQSC scripts that the application team applies to define queues, topics, channels, and subscriptions.

Frequently Asked Questions

Why use IBM MQ instead of Kafka or RabbitMQ?: IBM MQ is the canonical choice when your environment is built around enterprise messaging guarantees: transactional integrity, ordered delivery, message expiry handling, dead-letter queues, and integration with mainframe and middleware systems. Kafka is better for high-throughput event streaming; RabbitMQ is better for lightweight routing patterns. IBM MQ is right when you need its specific semantics — typically in financial services, insurance, healthcare, or mainframe-adjacent workloads.
Can on-premise IBM MQ applications talk to IBM MQ on Cloud?: Yes — that's a primary use case. You configure channels on both ends and they federate. Migration from on-premise to cloud typically starts with hybrid: cloud queue manager federated with on-premise, applications gradually shift their client connections. The MQSC dialect is identical.

Was this tool helpful?

Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.