Page History

...

• yes
  If a message with a particular correlation ID satisfies the completeness condition, then the cached messages, irrespective of the correlation ID, will be aggregated and grouped based on correlation ID and sent out. Separate output will be sent for each correlation ID.
  
  Example
  Let Ma(Cn) denote message with Correlation ID(C) value n and Message XPath value as a and Aggregator is configured to the Completeness XPath value as X.
  Ma(C1), Mb(C2), Mb(C1), Mc(C2), Mc(C3), MX(C1), MX(C2), MX(C3) are sent to the input port of the Aggregator.

...

Ignore Duplicate Messages

• yes
  Aggregator checks for the duplicate messages and ignores the duplicate messages. 

• no
  Aggregator caches all the messages and doesn't check if the message is duplicate or not.

• no
  Aggregator checks for the duplicate messages and ignores the duplicate messages. 

The procedure to determine the duplicate message is as follows

...

Configure the Aggregator as described in section Configuration and Testing component to send sample input and to check the response respectively.
In the example below, only Input ports XSD is set to chat schema (can use Fetch from Schema for this) in Aggregator Custom Property Sheet and all the remaining properties are left as default.

...

This scenario explains the usage of Dynamic number of messages completeness condition.
Configure the Aggregator as described in section Configuration and Testing and use chat and display component to send sample input and to check the response respectively.

...