The LocalEnvironment tree has its own correlation name, LocalEnvironment, and you must use this in all ESQL statements that refer to or set the content of this tree.
The LocalEnvironment tree is used by the broker, and you can refer to and modify this information. You can also extend the tree to contain information that you create yourself. You can create subtrees within this tree that you can use as a scratchpad or working area.
This topic describes how to refer to the information that is set up by the broker. Using scratchpad areas in LocalEnvironment describes how to extend the contents of this tree for your own purposes.
The message flow sets up information in two subtrees, Destination and WrittenDestination, below the LocalEnvironment root. You can refer to the content of both of these, and can write to them to influence the way in which the message flow processes your message. However, if you write to these areas, ensure that you follow the defined structure to ensure that the tree remains valid. For more details of their content, see LocalEnvironment tree.
If you want the LocalEnvironment tree to be included in the output message that is propagated by the Compute node, ensure that you copy this tree by setting the Compute node property Compute mode to a value that includes LocalEnvironment (for example, All). If you do not, the LocalEnvironment tree is not included in the output message.
DECLARE cursor REFERENCE TO LocalEnvironment.Destination.MQ; IF LASTMOVE(cursor) THEN
SET cursor.DestinationData.queueManagerName = 'myNewQManagerName'; SET cursor.DestinationData.queueName = 'myNewQueueName';
For information about the full list of elements in the Defaults and DestinationData subtrees, see Data types for elements in the DestinationData subtree.
For another example of how you can use LocalEnvironment to modify the behavior of a message flow, refer to the XML_PassengerQuery message flow in the Airline sample program. The Compute node in this message flow writes a list of destinations in the RouterList subtree of Destination that are used as labels by a later RouteToLabel node that propagates the message to the corresponding Label node.
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ac16860_ |