| Author |
Message
|
| sspr |
 Posted: Wed Jul 12, 2006 3:56 am Post subject: cross platform communication |
 |
|
Newbie
Joined: 12 Jul 2006
Posts: 4
|
Hi..
I want a clarification. I am working with IBM MQ Series. this is one more message queuing serivce. something like a MSMQ's. I have developed a sample application using VC++ to interact with these queues.
I have the MSMQ's on windows server and IBM MQ Series also on windows server. My application reads messages from the IBM MQ Series and dumps into the MSMQ's. This is running fine.
Now I have a doubt. If the same IBM MQ Series are on a Linux server and I run my application(on windows) to read from a remote server(IBM MQ Series on Linux server). Will there be any problem.
is that cross platform communication possible.
Thanks in advance |
|
| Back to top |
|
 |
| Vitor |
| Posted: Wed Jul 12, 2006 4:34 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
You can't read directly from a remote queue manager under IBM MQ. The 2 possible methods would be a) connect as an MQ client to the Linux box from Windows & read from that queue manager; b) connect the Linux queue manager to the Windows queue manager, get it to forward the messages and read from the Windows queue manager.
But the MQ API calls are the same on Windows and Linux so the application would run unmodified. The only change might be if your Windows app is currently linked with the server-side libraries you might need to relink with the client ones.
Apologies if I've misunderstood the question. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Jul 12, 2006 4:49 am Post subject: Re: cross platform communication |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| sspr wrote: |
| this is one more message queuing serivce. something like a MSMQ's. |
Also, it's not "one more" message queuing service, it's the best one! 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| xxx |
| Posted: Wed Jul 12, 2006 4:37 pm Post subject: |
|
|
Centurion
Joined: 13 Oct 2003
Posts: 137
|
|
| Back to top |
|
|
| sspr |
| Posted: Thu Jul 13, 2006 12:33 am Post subject: basic doubt |
|
|
Newbie
Joined: 12 Jul 2006
Posts: 4
|
i am new to this IBM MQ Series..
is it possible to read from remote queue? a remote queue as my understanding goes can be on the same server under a different queue manager. or on different server under a queue manager.
while using MSMQ's if we specify the ip address of the remote server and the queue name on that server we can connect to the queue on the different server. by remote queue i mean this secnario.
i have written an application using c++ to read from local queue of a IBM MQ Series and dump into MSMQ's. i want to extend the application to read from a remote queue and dump into my MSMQ.
is it possible.. i could not figure out a way to do it can anyone help me out |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jul 13, 2006 12:46 am Post subject: Re: basic doubt |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
In IBM MQ terminology a "local" queue is a queue hosted by the queue manager to which you're connected, a "remote" queue is a definition on your queue manager which points to a local queue hosted on a different queue manager. The location of the queue manager (same or different server) is irrelevant in this context.
MQSeries does not allow the reading of messages from remote queues. To achieve what you're discussing you'd need to connect to the queue manager hosting the target queue (using the same method as you used to connect to the local one, just some different parameters and possibly configuration) and then do the read because then the queue would be "local" to your connection. Straightforward. Possibly undesireable due to network issues, or possibly not - depends on your set-up.
The other way would be to get the remote queue manager to forward the messages to your local one. Bit more set-up there.
Check out the "Intercommunication" manual for more information on local & remote queues, and the "Clients" manual for information about connecting your application.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
