Installing WebSphere MQ

You can install WebSphere® MQ and use WebSphere MQ capabilities in IBM® Integration Bus.

About this task

On distributed systems, WebSphere MQ is no longer a prerequisite for using IBM Integration Bus, which means that you can develop and deploy applications with IBM Integration Bus independently of WebSphere MQ. However, WebSphere MQ is still fully supported, and a subset of IBM Integration Bus capabilities require access to WebSphere MQ components.

The following capabilities require WebSphere MQ to be part of the infrastructure for your IBM Integration Bus deployment. Specifically, you must install a WebSphere MQ server on the same machine as your integration node, and you must associate a queue manager with the integration node:
Capability Detail Additional configuration notes
Flow control You have either of the following nodes in your message flows: You must create the set of IBM Integration Bus queues on your queue manager; see Creating the default IBM Integration Bus queues on a WebSphere MQ queue manager. An integration node that supports this capability must not share a queue manager with another integration node.
BPM support You use MQ bindings with any of the following nodes in your message flows:  
Record and replay   You must create the set of IBM Integration Bus queues on your queue manager; see Creating the default IBM Integration Bus queues on a WebSphere MQ queue manager.
Aggregation You have any of the following nodes in your message flows: You must create the set of IBM Integration Bus queues on your queue manager; see Creating the default IBM Integration Bus queues on a WebSphere MQ queue manager. An integration node that supports this capability must not share a queue manager with another integration node.
Advanced data processing You have any of the following nodes in your message flows: You must create the set of IBM Integration Bus queues on your queue manager; see Creating the default IBM Integration Bus queues on a WebSphere MQ queue manager. An integration node that supports this capability must not share a queue manager with another integration node.
Managed file support You have any of the following nodes in your message flows:  
High availability You have multi-instance integration nodes.  
High availability You are using the HTTP proxy servlet with your integration node. You must create the set of IBM Integration Bus queues on your queue manager; see Creating the default IBM Integration Bus queues on a WebSphere MQ queue manager.
Load balancing You are using an integration node listener (instead of embedded listeners) with your integration node. You must create the set of IBM Integration Bus queues on your queue manager; see Creating the default IBM Integration Bus queues on a WebSphere MQ queue manager.
Accounting and statistics You are using accounting and statistics by using the web user interface, and you are using WebSphere MQ rather than MQTT. You must create the set of IBM Integration Bus queues on your queue manager; see Creating the default IBM Integration Bus queues on a WebSphere MQ queue manager.
Publish and subscribe You have either of the following nodes in your message flows:  
The following table describes the IBM Integration Bus capabilities that do not require WebSphere MQ to be part of the infrastructure for your IBM Integration Bus deployment. Specifically, you must install either a WebSphere MQ client or a WebSphere MQ server on the same machine as the integration node, but you do not need to associate a queue manager with the integration node unless specified in the "Additional configuration notes" column:
Capability Detail Additional configuration notes
Java connectivity and JDBC You have either of the following nodes in your message flows:  
WebSphere MQ connectivity You have any of the following nodes in your message flows: You need to specify a queue manager on the integration node only if you want to use the queue manager by default for your local MQ connection. For more information, see Configuring a local connection to WebSphere MQ.
Publish and subscribe You are using publish and subscribe capabilities to emit integration node events (for example, monitoring, operational, or administration events) over WebSphere MQ and over MQTT. By default, integration node events use the queue manager that is associated with the integration node. However, you can use a policy to configure integration node events to use a different queue manager.
Transactional support for SAP You have any of the following nodes in your message flows: You must associate a queue manager with the integration node

To install WebSphere MQ components, see the WebSphere MQ product documentation: http://www.ibm.com/support/knowledgecenter/SSFKSJ_8.0.0/com.ibm.mq.ins.doc/q008250_.htm.