Read the concept topic about message flow nodes.
You can include a Compute node in your message flow, and configure it to create a destination list within the LocalEnvironment subtree. You can then use the destination list in the following nodes:
Refer to the Airline sample to see how this technique is used.
For more information about destination list contents, and example procedures for setting values for each of these scenarios, see Accessing the LocalEnvironment tree.
You might find it useful to create the contents of the destination list from an external database accessed by the Compute node. You can then update the destinations without having to update and redeploy the message flow.
The use of the destination list to define which applications receive the output messages is in contrast to the publish/subscribe application model, in which the recipients of the publications are those subscribers currently registered with the broker. The processing completed by the message flow does not have any effect on the current list of subscribers.
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ac00380_ |