|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
How to pause in a node? |
« View previous topic :: View next topic » |
Author |
Message
|
jefflowrey |
Posted: Tue Aug 15, 2006 4:50 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
Instead of the Timer node, you could implement your own solution using a JCN and a thread.
You can't do this at all in ESQL.
You can also store the configuration data in something else - like a database or a User Defined Property. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
pcelari |
Posted: Tue Aug 15, 2006 5:03 am Post subject: |
|
|
Chevalier
Joined: 31 Mar 2006 Posts: 411 Location: New York
|
Again, many thanks for all the inputs.
Hopefully, this thread will inspire / challenge some expert to add a simple DelayNode to the repository.
Beyond complexity, the one thing I don't like using the Timeout nodes is the fact that the delay has to be hardcoded in ESQL, and so not run-time configurable as I'm currently doing with my triggered program. _________________ pcelari
-----------------------------------------
- a master of always being a newbie |
|
Back to top |
|
 |
jefflowrey |
Posted: Tue Aug 15, 2006 5:08 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
It is runtime configurable!
You can either use a User Defined Property to configure the delay time for a specific flow - and change this every time you redeploy.
Or you can store the delay time in any other store - database, queue, file (accessed from a JCN), etc.
And then you can build a Timeout Control Message that uses this information to set the delay time. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
|
|
|
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
|
|
|
|