Processing events
You can use event driven message processing to control the flow of messages through your message flows, by using aggregation, message collections, message sequences, and timeout flows. Information about the state of in-flight messages is held on system queues that are controlled by IBM® MQ queue managers.
About this task
If you want to use event driven processing on an integration server that is managed by an integration node, you must install IBM MQ on the same computer as your integration node. The system queues that hold the state information are owned by the queue manager that is specified on the integration server. You associate a queue manager with the integration server by specifying the queue manager name on the defaultQueueManager property in the server.conf.yaml configuration file; for more information, see Configuring an integration server by modifying the server.conf.yaml file.
If you want to use event driven processing with an independent integration server, you can use a remote default queue manager to control the system queues, without the need to install IBM MQ on the same machine as IBM App Connect Enterprise. Interactions between an independent integration server and IBM MQ can use a client connection to a remote queue manager, by using a default policy setting. For information about using a remote default queue manager, see Using a remote default queue manager and Configuring an integration server to use a remote default queue manager.
You must create the system queues by running the iib_createqueues command, as described in Creating the default system queues on an IBM MQ queue manager.
IBM MQ is not provided as part of the IBM App Connect Enterprise installation package, but your license for IBM App Connect Enterprise entitles you to install and use IBM MQ. For more information about using IBM MQ with IBM App Connect Enterprise, see Installing IBM MQ and Enhanced flexibility in interactions with IBM MQ. For more information about IBM MQ, see IBM MQ product information.