|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Local Environment tree not propagating through Compute node |
« View previous topic :: View next topic » |
Author |
Message
|
ashish_halge |
Posted: Fri Dec 18, 2009 2:48 am Post subject: Local Environment tree not propagating through Compute node |
|
|
Novice
Joined: 24 Aug 2008 Posts: 13 Location: Dubai, UAE
|
I have a flow with multiple computes nodes in it. I am setting some properties in LocalEnvironment tree in the first Compute node and would be using the same in further processing and at the end of the flow. But the Local Environment tree is not getting propagated through the proceeding Compute nodes even after setting the 'Compute Mode' property to 'All' or 'LocalEnvironmentAndMessage' on the Compute node in AIX. While on the Windows the same is getting propagated but when trying on AIX, its not getting propagated unless I manually copy it from InputRoot through ESQL. Kindly suggest the reason of the same. |
|
Back to top |
|
 |
mgk |
Posted: Fri Dec 18, 2009 3:53 am Post subject: |
|
|
 Padawan
Joined: 31 Jul 2003 Posts: 1642
|
ALL or LocalEnvrionmentAndMessage means that the NEW OutputLocalEnvrionment is propagated. If you want to propagate the InputLocalEnvrionment, do not use ALL or LocalEnvrionmentAndMessage or copy the InputLocalEvironment to the OutputLocalEnvrionment _________________ MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions. |
|
Back to top |
|
 |
ashish_halge |
Posted: Mon Dec 28, 2009 11:36 pm Post subject: |
|
|
Novice
Joined: 24 Aug 2008 Posts: 13 Location: Dubai, UAE
|
Thanks for the reply. So, what property should I set for the compute mode, if I want to propagate the InputLocalEnvironment details after the Compute node. Since, on Windows its working fine but giving problems on AIX. |
|
Back to top |
|
 |
rekarm01 |
Posted: Tue Dec 29, 2009 2:23 am Post subject: Re: Local Environment tree not propagating ... |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 1415
|
If it's working fine in Windows, but not in AIX, the more likely explanation is that either the two message flows are not the same, or the two broker versions are not the same, and handle message flow bugs differently.
Normally, Compute nodes can either propagate Input trees as-is, or create, populate, and propagate Output trees instead. Use the Compute Mode property to indicate which Output trees to propagate, by default:- If Compute Mode includes 'Message', then propagate OutputRoot; otherwise propagate InputRoot.
- If Compute Mode includes 'LocalEnvironment', then propagate OutputLocalEnvironment; otherwise propagate InputLocalEnvironment.
- If Compute Mode includes 'ExceptionList', then propagate OutputExceptionList; otherwise propagate InputExceptionList.
Output trees are initially empty; they require ESQL to populate them, particularly to copy the contents from the relevant Input trees. For example:
Code: |
SET OutputRoot = InputRoot;
SET OutputLocalEnvironment = InputLocalEnvironment;
SET OutputExceptionList = InputExceptionList; |
If a Compute node propagates an Output tree, but there is no corresponding ESQL to populate it, then the Compute node will propagate an empty tree.
For more details, please consult the documentation for Compute Nodes. |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
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
|
|
|
|