Author |
Message
|
sbk |
Posted: Fri Mar 01, 2013 12:54 pm Post subject: MQ PUB/SUB problem |
|
|
Novice
Joined: 25 Jan 2012 Posts: 22
|
Hello All,
I am new to MQ. While I am trying to do pub/sub concept in MQ , I am able to do the subscriptions for the queues of same queue manager and getting problem while trying to connect to localqueue of a remote queue manager. [reason code 2087(AMQ4043)---Queue manager not available for connection]
Please suggest.
Regards,
SBK.
[/img] |
|
Back to top |
|
 |
Vitor |
Posted: Fri Mar 01, 2013 12:59 pm Post subject: Re: MQ PUB/SUB problem |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
sbk wrote: |
I am able to do the subscriptions for the queues of same queue manager and getting problem while trying to connect to localqueue of a remote queue manager. [reason code 2087(AMQ4043)---Queue manager not available for connection] |
How are you trying to connect to this remote queue manager?
Why are you trying to connect to this remote queue manager?
Why are you not publishing and subcribing via your local queue manager?
Do you really mean "remote queue manager" in the WMQ sense (a queue manager to which you're not connected) or do you mean a queue manager not hosted on the box you're actually using?
(It changes how you "connect") _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
mqjeff |
Posted: Fri Mar 01, 2013 1:27 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
You can not read messages from queue managers that you are not connected to.
So if you are connected to qmgr A, you can not read messages from queue manager B.
Pub/Sub, oddly enough, does not change this. |
|
Back to top |
|
 |
zpat |
Posted: Fri Mar 01, 2013 11:49 pm Post subject: |
|
|
 Jedi Council
Joined: 19 May 2001 Posts: 5866 Location: UK
|
You can define a subscription destination of a remote queue definition on your local queue manager, which will route the messages to the remote queue manager.
You can access messages on a remote queue manager, either by connecting to it (client mode) running your code on it (bindings mode) or by defining a remote queue definition there to send the messages to your local queue manager.
Generally it's best to use just one QM and route messages to it.
There is also the option of distributed pub/sub and pub/sub clusters, but maybe start the easy way. |
|
Back to top |
|
 |
sbk |
Posted: Thu Mar 07, 2013 10:14 am Post subject: |
|
|
Novice
Joined: 25 Jan 2012 Posts: 22
|
Thanks for your replies. I worked with PUB/SUB .
Here the question is why they mentioned destinationqueuemanager and destination name in the subscription properties (destination queue manager and destination queue). While we are giving it directly (queuemanager name and Localqueue name) it is not taking.
Please suggest me. |
|
Back to top |
|
 |
sbk |
Posted: Thu Mar 07, 2013 10:15 am Post subject: |
|
|
Novice
Joined: 25 Jan 2012 Posts: 22
|
Please go to
QM--> subscriptions--> on the right pane select one subscription --> now right click on it and go to properties--> there we can see Destination details.
I am talking about these things.
Thanks..
SBK |
|
Back to top |
|
 |
bruce2359 |
Posted: Thu Mar 07, 2013 11:03 am Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9470 Location: US: west coast, almost. Otherwise, enroute.
|
Go to? Using what? The WMQ Explorer? Something else? _________________ I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
Back to top |
|
 |
|