Download to read offline
Uploaded byAnkush Sharma
Mule Custom Aggregator
An aggregator joins messages from multiple connectors into a single flow by correlating them. A custom aggregator is implemented as a user-written class that aggregates messages by implementing the MessageProcessor interface. Configuring a custom aggregator involves specifying its class name, timeout, message info mapping, and optional properties. The message info mapping tab defines expressions to map message attributes to the message ID and correlation ID.
More Related Content
More from Ankush Sharma
Mule Custom Aggregator
- 1. MULE CUSTOM AGGREGATOR BY –ANKUSH SHARMA
- 2. WHAT IS ANAGGREGATOR? • A message splitter can is used to break down an outgoing message into parts and dispatch those parts over different endpoints configured on the router. Then this is the task of aggregator to do just opposite to splitter. An aggregator gets input from various connectors and join them in one flow. The actual endpoint used for each object in the list is determined by a filter configured on the endpoint itself. If the endpoint’s filter accepts the object, the endpoint will be used to route the object.
- 3. WHAT IS CUSTOMAGGREGATOR? • A Custom Aggregator is an instance of a user-written class that aggregates messages. This class must implement the interface MessageProcessor. Often, it will be useful for it to subclass AbstractAggregator, which provides the skeleton of a thread-safe aggregator implementation, requiring only specific correlation logic. As with most custom objects in Mule, it can be configured either with a fully specified class name or as a reference to a Spring bean. It can also be configured with the same timeout and failOnTimeout attributes described under Collection Aggregator.
- 4. MULE CUSTOM AGGREGATOR– CONFIGURATION WIZARD (GENERAL TAB) (CONT.)
- 5. MULE CUSTOM AGGREGATOR– CONFIGURATION WIZARD (GENERAL TAB) • Following are the options on general tab – • Display Name – The name of the component to be displayed in Mule flow. • Class – Fully qualified class name of the custom correlation aggregate router to be used. • Timeout – The timeout time in milliseconds. • Message Info Mapping – Maps the current message attributes with the known message attributes. • Store Prefix – Defines the prefix of the object store names.
- 6. MULE CUSTOM AGGREGATOR– CONFIGURATION WIZARD (ADVANCED TAB) (CONT.)
- 7. MULE CUSTOM AGGREGATOR– CONFIGURATION WIZARD (ADVANCED TAB) • This tab is used to add business events tracking for the whole process of aggregator.
- 8. MULE CUSTOM AGGREGATOR– CONFIGURATION WIZARD (PROPERTIES TAB) (CONT.)
- 9. MULE CUSTOM AGGREGATOR– CONFIGURATION WIZARD (PROPERTIES TAB) • This tab is used to add some spring properties that would be used in the process of aggregator.
- 10. MULE CUSTOM AGGREGATOR–MESSAGE INFO MAPPING CONFIGURATION WIZARD (GENERAL TAB) (CONT.)
- 11. MULE CUSTOM AGGREGATOR–MESSAGE INFO MAPPING CONFIGURATION WIZARD (GENERAL TAB) (CONT.) • Following are the options on general tab – • Message ID Expression – Expression for mapping message attributes to messageIdExpression. • Correlation ID Expression – Expression for mapping message attributes to correlationIdExpression.
- 12. MULE CUSTOM AGGREGATOR– CONFIGURATION WIZARD (NOTES AND META-DATA TABS) • Notes Tab, is used to add special notes for this filter component. • META-DATA Tab, is used to add meta-data for this filter component.
- 13.