Message channel planning example for IBM i

This section provides a detailed example of how to connect two IBM i queue managers together so that messages can be sent between them.

The example illustrates the preparations needed to allow an application using queue manager QM1 to put messages on a queue at queue manager QM2. An application running on QM2 can retrieve these messages, and send responses to a reply queue on QM1.

The example illustrates the use of TCP/IP connections. The example assumes that channels are to be triggered to start when the first message arrives on the transmission queue they are servicing.

This example uses SYSTEM.CHANNEL.INITQ as the initiation queue. This queue is already defined by IBM MQ. We can use a different initiation queue, but you have to define it yourself, start a new instance of the channel initiator using the STRMQMCHLI command, and provide it with the name of our initiation queue. For more information about triggering channels, see Triggering channels.

Note: A message channel using TCP/IP can be pointed at an IBM Aspera fasp.io Gateway, which provides a fast TCP/IP tunnel that can significantly increase network throughput. See Defining an Aspera gateway connection on Linux or Windows.

• What the example for IBM i shows
  This example involves a payroll query application connected to queue manager QM1 that sends payroll query messages to a payroll processing application running on queue manager QM2. The payroll query application needs the replies to its queries sent back to QM1.
• Running the example for IBM i
  When you have created the required objects we must start the channel initiators and listeners for both queue managers.
• Expanding the example for IBM i
  The example can be expanded in a number of ways.

Parent topic: Configuration reference