| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| WMBv8.0.0.1-> ma0i Support Pac |
« View previous topic :: View next topic » |
| Author |
Message
|
| broker_new |
 Posted: Mon Oct 08, 2012 4:08 pm Post subject: WMBv8.0.0.1-> ma0i Support Pac |
 |
|
Yatiri
Joined: 30 Nov 2006
Posts: 614
Location: Washington DC
|
Hi Guys,
We are using the ma0i support pac still which we have the risk of support from IBM. It is working great and consistently for last 7 years. I know that it can be easily replaced by DatabaseInput Node but i would like to bring up the discussion about Push vs Pull of the data.
It makes sense that oracle job use MQSERIES.PUT procedure to connect the Queue manager and put the message whenever the message/record is ready to be processed..what do you think..i am raising a RFE for it. 
_________________
IBM ->Let's build a smarter planet |
|
| Back to top |
|
 |
| marko.pitkanen |
| Posted: Mon Oct 08, 2012 9:42 pm Post subject: |
|
|
Chevalier
Joined: 23 Jul 2008
Posts: 440
Location: Jamsa, Finland
|
Hi,
I think that it is a good scheme if data owner publish data whenever it finds out that data is ready to be published. If data consumer must some how poll data from data owner there will always be additional processing or delay.
--
Marko |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Oct 09, 2012 2:48 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
I suppose one can consider the DatabaseInput node to be doing a poll/pull of data, since it's doing a periodic select for new records on the event table.
But the event table itself is populated through a push mechanism through the database trigger on the main table or tables.
So the data is pushed into a place where it's pulled from.
And even an MQInput node is periodically doing a pull of messages from the queue - it sits and does a get with wait and then sits and does another get with wait and then...
I'm sure you could replace the current setup, or even the databaseinput setup, with a trigger on the main table that calls a stored procedure that then writes a message to a queue or publishes it to a topic.
And I'm sure I'd do any one of the options being discussed where the circumstances were correct. |
|
| Back to top |
|
|
| zpat |
| Posted: Tue Oct 09, 2012 2:56 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
| MQinput node (MQGET with WAIT), will immediately process messages on arrival. It does not wait for an interval to elapse before doing so. So I would classify it as an event driven architecture, not a polling or timer driven one. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Oct 09, 2012 3:05 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| zpat wrote: |
| MQinput node (MQGET with WAIT), will immediately process messages on arrival. It does not wait for an interval to elapse before doing so. So I would classify it as an event driven architecture, not a polling or timer driven one. |
IF there are any messages waiting.
But, yes, I'll take your point that the get returns immediately and does not enforce a full timeout to expire.
However, a SELECT works the same way, except that you can't ask the select to just pause a bit in case a new row gets inserted, like a get with wait pauses just in case a new message gets inserted.
Again, this may be a bit philosophical and an impractical consideration, but this thread was raised as a discussion topic not on practical considerations. |
|
| 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
|
|
|
|
