| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Is there a WSMQ equivalent to SonicMQ's Client Persistence |
« View previous topic :: View next topic » |
| Author |
Message
|
| jamie_townsend |
 Posted: Wed Mar 09, 2011 8:38 am Post subject: Is there a WSMQ equivalent to SonicMQ's Client Persistence |
 |
|
Newbie
Joined: 09 Mar 2011
Posts: 4
|
Hi. I'm new to WebSphere MQ, but will be using it in a project where the clients will need to be able to send messages (and have them delivered) even though they might not be permanently connected to the queue manager (obviously messages would only be delivered when the connection can be re-established).
Sonic MQ's "Client Plus" offers this kind of persistent client, where messages sent when no connection to the queue manager can be achieved, they will be automatically stored in a client-side database and upon re-connection, automatically sent. This can be used to achieve guarenteed (although potentially delayed) message delivery.
Does WebSphere MQ offer equivalent functionality or would we have to write something ourselves?
Thanks in advance,
Jamie |
|
| Back to top |
|
 |
| mvic |
| Posted: Wed Mar 09, 2011 9:31 am Post subject: Re: Is there a WSMQ equivalent to SonicMQ's Client Persisten |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
Reply deleted as I misunderstood the question. See mqjeff's reply instead.
Last edited by mvic on Wed Mar 09, 2011 11:32 am; edited 1 time in total |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Mar 09, 2011 11:01 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
In general, no, there is no mechanism for doing this out of the box with JUST an MQ Client.
In general, the PROPER way to handle this with MQ, where you have a known-to-be-unreliable connection is to put a local qmgr on both sides of the unreliable connection, and then make sure to use reliable connections to the local qmgr.
Then your client apps would make reliable connections to a local qmgr, which would persist the messages and forward them down the unreliable connection as it was possible to do so.
If your issue is licensing fees for that many queue managers, you should instead consider the cost of ensuring that the network links are actually reliable. Then you have a better idea of which is less expensive in the long run.
If your issue is somehow with how "heavy" a local qmgr install would be, I suspect you'll find that the Sonic client ends up installing what amounts to a limited-use but full-blown local database and DBMS.
The MQ product is designed to ensure that MQ applications can make sound and logical business decisions based on the results of MQ operations. If it is *not* important to the business that a specific network link is available at the time of the transaction, then you use an MQ queue manager to manage the network reliability. Not a client. |
|
| Back to top |
|
|
| mvic |
| Posted: Wed Mar 09, 2011 11:31 am Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| mqjeff wrote: |
| In general, no, there is no mechanism for doing this out of the box with JUST an MQ Client. |
It's clear I completely misread the question. I will delete as much of my reply as the system will allow.  |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
