Set up communication on UNIX and Linux

When a distributed-queuing management channel is started, it tries to use the connection specified in the channel definition. For this to succeed, the connection must be defined and available. This section explains how to do this by using the forms of communication available for IBM MQ for UNIX or Linux systems.


Before starting

We might find it helpful to refer to the following sections:

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. A queue manager running on any entitled platform can connect through an Aspera gateway. The gateway itself is deployed on Red Hat or Ubuntu Linux, or Windows. See Defining an Aspera gateway connection on Linux or Windows.


About this task

When a distributed-queuing management channel is started, it tries to use the connection specified in the channel definition. To succeed, it is necessary for the connection to be defined and available. This section explains how to do this.

When setting up communication for IBM MQ on UNIX and Linux, we can choose from the following types of communication:

  • TCP/IP
  • LU 6.2

Each channel definition must specify one only as the transmission protocol (Transport Type) attribute. One or more protocols can be used by a queue manager.

For IBM MQ MQI clients, it might be useful to have alternative channels using different transmission protocols. For more information about IBM MQ MQI clients, see Overview of IBM MQ MQI clients.

Parent topic: Monitor and control channels on UNIX, Linux, and Windows


Related tasks


Related reference