All IBM MQ connections are tested after IBM MQ is configured by either using a sample program to send and
receive messages, or using sample amqscnxc to test IBM MQ client type connections.
The
amqscnxc sample connects to a queue manager by defining the channel connection in
the sample code, which is similar to the way that Managed File Transfer connects, when it uses an MQI or IBM MQ client type connection.
The instructions assume that the server we use for the base configuration has one IBM MQ version installed. If we have multiple IBM MQ installations in the base server, you must be careful to
use the correct file path for the version of IBM MQ you
want to use.
The queue managers used in these instructions do not require connection authentication.
While
it might be simpler to complete your first configuration without connection authentication required,
if your enterprise requires immediate use of connection authentication, see Managed File Transfer
and IBM MQ connection authentication for
instructions on how to configure an MQMFTCredentials.xml credentials file
Figure 1. Base topology with separate coordination queue manager and one partner agent
The queue manager roles for the example configuration are:
Base server
Queue manager MFT5 is the coordination queue manager
Queue manager MFT4 is used as the agent queue manager for agent MFT4AGT1, and also serves as the
command queue manager for the MFT5 configuration on the base server.
Partner server
Queue manager CSM1 doubles as the agent queue manager for agent CSM1AGT1, and as the command
queue manager for the MFT5 configuration on the partner server.
Queue manager MFT5, on the base server, is the coordination queue manager.