Aggregator service

Table of Contents

    Aggregator service Deprecated


    Use the Aggregator producer as of version 3.4.0!!

    The Aggregator service is used for combining several different messages into one message. This service uses a number of pluggable functionalities for this.

    The functionalities determine how the aggregator service decides to make a composite message, how to determine which incoming messages belong together and where incoming messages are temporarily stored.

    In the table below, you will find an explanation about these properties. All attributes with a ‘*’ are mandatory.




    By default, we fill this out with the technical ‘tag’, followed by a serial number. Changing the name is optional.


    Check this box if you want this service to be enabled.

    Aggregator Reference

    Reference to an aggregator bean. The bean must be an extention of the AbstractMyESBAggregator. When not set the default MyESBAggregator is used. This implementation will add all found messages in group as separate messageparts to a ConnectMessage. The part id's will be msgprt[idx]. The type of the part will be according to the message type. Headers of individual messages will be set on ConnectMessagePart. A composition of all headers will be set on the ConnectMessage.

    Discard Flow

    Reference to a flow were an incomplete message is send to after a time-out.


    Name of the MessagePart in a ConnectMessage where the content of the file is being stored.

    Correlation Strategy

    Reference to a correlation strategy bean. The bean must be an extention of the AbstractMyESBCorrelationStrategy. When not set a default MyESBPropertyCorrelationStrategy is used with default correlation-property correlationId

    Correlation Property

    When no correlation-strategy is set a different correlation property than the default correlationId can be set.

    Release Strategy

    Reference to a release strategy bean. The bean must be an extention of the AbstractMyESBReleaseStrategy. When not set a default SequenceSizeReleaseStrategy is used. This implementation consults the sequenceNumber and sequenceSize properties of each arriving message to decide when a message group is complete and ready to be aggregated


    !! Do not touch if you are not experiencing problems. !!

    Time-out in seconds for the aggregator gateway.


    Name of the MessagePart in a ConnectMessage where the content of the file is being stored.

    Header properties

    If you want to use the aggregator the following properties must be available in de header of the message.

    Properties value
    CorrelationId Unique ID that connects the messages / files with each other
    SequenceNumber Place in the sequence
    SequenceSize Total sequence size


    Copyright © 2019 ConnectPlaza.   For pricing, account management and more go to https://www.connectplaza.com

    About Connectplaza

    Si components version:   

    Lorem ipsum delore set

    Lorem ipsum delore set

    Window size is not optimal. Please enlarge for optimal experience

    No connection

    No response from the server. This window will automaticly disappear by an valid connection