View Source

{section}
{column}




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

We want to call the operation "AddIntegers" on a service "MathOperations", using a buffer. This operation needs two integer parameters, <integer1> and <integer2>, and&nbsp; returns their sum.

We will send messages to an EIP pattern "Aggregator". It will bufferize all messages, until he gets a trigger message. Then it sends the whole buffer, aggregated in one single message, to the next service, EIP Splitter. It will split back the aggregated message into several messages, and send them to the next step, "AddIntegers" operation, to process all messages.



h2. Petals Settings and Messages Flows

{gliffy:name=Petals RMI-EIP-JSR181\|align=left\|size=L\|version=2}

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