| Author |
Message
|
| wilsonjohn24 |
 Posted: Thu Oct 11, 2007 12:20 am Post subject: Hub/Spoke Arcitecture with JMS Subscriber at the Spoke |
 |
|
Voyager
Joined: 02 Feb 2007
Posts: 93
Location: Scotland
|
Hi,
[ pub/subs clients are JMS]
[WMB 6.03]
[WMQ 6.02]
[JMS 1.1]
Have WMB as the pub/subs engine on the Hub. I want to connect a Durable Subscriber via a Spoke system. I dont want the application that is subscribing talking directly with the Hub! I can do pub/sub ok when communicating directly with pubs/subs on the Hub.
I can publish ok from the spoke system ( creating remote defiition of stream etc on the spoke system to the hub), but I am unable to set up a durable subscription. I get error following error:
Broker command failed: 3081 Reason code 3081
(*Which I know is about security etc*)
Questions:
1) Is it standard approach to pub/subs from a already establish hub/spoke architectire?
2)Is there any special security setting I need to do other than clientID in JMS? [ The whole system is not security enabled]
3) Also is there any free software than can read PCF event messages?
I have authority events enabled but not tool to deciper them! |
|
| Back to top |
|
 |
| wilsonjohn24 |
| Posted: Thu Oct 11, 2007 6:30 am Post subject: |
|
|
Voyager
Joined: 02 Feb 2007
Posts: 93
Location: Scotland
|
Ok then,
Can you subscribe to a pub/subs engine indirectly via another queue manager than is not a pub/subs engine? Or must you connect directly to the pub/subs engine? |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Oct 11, 2007 6:37 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You should be able to interact with a broker that is on a different qmgr than the one your application is connected to.
It's necessary, first, to ensure that there is good solid MQ communications between the two queue managers.
Secondly, to make sure that any necessary queue names can be properly resolved from both directions (that your app can send to the correct broker queues and that the broker can send to the correct queues for your app).
There are properties on JMS destinations that distinguish between "your" queue manager and the BROKER queue manager... that is, there are property to identify the broker queue manager.
There is at least one SupportPac that should let you view authority messages - I think there may even be three, one of which is an MQ Explorer plugin.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| wilsonjohn24 |
| Posted: Thu Oct 11, 2007 8:09 am Post subject: |
|
|
Voyager
Joined: 02 Feb 2007
Posts: 93
Location: Scotland
|
1. MQ Comms are solid. As I get the reports of failure back to the non pubs/subs QM.
2.Proper alias etc all done....
3. I do change all the properties including the broker queue manager in JMS.
Simple Non JMS scenario using RFHUtil.
----------------------------------------------
1.Send a subscription direct to broker it works ok.
2.As 1 except change the subscription queue manager + queuename to
point to the non pub/subs queue manger still connecting directly to broker. Works ok.
3. Alias System.broker.control.queue on non pubs/subs Queue Manager to point to the name sake on the broker. Then do the same as 2, except connect to the non pubs/subs queue manager. But all the data entered is the same - I get 3081 error.
The fact that 2 works I conclude that the infrastructure set up is ok. The fact the 3 fails seem to indicate that a subscriber need to be connected directly to the broker.
This is was my take for what it's worth  |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Oct 11, 2007 2:53 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Dont use point 3--- In the TCF specify the broker qmgr which is not the qmgr you are connected to...
It should work better.
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| wilsonjohn24 |
| Posted: Thu Oct 11, 2007 10:07 pm Post subject: |
|
|
Voyager
Joined: 02 Feb 2007
Posts: 93
Location: Scotland
|
Hi fjb_saper,
So is it acceptable practice in a hub and spoke architecture to have you publishers and subscribers communicating directly with broker? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Oct 12, 2007 8:25 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
If you look at the TCF setup:
You can create a TCF that connects to QMGR B and specifies that QMGR A is the broker. You do not connect directly to the broker QMGR but you need regular channels and default routing between qmgr A and qmgr B
Enjoy
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| wilsonjohn24 |
| Posted: Tue Oct 16, 2007 10:22 pm Post subject: |
|
|
Voyager
Joined: 02 Feb 2007
Posts: 93
Location: Scotland
|
|
| Back to top |
|
|
|
|
