You can include a Compute node in your message flow, and configure it to create a DestinationList within the LocalEnvironment subtree. You can then use the DestinationList in the following nodes:
The Order Processing sample uses this technique and can provide useful guidance for you.
Refer to the Airline sample to see how this technique is used.
You might find it useful to create the contents of the DestinationList 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_ |