In summary:
create new node and associate with new qmgr
create new node and associate with old qmgr
create new node and don't associate with qmgr (configure directly flows or use policy)
https://www.ibm.com/support/knowledgecenter/SSTTDS_11.0.0/com.ibm.etools.mft.doc/bh25000_.htmFurther, if your IBM MQ queue manager is running on the same machine as your integration node, you can specify a local connection to the queue manager. Alternatively, if the IBM MQ queue manager that you want to connect to is hosted on a separate machine from IBM App Connect Enterprise, you can configure a client connection from your integration node so that it can access the messages on the remote queue manager.
The following IBM App Connect Enterprise features require IBM MQ Server to be installed on the same machine as the integration node, and they are available for use only if you specify a queue manager on the integration node:
- Event-driven processing nodes (aggregate, collector, sequence, resequence, and timeout nodes)
- FTEInput and FTEOutput nodes
- CDInput and CDOutput nodes
- Integration nodes with HTTP listeners
https://www.ibm.com/support/knowledgecenter/SSTTDS_11.0.0/com.ibm.etools.mft.doc/bb28660_.htm------------------------------
Muhammad Haider Raza, Integration Lead
Royal Cyber Inc.
------------------------------
Original Message:
Sent: 09-19-2018 11:34
From: Leonid Sadovnikov
Subject: ACE and MQ integration/architecture
What is the ACE and MQ integration/architecture when the local MQ installed was used in the solutions with IIB V9 and V10?
------------------------------
Leonid Sadovnikov
SCA
IBM
-
------------------------------