Configure an MFT agent for multiple channels in a cluster
To use IBM MQ multi-channel support in a clustered configuration, first set the agentMultipleChannelsEnabled property to true and then complete the steps in this topic.
About this task
In a cluster, multi-channel support is enabled by IBM MQ definitions on the queue manager of the destination agent only.
We must complete the steps in this topic in addition to the standard IBM MQ configuration steps required for a Managed File Transfer agent, which are listed in Configure MFT for first use.
The following configuration examples use runmqsc commands.
Procedure
- Define a cluster-receiver channel for each channel that we want to use. For example, if we are using two channels:
DEFINE CHANNEL(TO.DESTQMGRNAME_1) CHLTYPE(CLUSRCVR) CLUSTER(MFTCLUSTER) DEFINE CHANNEL(TO.DESTQMGRNAME_2) CHLTYPE(CLUSRCVR) CLUSTER(MFTCLUSTER)where:
- DESTQMGRNAME is the name of the queue manager of the destination agent.
- MFTCLUSTER is the name of the IBM MQ cluster.
You are recommended to use the MFTCLUSTER.DESTMGRNAME_n naming convention for channels, but this convention is not mandatory.
- Define a queue manager alias corresponding to each channel. For example:
DEFINE QREMOTE(SYSTEM.FTE.DESTQMGRNAME_1) RQMNAME(DESTQMGRNAME) CLUSTER(MFTCLUSTER) DEFINE QREMOTE(SYSTEM.FTE.DESTQMGRNAME_2) RQMNAME(DESTQMGRNAME) CLUSTER(MFTCLUSTER)You must use the SYSTEM.FTE.DESTQMGRNAME_n naming convention for queue manager aliases because the sending agent searches for queue manager aliases of this format. The numbers that we use for n must start at 1 and be consecutive. We must make the definitions cluster-wide so that they are available on the source agent's queue manager.For both the source agent and destination agent to correctly determine the number of queue manager aliases, do not define a default XMITQ for the queue manager.
Parent topic: The MFT agent.properties file
Related reference
Related information