| Author |
Message
|
| Blomman |
 Posted: Mon Nov 12, 2012 11:57 am Post subject: Administrer QueueManager throught intermediate QueueManager |
 |
|
Master
Joined: 31 Oct 2006
Posts: 230
|
Hi!
Ive been trying to find out how to connect and admin a QueueManager throught a intermediate QueueManager..
This is my setup.
QmA(WMB QueueManager, V7.0.1, linux) <---FireWall---> QmB (MSCS QueueManger Win 2008 server, running under an AD account).
QmA and QmB has channels and xmit queue setup for wmq communication to each other.
Communication between QmA and QmB works fine.
Now i have been trying to connect to QmB throught QmA with MQ explorer and runmqsc aswell. But all i get is a timeout thats says something like "command server not responding"(Command server is of course running on both boxes).
I have set up qmodel queues for MQExplorer, i have been trying all kind of security configurations, i have checked thats SYSTEM.ADMIN.COMMAND.QUEUE looks ok etc, etc...
I have noticed that he SDR channel on QmA starts, but the SDR channel back to QmA on QmB dosent.
What am i missing? Is this a security issue on QmB box? No hint in the logs either.
Best Regards!
//Blomman |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Mon Nov 12, 2012 12:13 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
runmqsc won't work.
When using MQExplorer, did you specifically say that the new qmgr should be added using "Connect using an intermediate queue manager"?
Is the name of the intermediate queue manager you specified the same as the name of the xmitq on QMB for QMA? |
|
| Back to top |
|
|
| Blomman |
| Posted: Mon Nov 12, 2012 12:24 pm Post subject: |
|
|
Master
Joined: 31 Oct 2006
Posts: 230
|
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Nov 12, 2012 12:50 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
So that means you can use runmqsc, as long as you are using runmqsc on the same machine as QmA. It didn't sound you like you were, it sounded like you were on a third machine. So that's why I said it won't work.
As long as you're running runmqsc on the same machine as QMA, then you can use runmqsc.
| Blomman wrote: |
| mqjeff wrote: |
When using MQExplorer, did you specifically say that the new qmgr should be added using "Connect using an intermediate queue manager"?
|
Yes i do that. |
I thought you did, but it never hurts to double-check.
| Blomman wrote: |
| mqjeff wrote: |
Is the name of the intermediate queue manager you specified the same as the name of the xmitq on QMB for QMA? |
No, can it?
Do you mean:
QmB(Xmitq:QmB) --> QmA? |
I mean that there must be an xmitq on QmB named 'QmA', and you need to have told MQ Explorer to use QmA.
It sounds like you do not have the reply path back from the command server on QmB working. So that's why it says the command server isn't working - because it's not getting back responses.
And you said the channel doesn't start, so that says that the reply messages aren't getting put on the xmitq tied to the channel (or maybe the channel isn't triggeredd?), so they're going to the wrong xmitq or to the DLQ or getting disposed. |
|
| Back to top |
|
|
| Blomman |
| Posted: Mon Nov 12, 2012 1:08 pm Post subject: |
|
|
Master
Joined: 31 Oct 2006
Posts: 230
|
Messy to quote one more time, answer like this..
Sorry not being clear enough, but runmqsc is supposed to work on QmB when i run it from QmA host.
Yes i have xmitq QmA on QmB.
Yes i have told MQ explorer to use QmA.
Other messages is triggering SDR channel on QmB, so not an triggering issue.
No messages on DLQ om QmB..
But probably the problem is QmB to sent the replys back to QmA, cant see the reason why. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Nov 12, 2012 1:14 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Yes, runmqsc is supposed to work if you run it on the machine that hosts QmA and tell it to connect to QmA and then talk to QmB remotely.
Yes, it does appear that the reply messages are the problem. If you are positive that the name of the xmitq is indeed *the same name* as the name of the receiving queue manager, then it's not clear what the issue is.
I would suggest trying to use a regular request/reply program to send messages to QMB from QMA and get them back as replies.
I would suggest stopping the channel from QMA to QMB, and trying to connect to QMB and then looking at the messages that should be sitting on the xmitq. Then you can look at the replytoqmgr name and verify what it it is. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Nov 12, 2012 5:21 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| mqjeff wrote: |
As long as you're running runmqsc on the same machine as QMA, then you can use runmqsc.
|
Looking at http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/topic/com.ibm.mq.amqzag.doc/fa11760_.htm
This seems to be contradicting your statement:
| Quote: |
| The source queue manager defaults to the default local queue manager. If you specify the -m LocalQmgrName option in the runmqsc command, you can direct the commands to be issued by way of any local queue manager. |
Nowhere is is specified that the remote qmgr needs to reside on the same box. What you do need though is a DEFAULT path to the remote qmgr and back. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Blomman |
| Posted: Tue Nov 13, 2012 2:06 am Post subject: |
|
|
Master
Joined: 31 Oct 2006
Posts: 230
|
| fjb_saper wrote: |
| mqjeff wrote: |
As long as you're running runmqsc on the same machine as QMA, then you can use runmqsc.
|
Looking at http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/topic/com.ibm.mq.amqzag.doc/fa11760_.htm
This seems to be contradicting your statement:
| Quote: |
| The source queue manager defaults to the default local queue manager. If you specify the -m LocalQmgrName option in the runmqsc command, you can direct the commands to be issued by way of any local queue manager. |
Nowhere is is specified that the remote qmgr needs to reside on the same box. What you do need though is a DEFAULT path to the remote qmgr and back. |
Probably what im missing is that the source queuemanger has to be the default queue manager, im not sure it is, will loook at this tomorrow when im back on site. I will test and let u know the result.
//Blomman |
|
| Back to top |
|
|
| exerk |
| Posted: Tue Nov 13, 2012 2:23 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| Blomman wrote: |
| Probably what im missing is that the source queuemanger has to be the default queue manager... |
The source queue manager does not have to be a default queue manager but you do need a 'default' path back from the target queue manager:
| Code: |
Queue Manager QMA -
SDR: QMA.TO.QMB
RCVR: QMB.TO.QMA
XMITQ: QMB
Queue Manager QMB -
SDR: QMB.TO.QMA
RCVR: QMA.TO.QMB
XMITQ: QMA |
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| Blomman |
| Posted: Tue Nov 13, 2012 3:11 am Post subject: |
|
|
Master
Joined: 31 Oct 2006
Posts: 230
|
| exerk wrote: |
| Blomman wrote: |
| Probably what im missing is that the source queuemanger has to be the default queue manager... |
The source queue manager does not have to be a default queue manager but you do need a 'default' path back from the target queue manager:
| Code: |
Queue Manager QMA -
SDR: QMA.TO.QMB
RCVR: QMB.TO.QMA
XMITQ: QMB
Queue Manager QMB -
SDR: QMB.TO.QMA
RCVR: QMA.TO.QMB
XMITQ: QMA |
|
This is basic intercommunication..
| Quote: |
Note: If you are using runmqsc with the -w option, source.queue.manager must be the default queue manager.
|
I dont want to put mqsc commands in a file all the time, not if it is necessary. |
|
| Back to top |
|
|
| zpat |
| Posted: Tue Nov 13, 2012 3:28 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
| It's easy to do with MO71. |
|
| Back to top |
|
|
| Blomman |
| Posted: Tue Nov 13, 2012 3:34 am Post subject: |
|
|
Master
Joined: 31 Oct 2006
Posts: 230
|
| zpat wrote: |
| It's easy to do with MO71. |
Ok, and how is MO71 gonna help me throught the firewall...?
//Blomman |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Nov 13, 2012 3:48 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
If qma has already punched through the firewall, why can't you get the same firewall access for an admin tool?
_________________
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 |
|
|
| exerk |
| Posted: Tue Nov 13, 2012 3:51 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| Blomman wrote: |
| exerk wrote: |
| Blomman wrote: |
| Probably what im missing is that the source queuemanger has to be the default queue manager... |
The source queue manager does not have to be a default queue manager but you do need a 'default' path back from the target queue manager:
| Code: |
Queue Manager QMA -
SDR: QMA.TO.QMB
RCVR: QMB.TO.QMA
XMITQ: QMB
Queue Manager QMB -
SDR: QMB.TO.QMA
RCVR: QMA.TO.QMB
XMITQ: QMA |
|
This is basic intercommunication..
| Quote: |
Note: If you are using runmqsc with the -w option, source.queue.manager must be the default queue manager.
|
I dont want to put mqsc commands in a file all the time, not if it is necessary. |
I know it's basic intercommunication but the question is whether you have an XMITQ explicitly named QMA or something like QMA.XMITQ - one will work, one will not; you've not really made clear in your posts which it is.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Nov 13, 2012 4:16 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| fjb_saper wrote: |
| mqjeff wrote: |
As long as you're running runmqsc on the same machine as QMA, then you can use runmqsc.
|
Looking at http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/topic/com.ibm.mq.amqzag.doc/fa11760_.htm
This seems to be contradicting your statement:
| Quote: |
| The source queue manager defaults to the default local queue manager. If you specify the -m LocalQmgrName option in the runmqsc command, you can direct the commands to be issued by way of any local queue manager. |
Nowhere is is specified that the remote qmgr needs to reside on the same box. |
I didn't say the remote qmgr needs to reside on the same box. QmA is the "local qmgr".
I said, and I continue to say, that runmqsc acts as a bindings application only. So you can't use it to talk to a queue manager that is not running on the same machine. |
|
| Back to top |
|
|
|
|
