| Author |
Message
|
| hopiee |
 Posted: Fri May 17, 2013 11:09 pm Post subject: Timer control & notification node for batch processing |
 |
|
Newbie
Joined: 17 May 2013
Posts: 9
|
Understood that timer control shall have the UID to be associated with one timer notification node. But I need to have a message flow that is flexible enough to hold multiple scheduler (for batch processing) for future expansion, in such, different request from multiple system would have different scheduler/ timestamp to kick start the batch processing.
Example:
System A would like to have scheduler daily 6AM.
System B would like to have scheduler daily 7AM.
In timer request, i would have two UID eg:
A_SCH_0600
B_SCH_0700
At the same time, in the message flow i would have two timer notification nodes to associate with this two UID.
But if in future, i would have 10 systems integrated and each would have their respective scheduler timing. Does it means that i need to create 10 timer notification? 
Is there any other alternative or suggestion? Currently what's in my mind: using a timer notification (which trigger hourly) to extract the data from DB, in which it contains the message to process & time to process in batch.
 |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Sat May 18, 2013 4:06 am Post subject: Re: Timer control & notification node for batch processi |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| hopiee wrote: |
Currently what's in my mind: using a timer notification (which trigger hourly) to extract the data from DB, in which it contains the message to process & time to process in batch.
|
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| McueMart |
| Posted: Mon May 20, 2013 12:15 am Post subject: |
|
|
Chevalier
Joined: 29 Nov 2011
Posts: 490
Location: UK...somewhere
|
A good alternative is to use something other than timer nodes to invoke your flow (Cron on Linux / Scheduled Tasks on Windows).
Saying that, I think having a timer node that runs automatically every X time, and pulls config data from a DB isnt at all bad. |
|
| Back to top |
|
|
| kash3338 |
| Posted: Mon May 20, 2013 1:39 am Post subject: |
|
|
Shaman
Joined: 08 Feb 2009
Posts: 709
Location: Chennai, India
|
| Using Timer Notification/Control nodes by fetching the trigger details from DB and by making use of the Timer XML, you can achieve this scenario. |
|
| Back to top |
|
|
| hopiee |
| Posted: Tue May 21, 2013 2:31 am Post subject: |
|
|
Newbie
Joined: 17 May 2013
Posts: 9
|
Thanks for all the input. After had the discussion, it is decided to use timer node to perform hourly db extraction which consist the schedule time provided from application. The schedule time which could have varies from hourly, daily, weekly on certain day n even up to quarterly. So we would not need to suffer to cater for future incoming scheduler request. As well as the worries for the timer in system.timer queue would be missing after server or MSG flow clashed etc.
This really require support n maintenance to ensure all schedulers are in order.
Good day!  |
|
| Back to top |
|
|
| ganesh |
| Posted: Tue May 21, 2013 6:20 am Post subject: |
|
|
Master
Joined: 18 Jul 2010
Posts: 294
|
Has anyone faced problems with timeout notification node not firing at the set time or has any one noticed this node to be working intermittently ?
Broker - 7.0.0.3
OS - Solaris. |
|
| Back to top |
|
|
|
|
