Building the Core – Enterprise Business Flows - Applied SOA Patterns on the Oracle Platform - page 209

you can see in the following screenshot, we do not use this operation in an out-
bound call. Why is that? It is because of the following reasons:
◦ It is our outbound flow. We believe that here we can trust ourselves. Still,
we have the possibility to employ southbound ABCSes to perform the
validation.
◦ We have already decided that the validation would be part of the execu-
tion plan performed on SB. It gives us a lot of flexibility, and we can
maintain this operation in a really agnostic way.
Configuring Mediator's endpoint property
You have to consider this option wisely. With an agnostic payload, we can generally valid-
ate MessageHeader , ProcessHeader (with EP), and MessageTrackingData .
Logically, it should be done on OSB and/or the adapter layer. Although the Schematrons
functionality is really quick, we can achieve the same kind of performance by other
means. We suggest that you perform JIT verifications yourself. For this use case, we will
not perform it on Mediator.
Inbound flows are easier (again, for this use case only), but practically, all of the outbound
functionalities are applicable for inbound flows as well. You can also perform partial/com-
plete validation (we don't). The transformation of SCA's responses is also inevitable, as