| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQClient listening for messages from a remote MQServer |
« View previous topic :: View next topic » |
| Author |
Message
|
| Vin |
 Posted: Thu Aug 07, 2003 8:32 pm Post subject: MQClient listening for messages from a remote MQServer |
 |
|
Master
Joined: 25 Mar 2002
Posts: 212
Location: India
|
| I have a remote MQServer and a queue residing on it. I want to get messages from this queue using MQ Client API. Can I use trigerring here? or should I set up a listener class for getting the messages? Do I need an MQServer at all on my side? How do I do this? |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Fri Aug 08, 2003 5:51 am Post subject: Re: MQClient listening for messages from a remote MQServer |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| Vin wrote: |
| I have a remote MQServer and a queue residing on it. I want to get messages from this queue using MQ Client API. Can I use trigerring here? or should I set up a listener class for getting the messages? Do I need an MQServer at all on my side? How do I do this? |
You can use triggering to start any kind of application. However, in order for triggering to start any kind of application, you need a trigger monitor running on the same machine. If the machine your trigger monitor is running on does not have an MQServer on it, you need a trigger monitor that can act as an MQ Client - like runmqtmc.
You don't need an MQServer on your side. However, if you want to isolate your application from whether or not the remote queue manager is available, then you *do* need a queue manager on your side. |
|
| Back to top |
|
|
| Vin |
| Posted: Fri Aug 08, 2003 5:58 am Post subject: |
|
|
Master
Joined: 25 Mar 2002
Posts: 212
Location: India
|
| Thanks for the reply. Wanted to ask you a question though, When you said If I want to isolate the app from the remote MQServer being down what exactly do u mean by that, what is the difference between the client server in this case? |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Aug 08, 2003 11:39 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| Vin wrote: |
| Thanks for the reply. Wanted to ask you a question though, When you said If I want to isolate the app from the remote MQServer being down what exactly do u mean by that, what is the difference between the client server in this case? |
The client makes a synchronous TCP (or SNA or whatever) connection to the server. If the server is down or the network between the client and the server is interrupted, the client can't do any work. Think of an MQClient as sort of like a web-browser. If the web server is down, you don't get any web pages in the browser.
If your application is instead connecting to a local server, then the application can exchange messages with the local server - which will handle the message exchange with the remote server for you, and will store messages when the remote server is unavailable and forward them when it becomes available again. |
|
| 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
|
|
|
|
