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

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).

Table of contents

== This article is a STUB, writing in progress ==
Rationale and Context
Solution

Overall solution
Petals Settings and Messages Flows

Configuration for the Petals-SE-Talend component

Configuration for the Petals-BC-SOAP component
Running the use case

Contributors

No contributors found for: authors on selected page(s)

Solution

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, 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.

Wiki

All versions of Petals ESB

Helpful links

Bufferize operations with EIP

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

Rationale and Context

Solution

Overall solution

Petals Settings and Messages Flows

Configuration for the Petals-SE-Talend component

Configuration for the Petals-BC-SOAP component

Running the use case

Labels