Setting up communication for Windows
When a distributed-queuing management channel is started, it tries to use the connection specified in the channel definition. For this to succeed, it is necessary for the connection to be defined and available. This section explains how to do this using one of the four forms of communication for WebSphere® MQ for Windows systems.
You might find it helpful to refer to Example configuration - IBM® WebSphere MQ for Windows.
For UNIX and Linux® systems see Setting up communication on UNIX and Linux systems.
Deciding on a connection
- Defining a TCP connection on Windows
- Defining an LU 6.2 connection on Windows
- Defining a NetBIOS connection on Windows
- Defining an SPX connection on Windows ( Windows XP and Windows 2003 Server only)
Each channel definition must specify only one protocol as the Transmission protocol (Transport Type) attribute. One or more protocols can be used by a queue manager.
For WebSphere MQ clients, it might be useful to have alternative channels using different transmission protocols. For more information about WebSphere MQ clients, see Overview of clients.