The local environment tree has its own correlation name, LocalEnvironment, and you must use this name in all ESQL statements that refer to or set the content of this tree.
You can refer to and modify the information in the local environment tree. You can also extend the tree to contain information that you create yourself. You can create subtrees of this tree that you can use as a scratchpad or working area.
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 subtrees, and you can write to the Destination tree to influence the way in which the message flow processes your message. However, if you write to the Destination tree, follow the defined structure to ensure that the tree remains valid.
If you want the local environment tree to be included in the output message that is propagated by the Compute node, you must set the Compute node property Compute mode to a value that includes the local environment (for example, All). If you do not, the local environment tree is not copied to the output message.
The information that you insert into DestinationData or Defaults depends on the characteristic of the corresponding node property:
If necessary, configure the sending node to indicate where the destination information is. For example, for the output node MQOutput, set Destination Mode:
To find more information about ESQL procedures that perform typical updates to the local environment, see Populating Destination in the local environment tree. Review the ESQL statements in these procedures to see how to modify the local environment. You can use these procedures unchanged, or modify them for your own requirements.
To find more information about how to extend the contents of this tree for your own purposes, see Using scratchpad areas in the local environment.