ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Scheduling with Timer nodes

Post new topic  Reply to topic
 Scheduling with Timer nodes « View previous topic :: View next topic » 
Author Message
Sam Uppu
PostPosted: Sat Feb 13, 2010 10:26 pm    Post subject: Scheduling with Timer nodes Reply with quote

Yatiri

Joined: 11 Nov 2008
Posts: 610

Hi Guys,

We have a requirement where we need to trigger out message flow at 10:00PM daily.

I am thinking to use timer nodes for the implementation.

The flow design is as follows.

Timeoutnotification_start ---> COmpute1 ---> Timeoutcontrol_daily


Timeoutnotification_daily --->compute2 ----MQoutputnode



The parameters on Timeout notification_start are Mode is Automatic and interval is 82800.


I have prepared the timeout request message on compute1 node with Starttime as 22:00, count as -1 and interval as 86400.



When the message flow is first deployed, the Timeoutnotification_start sends a control message and the compute1 node generates the
timeout request message to start the flow at 22:00.

The message flow is triggered at 22:00. And since the interval on timeout request message is 86400, the flow has to be triggered daily at 22:00.


Next day ie., after 82800 seconds another control message is sent by the Timeoutnotification_start node which makes compute node1 to generate another
timeoutrequest message.

I am wondering if the first timeout request message sent by timeoutcontrol_daily to trigger the flow for every 86400(2nd day) will be overridden by the timeout request message sent on 2nd day?

Will this generate any exceptions?
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Sun Feb 14, 2010 5:53 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

check out the documentation. There are a few flags in the message. It should answer your questions.

Have fun
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
balaji83it
PostPosted: Wed Feb 17, 2010 12:20 am    Post subject: Reply with quote

Acolyte

Joined: 20 Jul 2007
Posts: 72

Hello Sam,

I faced a similar problem. You can do the following.

Set a big value for the 1st timeoutnotif node. The value which I gave was approx 32 years. Calc the same in seconds.


So the 1st time out notif will trigger a 2nd message only after 32 years.


Thanks,
KONIJETI BALAJI.
Back to top
View user's profile Send private message
Sam Uppu
PostPosted: Wed Feb 17, 2010 1:39 pm    Post subject: Reply with quote

Yatiri

Joined: 11 Nov 2008
Posts: 610

balaji83it wrote:
Hello Sam,

I faced a similar problem. You can do the following.

Set a big value for the 1st timeoutnotif node. The value which I gave was approx 32 years. Calc the same in seconds.


So the 1st time out notif will trigger a 2nd message only after 32 years.


Thanks,
KONIJETI BALAJI.


I think by setting AllowOverwrite to True, the contol message will be overridden.

Let me know if I am wrong.
Back to top
View user's profile Send private message
balaji83it
PostPosted: Wed Feb 17, 2010 10:18 pm    Post subject: Reply with quote

Acolyte

Joined: 20 Jul 2007
Posts: 72

I think overwrite will not work. If you want to overwrite a timer request, the id needs to be same.


Also why do you want to unnecessarily generate timeout notfi requests from the 1st timeout notification node?

Internally all these msgs will be store in a queue which will impact the performance.

So my suggestion would be to use a big value for the 1st timeout notif node.
Back to top
View user's profile Send private message
Sam Uppu
PostPosted: Fri Feb 19, 2010 11:31 am    Post subject: Reply with quote

Yatiri

Joined: 11 Nov 2008
Posts: 610

balaji83it wrote:
I think overwrite will not work. If you want to overwrite a timer request, the id needs to be same.


Also why do you want to unnecessarily generate timeout notfi requests from the 1st timeout notification node?

Internally all these msgs will be store in a queue which will impact the performance.

So my suggestion would be to use a big value for the 1st timeout notif node.



I think I can use a bigger value on the first timeout notification node.

I know that first timeout notification node sends the first control message
after the flow is deployed.

I am wondering if the borker goes down for some time,may be any reason and later comes back, will the first timeoput notification node send the control message once the broker is up?
Back to top
View user's profile Send private message
balaji83it
PostPosted: Fri Feb 19, 2010 11:24 pm    Post subject: Reply with quote

Acolyte

Joined: 20 Jul 2007
Posts: 72

yes the timeout notif sends msg once the broker is up. Then you can use a overwrite option for the msg u r setting in 1st timeot
control.

So to summarize use a combination of big value in timeout notif and allowoverwrite =true in 1st compute node.

Hope this solves your problem.




Thanks

KONIJETI BALAJI.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Scheduling with Timer nodes
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.