h1. == This article is a STUB, writing in progress ==

h1. Rationale and Context

An enterprise wants to delay some operations off-peak hours. Instead of calling operations directly, we will bufferize them, and send them later, when a trigger signal comes (might be automated, or activated by user).
{column}
{hide-if:display=pdf}
{column:width=350px}
*Table of contents*
{toc}
*Contributors*
{contributors:order=name\|mode=list}
{column}
{hide-if}
{section}

h1. Solution


h2. Overall solution

In this case, let us call call a simple operation, "AddIntegers" on a service "MathOperations". This operation takes <integer1> and <integer2> parameters, both with an integer value,&nbsp; and returns the sum of the two integers.

We will first use the EIP pattern "Aggregator", chained with the EIP "Splitter". Aggregator bufferize messages, until receiving a trigger message. Then he sends one single message aggregating all bufferized messages, to the next service. Then we will split back all messages, to be readable by "AddIntegers" operation, using the EIP pattern Splitter.


h2. Petals Settings and Messages Flows
{gliffy:name=EIP Splitter Aggregator}

&nbsp;

h1. Configuration for the Petals-SE-Talend component

hjh


h2.


h1. Configuration for the Petals-BC-SOAP component


h1. Running the use case

To test this use case, you need to deploy the Petals-SE-EIP