| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Can a channel exit route messages ? |
« View previous topic :: View next topic » |
| Author |
Message
|
| fjb_saper |
 Posted: Fri Jun 25, 2010 11:01 am Post subject: |
 |
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Mr Butcher wrote: |
i dont understand the question. for me it makes no difference. the exit can modify the queue name or leave it. the new target may apply to a local defined qlocal ueue, to a local definition of a remote queue or to a remote queue (in that case the qmgr must be known). that thats the same in every case, with or without exit.
there are may "and if" questions. as i wrote before, it depends on the situation. ... and in some situations i would use that exit solution. in some not. |
Sure but what I don't quite get is how the exit will deal with CCSID translations. Remember that this is supposed to handle content routing.
Messages can come from multiple sources and with multiple CCSIDs...
An application that does the routing can take advantage of MQ's automatic CCSID translation...
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Fri Jun 25, 2010 11:39 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
I don't see CCSID as an issue.
For CONVERT(YES) on sender, sender platform does conversion, no issue.
On receiving end, consuming app MQGMO_CONVERT drives conversion after message arrives on destination queue, wherever that might be - no issue.
Am I missing something?
[edit]Now I see it: if the CCSIDs of sending and receiving ends are different, AND the consuming app intends to MQGMO_CONVERT, the exit will inherit the unconverted message. How would the exit app look at the payload? Do a hone-grown conversion in the exit?
Ah! What could possibly go wrong? 
_________________
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.
Last edited by bruce2359 on Fri Jun 25, 2010 2:07 pm; edited 2 times in total |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri Jun 25, 2010 12:07 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Moved to User Exits.
_________________
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: Fri Jun 25, 2010 1:15 pm Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
And I suppose what we are all missing here, is the fact that a channel exit cannot (strictly speaking) route a message; change RNAME and/or RQMNAME, yes, but for it to alter the route it would have to have the ability to put it on another transmission queue from that which the channel agent has pulled it, and that aspect of using an exit opens up a whole new can of worms...
_________________
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 |
|
|
| bruce2359 |
| Posted: Fri Jun 25, 2010 1:58 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
The APR (or APG) says that all MQI calls can be used in an exit, but recommends that exits not use MQBEGIN, MQCMIT, MQBACK. Worms, indeed.
_________________
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 |
|
|
| fatherjack |
| Posted: Fri Jun 25, 2010 2:35 pm Post subject: |
|
|
Knight
Joined: 14 Apr 2010
Posts: 522
Location: Craggy Island
|
| exerk wrote: |
| And I suppose what we are all missing here, is the fact that a channel exit cannot (strictly speaking) route a message; change RNAME and/or RQMNAME, yes, but for it to alter the route it would have to have the ability to put it on another transmission queue from that which the channel agent has pulled it, and that aspect of using an exit opens up a whole new can of worms... |
Yes. And that's what i was trying to suggest when i said
| fatherjack wrote: |
| And if the destination queue is on a different queue manager? |
Sure you can change the destination queue name in the exit to something which may be a remote queue def on the destination qmgr or even change both the destination queue and queue manager names but then there's potentially a whole bunch of MQ admin to make sure messages can get to all ultimate destination queues, not to mention the mapping data the exit needs access to in order to derive the destination queue and queue manager names.
It all just seems a bit tricky to me when there are much simpler solutions.
_________________
Never let the facts get in the way of a good theory. |
|
| Back to top |
|
|
|
|
|
|
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
|
|
|
|
