| Author |
Message
|
| danielboone |
 Posted: Thu Feb 16, 2012 7:47 pm Post subject: Subscribing to a remote publisher |
 |
|
Newbie
Joined: 16 Feb 2012
Posts: 4
|
Hi All,
I'm extremely new to MQ (our MQ administrator just quit and I have to try and configure the environment for a project). I've looked at the manual for 7.0.1 and used google but can't find out everything I need to know.
I have to configure a subscription in our 7.0.1 environment with MQ Explorer. It needs to connect to a remote publisher but I don't have any examples to copy as this is the first subscription to be set up.
Our normal send and receive traffic queues are connected to send and receive channels. Only the Sender channel has the IP address of the remote MQ machine.
I'm trying to set up a subscription and the instructions I've found only talk about a local publisher. I thought I'd have to send up a receiver channel to connect to the remote publisher, but receiver channels don't have IP addresses. I can't figure out where I tell the system where the remote publisher is!
Can anyone tell me how to set up a subscription to a remote publisher? I have the IP address, the MQ port, the remote Queue Manager name and the topic. Am I missing anything?
Thanks for your time!!! |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Thu Feb 16, 2012 8:04 pm Post subject: Re: Subscribing to a remote publisher |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| danielboone wrote: |
I'm trying to set up a subscription and the instructions I've found only talk about a local publisher. I thought I'd have to send up a receiver channel to connect to the remote publisher, but receiver channels don't have IP addresses. I can't figure out where I tell the system where the remote publisher is!
Can anyone tell me how to set up a subscription to a remote publisher? I have the IP address, the MQ port, the remote Queue Manager name and the topic. Am I missing anything?
Thanks for your time!!! |
- Determine where the topic is being published (qmgr) = source
- Determine where the qmgr the consumer connects to is = target
- Determine the pub/sub topology and see if there is already a relationship (pub/sub) between source and target
- Make sure there exists a sdr/rcvr channel between target and source and between source and target
- determine whether the subscription will be administrative or dynamic
- The rest should all be in the manuals
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| danielboone |
| Posted: Thu Feb 16, 2012 8:41 pm Post subject: Re: Subscribing to a remote publisher |
|
|
Newbie
Joined: 16 Feb 2012
Posts: 4
|
| fjb_saper wrote: |
[*]Determine where the topic is being published (qmgr) = source
|
That's the remote server - I have their IP, port and topic.
| fjb_saper wrote: |
[*]Determine where the qmgr the consumer connects to is = target
|
I have a test queue manager I'm going to link it to - provided I can have messages from different source IPs coming into a single QMGR (which it looks like I can). Otherwise I'll create a new QMGR.
| fjb_saper wrote: |
[*]Determine the pub/sub topology and see if there is already a relationship (pub/sub) between source and target
|
As far as I can tell it'll have "event" publications and should be a "durable" subscription.
There's no relationship between the source and target at this point.
| fjb_saper wrote: |
[*]Make sure there exists a sdr/rcvr channel between target and source and between source and target
|
I've created a receiver channel. I can't see any reason I'd need a sender channel when I'm just going to receive messages (ie. I'm not publishing anything) - do I need a sender channel?
| fjb_saper wrote: |
[*]determine whether the subscription will be administrative or dynamic
|
I've searched the manual as the terms aren't familiar to me and can't find an exact match. I think I need predefined rather than dynamic queues if that's what you're asking?
| fjb_saper wrote: |
[*]The rest should all be in the manuals
|
I'm looking in the Websphere MQ -> Publish/Subscribe Users Guide. I can't find any "tutorial" or similar walkthrough unfortunately so I'm not sure exactly what I need to set up.
As a receiver, do I need to configure in the sender's IP address, or is that only configured on the sender side?
I've also been asked to do a ping test. I can't do a ping test on a receiver channel, but I can't see that I need to have a sender channel when I'll be a passive subscriber.
Thanks!!! |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Feb 17, 2012 5:39 am Post subject: Re: Subscribing to a remote publisher |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| danielboone wrote: |
| It needs to connect to a remote publisher |
No it doesn't. As my most worthy assocaite alludes to, the queue manager where you're subscribing needs to be connected to the queue manager where the publication is taking place. If you have sender/receiver channels linking the queue managers already then fine.
Our normal send and receive traffic queues are connected to send and receive channels. Only the Sender channel has the IP address of the remote MQ machine.
| danielboone wrote: |
| I can't figure out where I tell the system where the remote publisher is! |
That's because you don't, and from a design standpoint you shouldn't (because it couples the subscription to a given publisher). You're paying a lot of money for some IBM software to work all this out for you.
| danielboone wrote: |
| Can anyone tell me how to set up a subscription to a remote publisher? I have the IP address, the MQ port, the remote Queue Manager name and the topic. Am I missing anything? |
The knowledge that you're working too hard at this. Let the software see to it.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Feb 17, 2012 8:32 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
You need to separate the notion of a "remote publisher" from the notion of a "remote queue manager".
A "remote queue manager" is a queue manager that is not the queue manager that your application is connected to. If your application is running on machine 1, and the queue manager your application is connected to is running on machine 2, then this is not a "remote queue manager". That's a local queue manager, from which you can read messages off qlocals.
If you have an ip address, channel name, and port #, then you have the necessary information to connect to a queue manager - which will then be your local queue manager. You can then register a subscription on that queue manager to your topic, and the subscription will tell the queue manager which queue to put published messages onto.
Or if you are using something like JMS, you will merely create a Topic destination and that will handle all that work for you. You will then read messages from the Topic object.
Again, this has nothing to do with where the publisher application is running. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri Feb 17, 2012 9:57 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Pub/sub comes in two topologies: point-to-point and clusters.
You might want to investigate WMQ clusters; and, more specifically, pub/sub clusters. A topic can be part of a WMQ cluster.
_________________
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 |
|
|
| danielboone |
| Posted: Sun Feb 19, 2012 8:17 pm Post subject: |
|
|
Newbie
Joined: 16 Feb 2012
Posts: 4
|
Okay, lets see if my understanding is any closer now then...
As my subscriber doesn't know where the publisher is (but my queue manager does) I have now created a new queue manager for the traffic from the off-site publisher.
They (as the publisher) will create a Sender channel with the IP/port details of my MQ server.
I (as the subscriber) will create only a Receiver channel which doesn't know (and doesn't need to know) how to find the sender.
So as long as the publisher's channel has the right IP and port for my MQ subscriber, and I have subscribed to the right topic name, I'll see the traffic.
Is that correct?
(Just to clarify : I am not responsible for interacting with the traffic. All my job is is to make sure the subscriber can see the publisher, once that is confirmed we're paying a vendor to come onsite and write code for us. I'm just hoping to set up the queue, turn it on, and see some messages through "browse messages" in the GUI.) |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun Feb 19, 2012 8:35 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| danielboone wrote: |
Okay, lets see if my understanding is any closer now then...
As my subscriber doesn't know where the publisher is (but my queue manager does) I have now created a new queue manager for the traffic from the off-site publisher.
They (as the publisher) will create a Sender channel with the IP/port details of my MQ server.
I (as the subscriber) will create only a Receiver channel which doesn't know (and doesn't need to know) how to find the sender.
So as long as the publisher's channel has the right IP and port for my MQ subscriber, and I have subscribed to the right topic name, I'll see the traffic.
Is that correct?
(Just to clarify : I am not responsible for interacting with the traffic. All my job is is to make sure the subscriber can see the publisher, once that is confirmed we're paying a vendor to come onsite and write code for us. I'm just hoping to set up the queue, turn it on, and see some messages through "browse messages" in the GUI.) |
you got it all wrong again:
- It does not matter where the publisher is. What matters is which qmgr (broker enabled) he publishes to => hereafter called publishing qmgr
- It does not matter where the subscriber is. What matters is which qmgr the subscriber is connected to => hereafter called subscribing qmgr
- In order for a subscription to be successful you need a default communication from subscribing qmgr to publishing qmgr AND from publishing qmgr to subscribing qmgr.
- The subscriber will identify a topic by it's topic string and the delivery queue and subscribe to it. The delivery queue needs to be a queue local in the subscribing qmgr. The subscription is sent to the publishing qmgr.
- The publishing qmgr will publish messages on a topic and deliver the messages to all subscriber that have registered a subscription to said topic with the publishing qmgr.
- Clustering just changes the scope of the subscription / publication. All other pub/sub rules still apply
 the pub/sub manual some more. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| danielboone |
| Posted: Sun Feb 19, 2012 8:41 pm Post subject: |
|
|
Newbie
Joined: 16 Feb 2012
Posts: 4
|
Thanks for correcting me and sorry for all the hassle to everyone replying to me!
I'm finding the manuals hard going for someone not very familiar with MQ - particularly as I'm a Sysadmin and not a coder. I'll go through the manuals again in light of your reply and see if I can make it make more sense! |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Sun Feb 19, 2012 11:20 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| danielboone wrote: |
| I'm finding the manuals hard going for someone not very familiar with MQ - particularly as I'm a Sysadmin and not a coder. I'll go through the manuals again in light of your reply and see if I can make it make more sense! |
Please start with the WMQ fundamentals before launching into an advanced subject like pub/sub. Search google for 'websphere mq fundamentals,' and start reading.
_________________
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 |
|
|
|
|
