MQSeries.net :: View topic - Channels vs client and server apps

HenriqueS · Posted: Fri Jun 29, 2007 3:55 pm Post subject:

Hello, IÂ´ve read some documentation about the MQI channels and tried to figure out the real need for MQI channel definitions...

I just wanted to make sure I got the things right...my assertions:

1) Server-side apps running on bindings mode do not need any channel definition to connect to the local MQ installation.

2) "Message channels" only apply for MQ to MQ communication, types of such messages channels are "Receiver" and "Sender".

3) "Message channels" channels provide assync communication. MQI channels ("Server connection" and "Client Connection") do not. If the communication layer is unreliable between the client and the app youÂ´ve got to deal with exceptions.

4) "Server connection" channels are needed to allow client apps to connect to the MQ server. The apps written to connect to the server must refer to the channel name on its code.

5) Entries on the "Client connections" folder are also needed to allow client apps to connect to the MQ server. If they are not used, the client app must be run with a environment variable that refers to the server.

Now questions:
6) Whats the purpose of the "Connection name" property inside a "Client connection" object, is not the client app already aware of the server since connects to it since from the beginning referring to the server hostname and channel name on its code?

7) Does always a client app need to load the client connection channel definitions - downloading the .TAB definition from the server or declaring the environment variable (MQSERVER)? IÂ´ve got client apps that donÂ´t do either, just open the connection with the server using three values (hostname, port and channel), and they do work...not even a "Client connection" object is created, only is created a "Server connection" object!

Am I wrong on any of my assertions above? Please try to answer in the numbering scheme to make it easier...

Many thanks!