| Author |
Message
|
| diego_maradona21 |
 Posted: Mon Aug 11, 2008 1:44 am Post subject: TimeoutNotification set to automatic fires only once |
 |
|
Novice
Joined: 24 Jul 2008
Posts: 17
|
Hi
I have to start message flow only once. I mean i need to start it immediately after deploy. I thought that TimeoutNotification node set to Automatic would do the trick but i cannot disable it just after it is fired (i could only disable nodes that are set to controlled).
Any suggestions? |
|
| Back to top |
|
 |
| AkankshA |
| Posted: Mon Aug 11, 2008 2:21 am Post subject: Re: TimeoutNotification set to automatic fires only once |
|
|
Grand Master
Joined: 12 Jan 2006
Posts: 1494
Location: Singapore
|
| diego_maradona21 wrote: |
Hi
I have to start message flow only once. I mean i need to start it immediately after deploy. ? |
The message flows get started automatically the moment you deploy them...
Not clear with the reqt of TimeOtNotification node here 
_________________
Cheers |
|
| Back to top |
|
|
| diego_maradona21 |
| Posted: Mon Aug 11, 2008 3:17 am Post subject: |
|
|
Novice
Joined: 24 Jul 2008
Posts: 17
|
ok so i will try to explain.
i have message flow that has to feed db table with some data. i have to repeat it after some time interval (different each flow so i have to control it by TimeoutNotification node set to controlled (named GetData_Time) - sometimes it's time interval is set to 100 sec, sometimes 120 sec etc) - i have no problem with that but i want to Fire it for the very first time cause when i use TimeoutNotification node set to controlled as very first node it wont be fired automatically. i have to trigger that flow so it feed table and set time interval on GetData_Time so it will now manage repeating of this operation. I tried to set TimeoutNotification set to Automatic as first node to start the whole operation, but i can't stop it - it will repeat and GetData_Time will be repeated also.
So what i have to do is set TimeoutNotification node (Automatic) as very first node and right after it is triggered - CANCEL it. |
|
| Back to top |
|
|
| sridhsri |
| Posted: Mon Aug 11, 2008 4:49 am Post subject: |
|
|
Master
Joined: 19 Jun 2008
Posts: 297
|
| You could try setting a very large timeout interval for the TN Node. I believe the max value is 1 short of 1 million. |
|
| Back to top |
|
|
| vaibhav_vy |
| Posted: Wed Aug 13, 2008 9:22 pm Post subject: |
|
|
Apprentice
Joined: 04 Aug 2008
Posts: 28
|
Even using very large timeout wont solve this problem as eventually it will be triggered after that.
What you can do is make use of Cache nodes. These nodes are available as fixpack IA91. When the first time your flow triggers, you can check whether it gets triggered in past by checking value in the Broker Cache. If its not set, it means its first invocation. Then set cache variable in Broker Cache. You can set it either at execution group level or Broker domain level as per your requirement. Next time when it will be triggered, value will be available in cache & you can terminate the flow there. |
|
| Back to top |
|
|
|
|
