| Author |
Message
|
| gag_nm |
 Posted: Mon Nov 18, 2013 12:42 am Post subject: Queue manager Alias- reply-to-Queue |
 |
|
Centurion
Joined: 16 Oct 2008
Posts: 102
|
we have three Queue managers(QA,QB,QC).
we want to send messages to LQ3 of QC through QB and reply back to LQ1 on LQA using reply-to-queue.
| Code: |
On QMA
we defined below queues
DEF QR(QMC) RQMNAME(' ') RNAME(' ') XMITQ(QMB)
DEF QR(QC) RQMNAME('QMC') RNAME(' ') XMITQ('QMC')
DEF QL(QMB) USAGE(XMITQ) TRIGTYPE(FIRST) TRIGGER
on QMB
DEF QL(QMC) USAGE(XMITQ) TRIGTYPE(FIRST) TRIGGER
on QMC
DEF QL(QC)
|
how do i setup for response back on LQ1 on QA using reply-toQueue mentioned in request message.
please provide some information to achieve this.... |
|
| Back to top |
|
 |
| PaulClarke |
| Posted: Mon Nov 18, 2013 4:16 am Post subject: |
|
|
Grand Master
Joined: 17 Nov 2005
Posts: 1002
Location: New Zealand
|
I'm not sure I understand your question. Why could the application not just add the transmission queue definitions for the way back like this ?....
on QMB
DEF QL(QMA) USAGE(XMITQ) TRIGTYPE(FIRST) TRIGGER
on QMC
DEF QL(QMB) USAGE(XMITQ) TRIGTYPE(FIRST) TRIGGER
DEF QR(QMA) RQMNAME(' ') RNAME(' ') XMITQ(QMB)
Then the application can specify whatever reply queue it likes on QMA and get the responses back.
Cheers,
Paul.
_________________
Paul Clarke
MQGem Software
www.mqgem.com |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Nov 18, 2013 4:28 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| PaulClarke wrote: |
| Then the application can specify whatever reply queue it likes on QMA and get the responses back. |
And now, anyone connected to QMC has full access to the command server on QMA. |
|
| Back to top |
|
|
| PaulClarke |
| Posted: Mon Nov 18, 2013 4:42 am Post subject: |
|
|
Grand Master
Joined: 17 Nov 2005
Posts: 1002
Location: New Zealand
|
| Quote: |
| And now, anyone connected to QMC has full access to the command server on QMA. |
That's a bit like saying that anyone who is connected to QMA has full access to the command server.
Are you implying that if you connect to a queue manager that you then have no control over security? Clearly that statement would be ridiculous.
There are, no doubt, security implications whenever one machine is connected to another. I didn't get the feeling that the question was about security though, but more about routing.
Cheers,
Paul.
_________________
Paul Clarke
MQGem Software
www.mqgem.com |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Nov 18, 2013 5:04 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
I agree the question is not about security.
My point is that the route you have described does exactly what you have said it does. It allows any application connected to QMC to send a message to any queue on QMA.
Perhaps it's unnecessary for me to state that this also includes the command server queue. But I thought it might be helpful to do so.
Perhaps it's pessimistic of me to expect that the channel to QMA does nothing to provide any security measures. But I don't believe it's *unrealistic* to think that. |
|
| Back to top |
|
|
| PaulClarke |
| Posted: Mon Nov 18, 2013 5:15 am Post subject: |
|
|
Grand Master
Joined: 17 Nov 2005
Posts: 1002
Location: New Zealand
|
I think we all agree that securing your channels and your queues is a good thing. However, in the original question there were these definitions.
| Quote: |
On QMA
we defined below queues
DEF QR(QMC) RQMNAME(' ') RNAME(' ') XMITQ(QMB)
DEF QR(QC) RQMNAME('QMC') RNAME(' ') XMITQ('QMC')
DEF QL(QMB) USAGE(XMITQ) TRIGTYPE(FIRST) TRIGGER
on QMB
DEF QL(QMC) USAGE(XMITQ) TRIGTYPE(FIRST) TRIGGER
on QMC
DEF QL(QC)
|
This allows anyone on QMA to target any queue on QMB or QMC and anyone on QMB to target queues on QMC. All I did was point out that the mirror set of definitions would get the response back again.
I fail to see how the mirror set of definitions is more innately insecure than anything else. Why is the direction of QMC to QMA your only cause for concern ? As I said, securing channels and queues is another topic albeit an important one.
_________________
Paul Clarke
MQGem Software
www.mqgem.com |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Nov 18, 2013 6:19 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
I agree!
I merely thought it would be helpful to mention the security aspects here. |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Mon Nov 18, 2013 6:31 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
Like, you need to inject the msg with an authorized ID in the MQMD for the command server to do what you ask it to do. Not to mention you had to inject a command msg.
Pessimistic? You Jeff? No way...  |
|
| Back to top |
|
|
| gag_nm |
| Posted: Thu Dec 19, 2013 12:20 am Post subject: |
|
|
Centurion
Joined: 16 Oct 2008
Posts: 102
|
hi
Using Rhfutl , trying to send message to this QMC, but i am receving
*Error cc=2 rc=2184 Cannot Open as error. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Dec 19, 2013 6:23 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9486
Location: US: west coast, almost. Otherwise, enroute.
|
Search here, or on google, for ReasonCode 2184.
_________________
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 |
|
|
| fjb_saper |
| Posted: Sun Dec 22, 2013 9:24 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20767
Location: LI,NY
|
| Quote: |
| DEF QR(QMC) RQMNAME(' ') RNAME(' ') XMITQ(QMB) |
Should have been defined as:
| Code: |
| DEF QR(QMC) RQMNAME('QMC ') RNAME(' ') XMITQ(QMB) |
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
