Planning an IBM MQ architecture

When planning your IBM® MQ environment, consider the support that IBM MQ provides for single and multiple queue manager architectures, and for point-to-point and publish/subscribe messaging styles. Also plan your resource requirements, and your use of logging and backup facilities.

Before you plan your IBM MQ architecture, familiarize yourself with the basic IBM MQ concepts. See IBM MQ Technical overview.

IBM MQ architectures range from simple architectures using a single queue manager, to more complex networks of interconnected queue managers. Multiple queue managers are connected together using distributed queuing techniques. For more information about planning single queue manager and multiple queue manager architectures, see the following topics:

[z/OS]On IBM MQ for z/OS® you can use shared queues and queue sharing groups to enable you to implement workload balancing, and your IBM MQ applications to be scalable and highly available. For information about shared queues and queue sharing groups, see Shared queues and queue sharing groups.

IBM MQ provides two different release models:
  • The Long Term Support (LTS) release is most suitable for systems requiring a long term deployment and maximum stability
  • The Continuous Delivery (CD) release is intended for systems which need to rapidly exploit the latest functional enhancements for IBM MQ.
Both release types are installed in the same way, but there are considerations relating to support and migration which you need to understand. See IBM MQ release types for further information.

For information about planning for multiple installations, storage and performance requirements, and use of clients, see the other subtopics.