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

data($body/*:CTUMessage/*:ProcessHeader/*:ExecutionPlan/
*:taskList/*:task/*:invoke/*:serviceTask/
*:taskSteps[@flow='request']/*: validate /@location)
Enrich
This operation denotes a callout to the external Entity service to extract additional data.
This is also a dynamic invocation of the URI provided in the EP's task parameter.
Implementation of Enrich functionality on OSB
Of course, the proxy for the reference data adapter must be created. We will look at it in
Chapter 6 , Finding the Compromise - the Adapter Framework . Right now, we will just re-
peat what we have said in the functional decomposition table. Practically, there are no
dedicated adapters here, compared to what we see in SOA Suite. So, we will use the JCA
adapter approach, especially for DB, following the sequence described earlier.
We will skip the filtering operation for brevity, but you can easily figure it out by yourself.
Naturally, that will be another dynamic query in the Assign operation, checking the
message body for the presence of XPath, which is provided as a parameter in the EP Fil-
ter task. If the XPath pattern is recognized, the Discard flag is returned and further pro-