|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
MQ Series Vs MQ Series Everyplace |
« View previous topic :: View next topic » |
Author |
Message
|
mzafer |
Posted: Fri Nov 02, 2001 1:56 am Post subject: |
|
|
Newbie
Joined: 30 Oct 2001 Posts: 3
|
Hello There,
I have just started with MQ Series, My requirements are that the system should support both Synchronous and Asynchronous messages. I have installed MQ Series Everyplace since MQ series supports only Asynchronous messages. Now I am in a dilemma as I am not sure whether to continue with MQ Series Everyplace or look for a solution inside MQ Series itself.
Well, to make it clear.. I want to know the diference between MQ Series and MQ Series Everyplace, where exactly are they to be used.. and more..
Hoping for a reply at the earliest
Zafer
|
|
Back to top |
|
 |
donovang |
Posted: Tue Nov 13, 2001 7:47 am Post subject: |
|
|
Newbie
Joined: 23 Aug 2001 Posts: 9 Location: Ireland
|
MqSeries everyplace is basically for use with Palm pilots etc. It allows them to connect via a gateway to an MQ queue manager. Both are asynchronous.
|
|
Back to top |
|
 |
donovang |
Posted: Tue Nov 13, 2001 7:50 am Post subject: |
|
|
Newbie
Joined: 23 Aug 2001 Posts: 9 Location: Ireland
|
Correction....saw this just now in another posting....
The MQ Everyplace Native Client for Palm does NOT support asynchronous messaging. Only a stub queue manager without local queues can be built on PalmOS.
|
|
Back to top |
|
 |
zpat |
Posted: Tue Dec 11, 2001 3:50 am Post subject: |
|
|
 Jedi Council
Joined: 19 May 2001 Posts: 5866 Location: UK
|
You can use MQSeries for synchronous messaging, simply use MQPUT and then MQGET with the WAIT option. Typically you get the reply message based on the correlid (which is set as the outgoing msgid and moved to the correlid by the server application). The reply-to-queue field is usually set so the server application can reply to different queues automatically.
We use MQ for client/server applications and have done for several years, in fact I would suggest most MQSeries applications are synchronous in nature. With non-persistent messages, the response times are very good.
We generally use MQ client connections direct to the mainframe MQ server for simplicity rather than local MQ servers.
The best way to get advice on suitability is to state your requirements in functional terms - and NOT in terms of possible solutions/products - then we can say if MQ will meet the requirements.
[ This Message was edited by: zpat on 2001-12-11 03:54 ] |
|
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
|
|
|
|