Triggering maps to run by multiple events

When you have a message flow that contains a TX Map node that is preceded by a Collector node, multiple events can trigger the IBM Transformation Extender map to run.

The Collector node in a message flow groups together multiple messages that arrive at its input terminals, and runs the rest of the flow when triggering criteria that you have defined are met. It performs event triggering functions similar to the IBM Transformation Extender with Launcher product.

The node propagates all the messages it receives in a message collection, which is a type of broker message tree. Each message is contained within a folder in the message collection. The folder names are taken from the names of the input terminals of the Collector node. When you use the Collector node and TX Map nodes together in your message flow, you must add Collector input terminals with names that match the card names, not the card numbers, of the map's input cards.

If the IBM Transformation Extender map has an input card with a card name that matches the name of a folder in the message collection, the Collector node delivers the message in that folder to that input card. After the Collector node delivers the messages within all of the folders in the collection to the map's input cards with matching names, the TX Map node runs the map.

If the IBM Transformation Extender map has other input cards that do not match any folder names in the message collection, these input cards do not receive messages, and the map pulls data from each of these card's adapter.