From Traditional Integration to Composition – Enterprise Business Services - Applied SOA Patterns on the Oracle Platform - page 264

To understand the nuances, we are going to link SOA patterns with the underlying EA in-
tegration patterns, and then we are going to see the operations we will have to implement
on OSB to make them generic.

Components re-
quired

EAI pat-
terns

Problem SOA patterns

Intermediate routing

Content-
based rout-
ing

We need to redirect messages to the different service providers depending on the
message content.

Static routing table,
Business Delegate

Intermediate Routing

This is similar to the previous task, but we need to establish a high level of
maintainability and business agility. Therefore, we need to avoid dependency on
the router on all possible (current and future) destinations.

Rule storage, rule
engine, Business
Delegate

Intermediate Routing
plus rule centralization;
Inventory Endpoint;

Dynamic
Router

Transformation en-
gine (Java Bean,
POJO), message in-
termediate storage

Intermediate Routing
plus Composition Con-
troller

We want to process messages with different parts, each of which have different
processing requirements; that is, different service providers.

Splitter

Transformation

Intermediate Routing
plus Composition Con-
troller, and Service In-
stance Routing

After processing the different parts of the message on different endpoints, we
want to assemble the results into one message.

engine (Java Bean,
POJO), message in-
termediate storage

Aggregator

Intermediate Routing
plus state messaging,
messaging metadata,
service agent

Execution plan
(XML), Business
Delegate

We want to process a message sequentially, passing it through a series of pro-
cessing steps.

Routing
slip

Static routing table
with parallel rules This is similar to routers, but we want to dispatch messages to several recipients

n out of total list m .

Recipient
list

Intermediate Routing

Business Delegate

XPath processor
(XMLBean)

Message
filter

We want to suppress the unwanted message. Messaging metadata

That's the ultimate processing block, presenting the RTD processing pattern in a
compound way. We split messages upon receiving, route it to the destinations,
and aggregate the responses. The pattern can include routing slip or recipient list
as well instead of a basic router.

Composition controller
and subcontroller; Ser-
vice Broker plus Inter-
mediate Routing

All components
from the preceding
column

Composed
Message
Processor

Transformation