Features, scenarios, and message flow nodes that require a local IBM MQ server and queue manager

A summary of the features, scenarios, and message flow nodes in IBM® App Connect Enterprise where IBM MQ can be used only with a local IBM MQ server and queue manager.

When you use IBM MQ with IBM App Connect Enterprise, many tasks can be successfully run with either a local or a remote IBM MQ server and queue manager. The following tables contain summaries of the features, scenarios, and message flow nodes that can be run only with a local IBM MQ server and queue manager.
Table 1. Features that require a local IBM MQ server and queue manager
Scenario Comments
Integration node HTTP listener. The IBM MQ server and queue manager must run on the same machine as the integration node for the storage and retrieval of state information. You must specify a queue manager on the integration node. However, if you use HTTP nodes or SOAP nodes with the integration server embedded listener, IBM MQ is not required.

For more information, see Configuring MQ nodes for transactions, and HTTP listeners.
HTTP proxy servlet. The IBM MQ server and queue manager must run on the same machine as the integration node for the storage and retrieval of state information.

For more information about the HTTP proxy servlet, see HTTP proxy servlet overview.
Table 2. Scenarios that require a local IBM MQ server and queue manager
Scenario Comments
Two-phase commit transactions. Many of the circumstances that required a two-phase commit in earlier releases (such as multiple queue managers, combined database, and queue updates) now have viable alternatives.

For more information, see https://www.ibm.com/docs/en/ibm-mq/9.2?topic=cics-requirements-two-phase-commit-process.
Queue-based administration security (system queues are not required for file-based security). The IBM MQ server and queue manager must run on the same machine as the integration node for the storage and retrieval of state information. You must specify a queue manager on the integration node.

For more information, see Configuring administration security to use file-based, queue-based, or LDAP authorization.
Java™ connectivity and JDB (for some supplied nodes)

For JMSMQTransform and MQJMSTransform nodes, IBM MQ (Client or Server) must be installed on the same machine as the integration server.

For more information, see IBM App Connect Enterprise features and Installing IBM MQ.
Globally coordinated transactions The IBM MQ server and queue manager must run on the same machine as the integration node for the storage and retrieval of state information. You must specify a queue manager on the integration node.

For more information, see Configuring MQ nodes for transactions.
High Availability configurations The IBM MQ server and queue manager must run on the same machine as the integration node for the storage and retrieval of state information. You must specify a queue manager on the integration node.

For more information, see Configuring MQ nodes for transactions.
Load balancing If you are using an integration node listener (instead of embedded listeners) with your integration node, you must install an IBM MQ server on the same machine as the integration server that uses the capabilities. Also, you must associate a queue manager with the integration server or integration node by setting the defaultQueueManager configuration property.

For more information about setting the configuration property, see either Configuring an integration server by modifying the server.conf.yaml file or Configuring an integration node. You by modifying the node.conf.yaml file.

You must create the set of IBM App Connect Enterprise queues on your queue manager.

For more information, see Creating the default system queues on an IBM MQ queue manager.
Table 3. Message flow nodes that require a local IBM MQ server and queue manager
Scenario Comments
The following nodes require that an IBM MQ local queue manager is specified on the integration node when you want to use this queue manager by default for your local IBM MQ connection:
  • MQInput
  • MQOutput
  • MQGet
  • MQReply

The MQInput, MQOutput, MQGet, and MQReply nodes require that IBM MQ is installed either locally or remotely. However, they do not require a queue manager to be specified on the integration node unless you want to use this queue manager by default for your local IBM MQ connection.

For more information, see Configuring a local connection to IBM MQ and Configuring a client connection to IBM MQ.
The following nodes require that either IBM MQ Client or Server is installed on the same machine as the integration node. They also require a queue manager to be specified on the integration node:
  • SAPInput
  • SAPReply
  • SAPRequest
 For more information, see SAPInput node, SAPReply node, and SAPRequest node
FTEInput node The IBM MQ server and queue manager must run on the same machine as the integration node for the storage and retrieval of state information. You must specify a queue manager on the integration node.

For more information, see Configuring MQ nodes for transactions.
FTEOutput node The IBM MQ server and queue manager must run on the same machine as the integration node for the storage and retrieval of state information. You must specify a queue manager on the integration node.

For more information, see Configuring MQ nodes for transactions.
CDInput node The IBM MQ server and queue manager must run on the same machine as the integration node for the storage and retrieval of state information. You must specify a queue manager on the integration node.

For more information, see Configuring MQ nodes for transactions.
CDOutput node The IBM MQ server and queue manager must run on the same machine as the integration node for the storage and retrieval of state information. You must specify a queue manager on the integration node.

For more information, see Configuring MQ nodes for transactions.

For more information about the main IBM App Connect Enterprise features that require the installation of IBM MQ Client or Server, see IBM App Connect Enterprise features.

For more information about scenarios in IBM App Connect Enterprise that require a local IBM MQ Client or Server and a local queue manager, see When does ACE need a local MQ server?