| Author |
Message
|
| siljcjose |
 Posted: Thu Jun 25, 2009 2:14 am Post subject: Environment variables and Timer Nodes |
 |
|
Apprentice
Joined: 18 Aug 2005
Posts: 27
|
Hi,
We have a requirement, where we need to persist some data before sending it to the Timer Control node and get that data back once we have the Out via the TimeOut Notification node. We tried using the environment variables to do that. But we are not getting the environment variables through. It is dropped when the message comes out of the Notification Node.
Please can somebody let us know, if we can use Environment variables for this purpose, when using Timer Control and Notification node.
Thanks. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Thu Jun 25, 2009 2:17 am Post subject: Re: Environment variables and Timer Nodes |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| siljcjose wrote: |
| Please can somebody let us know, if we can use Environment variables for this purpose, when using Timer Control and Notification node. |
Environment variables don't last past the execution of the flow that creates them.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| siljcjose |
| Posted: Thu Jun 25, 2009 2:38 am Post subject: |
|
|
Apprentice
Joined: 18 Aug 2005
Posts: 27
|
| Does this mean that the introduction of a timer control and Notification node in the flow, makes the involved flows behave as independent flows ? |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Thu Jun 25, 2009 2:43 am Post subject: Re: Environment variables and Timer Nodes |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| Vitor wrote: |
Environment variables don't last past the execution of the flow that creates them. |
This is true unless they are shared environment variables. This might be a solution to the problem.
_________________
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 |
|
|
| satya2481 |
| Posted: Thu Jun 25, 2009 5:32 am Post subject: |
|
|
Disciple
Joined: 26 Apr 2007
Posts: 170
Location: Bengaluru
|
Is there any solution to over come this issue?
Where can we store the values or details which are needed to be used to perform some business logic after the Notification node....
Using the shared variables is only the options?
Cant we store the details in LocalEnvironment? Because I tried to debug the flow and checked the Presence of LocalEnvironmennt tree at the ouput terminal of Notification node.
_________________
IBM Certified Solution Developer WebSphere Message Broker V6.0
IBM Certified System Administrator WebSphere MQ V6.0 |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Jun 25, 2009 5:36 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
TimeoutNotification is an *input* node.
It starts a new message flow instance, just like every other Input node.
Data stored in the Environment tree can not be shared between message flow instances.
Data stored in ESQL Shared variables can be, as long as the instances are on the same EG.
Data stored in the message passed to the TimeoutControl node is available at every instance of the TimeoutNotification node that uses the same UniqueID. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jun 25, 2009 5:50 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| satya2481 wrote: |
| Cant we store the details in LocalEnvironment? Because I tried to debug the flow and checked the Presence of LocalEnvironmennt tree at the ouput terminal of Notification node. |
If you'd even looked at the documentation before posting, you'd realise why that's a really stupid thing to say.
And no, you can't pass details to another flow in LocalEnvironment. Logically, if the Environment is flow specific (as I said above) a LocalEnvironment from it's name should indicate it has an even smaller scope. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| telecoda |
| Posted: Thu Jun 25, 2009 6:50 am Post subject: |
|
|
Novice
Joined: 05 Feb 2008
Posts: 15
|
Can the data you need to persist not be added to the message you are sending to the Timer control node?
Therefore when your flow effectively wakes up you'll have the information you require?
Either that or look at the Coordinated Request Reply sample that uses an additional message queue to persist information based upon correlation with a message id. |
|
| Back to top |
|
|
| AkankshA |
| Posted: Thu Jun 25, 2009 9:03 pm Post subject: Re: Environment variables and Timer Nodes |
|
|
Grand Master
Joined: 12 Jan 2006
Posts: 1494
Location: Singapore
|
| siljcjose wrote: |
Hi,
We have a requirement, where we need to persist some data before sending it to the Timer Control node and get that data back once we have the Out via the TimeOut Notification node. We tried using the environment variables to do that. But we are not getting the environment variables through. It is dropped when the message comes out of the Notification Node.
Please can somebody let us know, if we can use Environment variables for this purpose, when using Timer Control and Notification node.
Thanks. |
You can use usr folder of MQRFH2 header to store the details and they ll survive across timeout notification node...
Otherwise, you can think about using database for this....
_________________
Cheers |
|
| Back to top |
|
|
|
|
