Set up communication on Windows
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 Windows systems.
Before starting
We might find it helpful to refer to Example configuration - IBM MQ for Windows.
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.
When setting up communication for IBM MQ on Windows, we can choose from the following types of
communication:
- TCP/IP
- LU 6.2
- NetBIOS
- Defining a TCP connection on Windows
Define a TCP connection by configuring a channel at the sending end to specify the address of the target, and by running a listener program at the receiving end. - Defining an LU 6.2 connection on Windows
SNA must be configured so that an LU 6.2 conversation can be established between the two machines. - Defining a NetBIOS connection on Windows
A NetBIOS connection applies only to a client and server running Windows. IBM MQ uses three types of NetBIOS resource when establishing a NetBIOS connection to another IBM MQ product: sessions, commands, and names. Each of these resources has a limit, which is established either by default or by choice during the installation of NetBIOS.
Parent topic: Monitor and control channels on UNIX, Linux, and Windows
Related tasks
- Monitor and control channels on UNIX, Linux, and Windows
- Configure connections between the server and client
- Set up communication on UNIX and Linux
Related reference