Bufferize operations with EIP

compared with
Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (5)

View Page History
{section}
{column}

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}
*Deployed configurations:*
# One Petals ESB node has:
## [SE-RMI|petalsesb:Petals-SE-RMI] for sending test messages via [webconsole|webconsole:User Guide]
## [SE-EIP|petalsesb:Petals-SE-EIP] for the buffering chain + 1
## [SE-JSR181|petalsesb:Petals-SE-Jsr181 1.1] which contains the operation "AddIntegers" on the sample service "MathOperations"
# Then we will configure and deploy
## One Service Assembly (SA) containing two EIP Service Unit (SU) : Aggregator and Splitter patterns