| Author |
Message
|
| elixir9999 |
 Posted: Thu Sep 24, 2015 3:59 am Post subject: Timeout Notification Node Dilemna - Need a workaround |
 |
|
Novice
Joined: 24 Sep 2015
Posts: 10
|
Hi Experts
I am a Newbie to WMB and We have a requirement for Kicking Off a Msg Flow at 10 P.M each night.
After alot of Googling, I have suggested 2 ways to them -
1. Use a CronJob to put a msg on the Input Q to start the flow.
2. Use Timeout Notification node.
They have declined option 1 saying that IBM doesn't support cron jobs anymore, so we can't put that on the server.
For option 2, they are still fine but I have a question - Today i deploy the flow at the exact same time when I want it to et triggered after 24 Hrs but what happens when the Server is rebooted or the Flow is Stopped and started.
Will the timer also start again from that moment and If Yes is there any Workaround this problem of rebooting or restarting that can be followed, so the flow is kicked off on the exact same time at 10 P.M irrespective even if it was redeployed or something like that.
We also have TWS in our environment, But I could not find any Integration documents or scenarios of TWS integration with IIB, Could you kindly give your valuable advices or comments - How can I reach to an efficient solution.
Thanks
Sumit[/b] |
|
| Back to top |
|
 |
| Vitor |
| Posted: Thu Sep 24, 2015 4:12 am Post subject: Re: Timeout Notification Node Dilemna - Need a workaround |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| elixir9999 wrote: |
| They have declined option 1 saying that IBM doesn't support cron jobs anymore, so we can't put that on the server. |
Who are "they" and when did IBM start supporting cron? Last time I looked cron was a utility provided with Unix. So IBM would only support it (or not) on AIX and if AIX doesn't support cron any more I must have missed the technote.
FWIW we use cron for our flow scheduling, though as a pattern we prefer to be event driven.
| elixir9999 wrote: |
| For option 2, they are still fine but I have a question - Today i deploy the flow at the exact same time when I want it to et triggered after 24 Hrs |
And in 6 months someone will redeploy the flow with a fix at the wrong time.
| elixir9999 wrote: |
| Will the timer also start again from that moment |
Yes
| elixir9999 wrote: |
If Yes is there any Workaround this problem of rebooting or restarting that can be followed so the flow is kicked off on the exact same time at 10 P.M irrespective even if it was redeployed or something like that.
|
No.
| elixir9999 wrote: |
| We also have TWS in our environment, But I could not find any Integration documents or scenarios of TWS integration with IIB, |
Get it to drop a message on a queue, like option 1.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Thu Sep 24, 2015 4:35 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
With a little thought you could write code in a flow that uses timer nodes that would make an event fire at the same time every day.
I use this in many places. Well actually our event are times to fire every minute at 30 seconds past the minute mark
Then a DB table holds all the information about when messages should be sent when and to whom.
We also use Zcron to run jobs that are outside MQ or Broker. This is on windows.
As for cron?
cron is a key part of any core Unix System. Everyone uses it.
It would be pretty simple to write a script to put a messageonto a queue when the cron job runs. The supplied command line tool amqsput is actually ideal for this sort of simple application.
I'd go back to whoever said that IBM does not support cron. If you are running on AIX then of course they do. Cron is part of the OS.
Get them to show you in writing where IBM has said this. I am sure that a good number of people here would be interested in finding that out.
IBM AIX 7.1 Info Centre has all the help about Cron that you could need.
https://www-01.ibm.com/support/knowledgecenter/ssw_aix_71/com.ibm.aix.cmds1/cron.htm?lang=en
Just for starters.
_________________
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 |
|
|
| elixir9999 |
| Posted: Thu Sep 24, 2015 5:07 am Post subject: |
|
|
Novice
Joined: 24 Sep 2015
Posts: 10
|
"With a little thought you could write code in a flow that uses timer nodes that would make an event fire at the same time every day."
In our flow the timeout Notification node is the very first Node only, No nod before that since it is used to just trigger the flow on the exact same time each day.
So, not sure how i can use the First node in any other node that follows, Sorry that is just what I am thinking if it could be achieved, please do let me know - will definitely try that too...
Thanks |
|
| Back to top |
|
|
| elixir9999 |
| Posted: Thu Sep 24, 2015 5:11 am Post subject: |
|
|
Novice
Joined: 24 Sep 2015
Posts: 10
|
Thank you VITOR for your reply.
"Who are "they" " - They stand for our SME's.
IBM has said that if we deploy CronJob on our AIX servers then they won't support it as they want to sell TWS to more and more Enterprises now and we are forced to remove some of the already running CronJobs as well.
For TWS, Can you please guide me to any Documentation present or any Example or scenarios where I can study how to integrate TWS with IIB or MQ , I tried alot but couldn't find anything realted to these together.
Thanks |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Sep 24, 2015 5:29 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| elixir9999 wrote: |
| "Who are "they" " - They stand for our SME's. |
I would put it to you they're not as "expert" as they claim
| elixir9999 wrote: |
| IBM has said that if we deploy CronJob on our AIX servers then they won't support it as they want to sell TWS to more and more Enterprises now and we are forced to remove some of the already running CronJobs as well. |
IBM is a house of many mansions - quote name / area within IBM. Also please post the link where IBM withdraws support of cron on AIX for the benefit of those of us who use cron on AIX.
| elixir9999 wrote: |
| For TWS, Can you please guide me to any Documentation present or any Example or scenarios where I can study how to integrate TWS with IIB or MQ , I tried alot but couldn't find anything realted to these together. |
I doubt there's any direct integration between TWS and IIB / MQ, though I'm not an expert on it. As I suggested above, your best bet is probably to get TWS to drop a message on a queue.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Thu Sep 24, 2015 5:37 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| elixir9999 wrote: |
"With a little thought you could write code in a flow that uses timer nodes that would make an event fire at the same time every day."
In our flow the timeout Notification node is the very first Node only, No nod before that since it is used to just trigger the flow on the exact same time each day.
So, not sure how i can use the First node in any other node that follows, Sorry that is just what I am thinking if it could be achieved, please do let me know - will definitely try that too...
Thanks |
When a flow is started that uses A Timeout Notification Node [1], the timeout actually fires and produces a message. If this is wired to a Compute then some ESQL can be used to then schedule the firing of ANOTHER Notification Node[2] via a Timeout Control Node. The params on that node [1] should be set to repeat itself say every 7 days. The ESQL would determine the time to go before the desired time for the main job. Then that node would also be set (in the ESQL) to fire every 24 hours.
If you doubt me, deploy a flow, stop it. Enable user trace, start the flow, disable user trace and extract the log data.
_________________
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 |
|
|
| vishnurajnr |
| Posted: Thu Sep 24, 2015 7:39 pm Post subject: |
|
|
Centurion
Joined: 08 Aug 2011
Posts: 134
Location: Trivandrum
|
There is well known article in DeveloperWorks which explains the programming patterns for timer nodes.
I hope you already read this. For your requirement, worth to apply Timeout Notification and Timeout Control node combinations as mentioned by smdavies99. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Thu Sep 24, 2015 9:47 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| vishnurajnr wrote: |
There is well known article in DeveloperWorks which explains the programming patterns for timer nodes.
I hope you already read this. For your requirement, worth to apply Timeout Notification and Timeout Control node combinations as mentioned by smdavies99. |
I'll second that advice. When I wrote the original version of my flow around 2006 that article was very helpful.
We use the latest version (Mk V) in all our systems.
_________________
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 |
|
|
|
|
