Home

 

Communications

WebSphere MQ clients use MQI channels to communicate with the server. A channel definition must be created at both the WebSphere MQ client and server ends of the connection. How to do this is explained in Defining MQI channels.

The transmission protocols possible are shown in the following table:

Table 2. Transmission protocols for MQI channels

Client platform	LU 6.2	TCP/IP	NetBIOS	SPX
UNIX systems	Yes1	Yes
Windows	Yes	Yes	Yes	Yes
Notes: Except on Linux (POWER platform)

Table 11 shows the possible combinations of WebSphere MQ client and server platforms, using these transmission protocols.

A WebSphere MQ application on a WebSphere MQ client can use all the MQI calls in the same way as when the queue manager is local. MQCONN or MQCONNX associates the WebSphere MQ application with the selected queue manager, creating a connection handle. Other calls using that connection handle are then processed by the connected queue manager. WebSphere MQ client communication is synchronous, in contrast to communication between queue managers, which is connection-independent and time-independent.

The transmission protocol is specified via the channel definition and does not affect the application. For example, a Windows application can connect to one queue manager over TCP/IP and to another queue manager over NetBIOS.

 

Home