You can install IBM® MQ and use IBM MQ capabilities in IBM App Connect Enterprise.
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. This means that you must install an IBM MQ server on the same machine as your integration server, and you must associate a queue manager with the integration server, by setting the defaultQueueManager property in the integration server's server.conf.yaml configuration file. For more information about configuring your integration server, see Configuring an integration server by using the server.conf.yaml file.
The following capabilities require IBM MQ to be part of the infrastructure for your IBM App Connect Enterprise deployment:
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 App Connect Enterprise queues on your queue manager; see Creating the default system queues on a WebSphere MQ queue manager. An integration server that supports this capability must not share a queue manager with another integration server. |
Aggregation | 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; see Creating the default system queues on a WebSphere MQ queue manager. An integration server that supports this capability must not share a queue manager with another integration server. |
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; see Creating the default system queues on a WebSphere MQ queue manager. An integration server that supports this capability must not share a queue manager with another integration server. |
Managed file support | You have any of the following nodes in your message flows: | |
Accounting and statistics | You are using accounting and statistics by using the web user interface, and you are using IBM MQ rather than MQTT. | You must create the set of IBM App Connect Enterprise queues on your queue manager; see Creating the default system queues on a WebSphere MQ queue manager. |
Publish and subscribe | You have the following node in your message flows: |
Capability | Detail | Additional configuration notes |
---|---|---|
Java™ connectivity and JDBC | You have either of the following nodes in your message flows: | |
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 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 events over IBM MQ and over MQTT. | By default, integration server events use the queue manager that is associated with the integration server. 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 |
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.