| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Alias queue managers - |
« View previous topic :: View next topic » |
| Author |
Message
|
| rcp_mq |
 Posted: Wed Sep 25, 2013 10:29 am Post subject: Alias queue managers - |
 |
|
Centurion
Joined: 13 Dec 2011
Posts: 133
|
I didn't want to steal a poster's thread, so i'm creating a new one.
exerk: If the apps bind there's no way to 'fool' the app with a different name, and if the apps are client and passing a specific name that's been hard-coded then same thing. Queue manager aliases are more an internal routing/rerouting mechanism.
@exerk, So you mean 'fooling' does not work after the hard-coding right? |
|
| Back to top |
|
 |
| exerk |
| Posted: Wed Sep 25, 2013 3:50 pm Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
What I mean is, if the app is hard-coded to pass a queue manager name of QM1 (for example) and the new queue manager name is different, the app will get a non-zero return code of MQRC 2058. There's no way to spoof it into believing it is connecting to the 'right' queue manager that I am aware of.
Similarly, if a Client application, it will expect to get a connection to the queue manager whose name it passes to the client code - and I don't think wildcarding will work as it's the app that needs to pass a wildcard as a queue manager name.
As always, I'm happy to be proved wrong.
_________________
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 |
|
|
| JosephGramig |
| Posted: Thu Sep 26, 2013 5:51 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
exerk,
You are correct about MQCONN with a wildcard in front of the QmgrName. It is the application that must issue the MQCONN with an '*' asterisk as the first character and then the "QmgrName". But really what is going on is that when you put the * in front of the "name" it means you are using a "QmgrGroupName". The Client Channel Definition Table (CCDT which has a default name of AMQCLCHL.TAB) needs to have one or more channels defined with that "QmgrGroupName" without the asterisk. The WMQ Client code will then try them in a specific order which will be preferred and within that lexical order of the character set in use.
So, if the MQCONN always uses the * in front of the name, then and only then, could you "spoof" the QmgrName.
Of course, you could probably use a binary editor and find and change that QmgrName. In any case, this is why you should parametrize everything as much as possible.
more and more |
|
| Back to top |
|
|
| exerk |
| Posted: Thu Sep 26, 2013 6:13 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Joseph, I fully agree with everything you say, and it's my preference when configuring Client applications that the only queue manager name specified by an application is *, and the rest is left up to me so to speak.
But that still leaves the issue of an application binding to a queue manager, in which case it must specify the correct name - and as stated, I know of no way to fool one queue manager into accepting the name of another and allowing connection because that way madness lies - and again if the queue manager name is hard-coded into the app and it's a Client app then I suppose it's possible to edit the compiled app but I would think that the powers that be would go for what they would see as the easy option, which is a queue manager of the 'right' name.
_________________
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 |
|
|
| markt |
| Posted: Thu Sep 26, 2013 6:13 am Post subject: |
|
|
Knight
Joined: 14 May 2002
Posts: 508
|
| The preconn exit point does allow you to modify the qmgr - you don't need to be using * in the qmgr name for that to work. |
|
| Back to top |
|
|
| rcp_mq |
| Posted: Thu Sep 26, 2013 6:15 am Post subject: |
|
|
Centurion
Joined: 13 Dec 2011
Posts: 133
|
|
| Back to top |
|
|
| exerk |
| Posted: Thu Sep 26, 2013 8:31 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| markt wrote: |
| The preconn exit point does allow you to modify the qmgr - you don't need to be using * in the qmgr name for that to work. |
Provided that you code your Client app to use it - again we hit the brick wall of what would management see as being the easier solution, and generally that means the wrong one 
_________________
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 |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
