| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Dynamically change the MQOutput Node connection properties |
« View previous topic :: View next topic » |
| Author |
Message
|
| mhasan23 |
 Posted: Thu Oct 12, 2017 10:01 pm Post subject: Dynamically change the MQOutput Node connection properties |
 |
|
Novice
Joined: 12 Oct 2017
Posts: 20
|
I am working on a message flow in which BLOB messages are sent to MQOutput Node.
Flow: MQInputNode -> Compute Node -> MQOutputNode
As all the information about MQ like MQ Manager, Channel, Port and Hostname and Port are setup in database. Currently I have set the Queue Manager and Queue Name property of MQOutput node successfully from ESQL Compute Node. Now the problem is that how would I set the Queue Manager Hostname and Listner Port and Channel Name of queue manager. All this work I have to done via ESQL, can anyone have the solution for this. |
|
| Back to top |
|
 |
| zpat |
| Posted: Thu Oct 12, 2017 11:54 pm Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5849
Location: UK
|
You don't need to do it this complex way.
Assuming you do have a QM running on the same host as the message broker, just put the message to a queue on that local QM.
That queue can be a cluster queue or remote queue in the usual MQ style to forward the messages to another QM.
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Oct 13, 2017 4:58 am Post subject: Re: Dynamically change the MQOutput Node connection properti |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mhasan23 wrote: |
| As all the information about MQ like MQ Manager, Channel, Port and Hostname and Port are setup in database. |
Why? One of the reasons people pay a lot of money for MQ is that it handles all this sort of thing on behalf of the application. It's very anti-pattern (and in my view not best practice) to have this information at an application level (and IIB is an application in this context).
| mhasan23 wrote: |
| Now the problem is that how would I set the Queue Manager Hostname and Listner Port and Channel Name of queue manager. All this work I have to done via ESQL |
The MQOutput node doesn't accept connection details via ESQL, only the destination queue manager name and destination queue name. This is by design, for the reasons I give above.
| mhasan23 wrote: |
| can anyone have the solution for this. |
Use MQ in the way it's designed to be used, as my associate describes. If you're using IIBv10 you have a choice of which queue manager to use, while in v9 you're fixed to the queue manager associated with the broker.
Neither version allows you to vary connections at run time via ESQL.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| 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
|
|
|
|
