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

Components re-
quired

EAI pat-
terns

Problem SOA patterns

Decorator: Callout
to external service
and transformation
engine

Data Model Transform-
ation plus Composition
subcontroller

We need to enhance the messages data by the elements not available on the re-
ceiver.

Content
Enricher

Transformation en-
gine (Java Bean,
POJO)

Content
Filter

Data Model Transform-
ation

We are not suppressing a message. We are filtering out unwanted elements.

The same information we want to receive in different formats from the same ser-
vice. For instance, the same service should provide the same content in JSON
and XML format for SOAP and REST implementations.

Different O\X Map-
pers implemented in
the same service

Content negotiation

Intermediary router
in front of several
transformation ser-
vice agents

This is similar to the previous one; service provides can be requested using the
URL query string (empty body) or by an HTTP payload for SOAP and REST
implementations.

Dual Protocol (Mes-
saging, not Transport);
multichannel endpoint

Normalizer

Message Transformation also covers classic Sort and Validate, and it is realized on XML
Transformation engine(s). A Partial Validation pattern is supported for performance im-
provement as one of the validation forms. Throttler, Load Balancer, and Multicast are the
forms of the traditional intermediate routing. A Generic (and therefore pretty undisrupt-
ive) Service Agent SOA Pattern is the most common way of addressing the mentioned
tasks, but we are not sure that such a vague definition could help anyone. The components
required for each realization are listed in the previous table, but what we really want is an
agnostic way of fulfilling the tasks.