| Author |
Message
|
| wildrice |
 Posted: Fri Jul 04, 2003 12:10 am Post subject: MQ Server vs. Client |
 |
|
Newbie
Joined: 03 Jul 2003
Posts: 1
|
Hello all,
I am new to MQ, need your kindly support. We are trying to integrate a couple mainframes using MQ series, will have a central MQ Server. But I don't know we should install MQ server or just MQ client on mainframes in order to communicate with that server. What's advantage or disadvantage using MQ server and client? I asked around, some feedback are MQ server to server is guaranteed, and server to client is not, is that correct? Thanks a lot!!
Felix |
|
| Back to top |
|
 |
| nirmala |
| Posted: Fri Jul 04, 2003 1:00 am Post subject: |
|
|
Novice
Joined: 08 Oct 2002
Posts: 20
|
| It depends on the what u require. if ur looking for synchronous communication then client will do. But if its asynchronous communication and if u require the message to saved in the destination side till it is processed then u require a server. |
|
| Back to top |
|
|
| GMcCarthy |
| Posted: Mon Jul 07, 2003 3:51 am Post subject: |
|
|
Centurion
Joined: 06 Nov 2001
Posts: 113
Location: Melville NY
|
What platforms are you looking to install the MQ Client? Can I assume by 'mainframe' you mean z/OS? If so, there is no client for z/OS.
_________________
Regards,
Gina
IBM Certified MQSeries Specialist |
|
| Back to top |
|
|
| zpat |
| Posted: Mon Jul 07, 2003 6:08 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
You could make one of your mainframes the central MQ server but there is no native MQ client for OS/390 as mentioned above. You can attach MQ clients to a OS/390 MQ server with the optional client attach facility.
Whether the Java MQ client would run on OS/390 is an interesting question of course. |
|
| Back to top |
|
|
| Cliff |
| Posted: Tue Jul 08, 2003 6:50 am Post subject: |
|
|
Centurion
Joined: 27 Jun 2001
Posts: 145
Location: Wiltshire
|
Regarding your original post, 'MQ server to server is guaranteed, and server to client is not, is that correct? ' - Yes.
For client applications, MQSeries API calls are passed to the server where they are processed by a proxy on behalf of the client. This means there are small possibilities for things to go wrong - consider the client app putting messages under syncpoint, then issuing MQCMIT. The MQCMIT call is passed to the server, where it is processed successfully, during which time the network falls over. The client doesn't know whether the unit of work was completed or not... Likewise, if the client app MQGETs messages outside syncpoint and the connection is broken before the client app receives the data, then the data is lost.
Just be aware that MQClient code is free but that price comes at a cost! The client has no store-and-forward capability, you need a full queue manager for that.
Good luck -
Cliff |
|
| Back to top |
|
|
| techno |
| Posted: Wed Apr 21, 2004 10:58 am Post subject: |
|
|
Chevalier
Joined: 22 Jan 2003
Posts: 429
|
Above argument may not be vailid. I have an asynchronous listener running with client connection. For the apps which are sending a message, we may need to have more than one qmgrs so that one of the connections/sends would be successful.
What do you think? |
|
| Back to top |
|
|
|
|
