Use the Event coordination property for
controlling how message collections are propagated from the Collector node.
About this task
In addition to the dynamic input
terminals that you can add to the Collector node, there is a
static input terminal called Control. The purpose
of this terminal is to allow an external resource to trigger the output
from the collector node. Details are controlled through the Event
coordination property settings.
Incomplete message collections
that have exceeded the value for the Collection
expiry timeout are immediately propagated to the Expire
terminal, regardless of how you configure the Event coordination property.
To
configure Event coordination:
Procedure
- Open the message flow that contains the Collector node.
- Right-click the Collector node
and select Properties.
- Click the Advanced tab.
- Set the Event coordination property
on the Collector node.
Select from the following options:
- If you select Disabled,
messages to the Control terminal are ignored
and message collections are propagated when they are complete.
- If you select All
complete collections, complete message collections
are held on a queue. When a message is received on the Control terminal,
all message collections on the queue are propagated to the Out terminal.
- If you select First
complete collection, complete message collections are
held on a queue. When a message is received on the Control terminal,
the first message collection on the queue is propagated to the Out terminal.
If the queue is empty when a message arrives on the Control terminal,
the next message collection that is completed is propagated to the Out terminal.
Results
You have completed configuration of the Collector node.
What to do next
Next: if you have configured your Collector node to use control
messages, see Using control messages with the Collector node.