+

Search Tips | Advanced Search

Configure an MFT agent for multiple channels: non-clustered

To use IBM MQ multi-channel support in a non-clustered configuration, first set the agentMultipleChannelsEnabled property to true and then complete the steps in this topic.


About this task

In a non-clustered configuration, multi-channel support is enabled by IBM MQ definitions on the queue manager of both the source agent and the destination agent.

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 steps assume that sender-receiver channels are being used to communicate between the source and destination queue managers.

The following configuration examples use runmqsc commands.


Procedure

  1. On the destination agent's queue manager, define a receiver channel for each channel that we want to use. For example, if you are using two channels: 
    DEFINE CHANNEL(TO.DESTQMGRNAME_1) CHLTYPE(RCVR) TRPTYPE(TCP)
DEFINE CHANNEL(TO.DESTQMGRNAME_2) CHLTYPE(RCVR) TRPTYPE(TCP)
    where: DESTQMGRNAME is the name of the queue manager of the destination agent.

    You are recommended to use the TO.DESTMGRNAME_n naming convention for channels, but this convention is not mandatory. The receiver channel names must match the corresponding sender channels on the source agent's queue manager.

  2. On the source agent's queue manager, define a transmission queue for each channel that we want to use. For example, if we are using two channels: 
    DEFINE QLOCAL(DESTQMGRNAME_1) USAGE(XMITQ)
DEFINE QLOCAL(DESTQMGRNAME_2) USAGE(XMITQ)
    You are recommended to use the DESTMGRNAME_n naming convention for transmission queues, but this convention is not mandatory. The transmission queues you define are referenced from the sender channel definitions and the queue manager alias definitions in the following steps.
  3. On the source agent's queue manager, define a sender channel for each channel that we want to use. For example, if we are using two channels: 
    DEFINE CHANNEL(TO.DESTQMGRNAME_1) CHLTYPE(SDR) TRPTYPE(TCP) CONNAME(DESTHOST:port)
XMITQ(DESTQMGRNAME_1)
DEFINE CHANNEL(TO.DESTQMGRNAME_2) CHLTYPE(SDR) TRPTYPE(TCP) CONNAME(DESTHOST:port)
XMITQ(DESTQMGRNAME_2)
    You are recommended to use the TO.DESTMGRNAME_n naming convention for the channels, but this convention is not mandatory. The sender channel names must match the corresponding receiver channels on the destination agent's queue manager.
  4. On the source agent's queue manager, define a queue manager alias corresponding to each channel. For example: 
    DEFINE QREMOTE(SYSTEM.FTE.DESTQMGRNAME_1) RQMNAME(DESTQMGRNAME) XMITQ(DESTQMGRNAME_1)
DEFINE QREMOTE(SYSTEM.FTE.DESTQMGRNAME_2) RQMNAME(DESTQMGRNAME) XMITQ(DESTQMGRNAME_2)
    We must use the SYSTEM.FTE.DESTQMGRNAME_n naming convention for the queue manager aliases because the sending agent searches for queues manager aliases of this format. The numbers that we use for n must start at 1 and be consecutive.

    For the 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

Last updated: 2020-10-04