Installing IBM MQ
When you purchase a license for IBM® App Connect Enterprise, your license entitles you to install IBM MQ for use by App Connect Enterprise, within the terms of the license.
About this task
IBM MQ is fully supported by IBM App Connect Enterprise, and a subset of IBM App Connect Enterprise capabilities require access to IBM MQ components.
- Some capabilities require IBM MQ to be part of the IBM App Connect Enterprise infrastructure, and you must associate a queue manager with the integration server.
- Some capabilities do not require IBM MQ to be part of the IBM App Connect Enterprise infrastructure, and you do not always need to associate a queue manager with the integration server.
- Some capabilities require access to IBM MQ, either locally or on a remote server.
Capabilities that require IBM MQ to be part of the IBM App Connect Enterprise infrastructure:
For these capabilities, you must install an IBM MQ server on the same machine as the integration server that is to use the capabilities, and you must associate a queue manager with the integration server or integration node by setting the defaultQueueManager configuration property. For more information, see Configuring an integration server by modifying the server.conf.yaml file. Configuring an integration node by modifying the node.conf.yaml file, and Features, scenarios, and message flow nodes that require a local IBM MQ server and queue manager.
Multiple integration nodes can specify the same queue manager, but deploy issues can occur if an attempt is made to reuse a unique endpoint suffix when two different integration nodes share a queue manager and use the integration node listener.
For some capabilities, you must also complete additional configuration actions indicated in the "Additional configuration notes" column:
Capability | Detail | Additional configuration notes |
---|---|---|
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 App Connect Enterprise queues on your queue manager; see Creating the default system queues on an IBM 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 App Connect Enterprise queues on your queue manager; see Creating the default system queues on an IBM MQ queue manager. |
Global coordination of transactions (XA) | You are using globally-coordinated (XA) transactions. |
Capabilities that do not require IBM MQ to be part of the infrastructure for your IBM App Connect Enterprise deployment:
For these capabilities, you must install either an IBM MQ client or an IBM MQ server on the same machine as the integration server or integration node that is to use the capabilities, but you do not need to associate a queue manager with the integration server or integration node unless specified in the "Additional configuration notes" column:
Capability | Detail | Additional configuration notes |
---|---|---|
Java™ connectivity and JDBC | You have one of the following nodes in your message flows: |
Capabilities that require access to IBM MQ, either locally or on a remote server:
For these capabilities, you must install an IBM MQ client or server either on the same machine as the integration server or on another machine that can be accessed through a client connection:
Capability | Detail | Additional configuration notes |
---|---|---|
IBM MQ connectivity | You have any of the following nodes in your message flows: | You need to specify a queue manager on the integration server or integration node only if you want to use the queue manager by default for your MQ connection. For more information, see Configuring a local connection to IBM MQ and Using a remote default queue manager. |
Advanced data processing | You have any of the following nodes in your message flows: | You must create the set of IBM App Connect Enterprise queues on your queue
manager, as described in Creating the default system queues on an IBM MQ queue manager. You must configure the default queue manager by setting either the defaultQueueManager or remoteDefaultQueueManager property. For more information, see Processing events. An integration server that supports this capability must not share a queue manager with another integration server unless a unique queue prefix is set. You set a unique queue prefix either by using a policy or, if a remote default queue manager is being used, by setting the replacementQueuePrefix property. For more information, see Configuring an integration server to use a remote default queue manager. For TimeoutNotification nodes
using |
Publish and subscribe | You are using publish and subscribe capabilities to emit events or accounting and
statistics data over IBM MQ and MQTT. For more information, see Configuring the publication of event messages. |
By default, events use the queue manager that is associated with the integration server or integration node. However, you can use a policy to configure 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 server or integration node, or use
a SAPConnection policy and specify a CCDT through the Shared TID store client definition
file property. The remoteDefaultQueueManager setting does not apply to these nodes, but the CCDT can specify a remote queue manager to achieve the same effect. |
Procedure
- To install IBM MQ components, see the IBM MQ product documentation: http://www.ibm.com/support/knowledgecenter/SSFKSJ_8.0.0/com.ibm.mq.ins.doc/q008250_.htm.
- For capabilities listed in Capabilities that require IBM MQ to be part of the IBM App Connect Enterprise infrastructure, associate a queue manager with the integration server or integration node that is to use the capabilities.
- Complete any additional configuration actions for the capability that you want to use, as indicated in the "Additional configuration notes" column of the tables above.