SOA Magazine IV 01.2015

implemented in a canonical model eliminating point-to-point transformations and allowing putting in
place a mechanism of global mappings from the message format to canonical structure and from
canonical structure to the message format.
A native integration between Oracle B2B and Oracle SOA SCA allows covering all the necessary
requirements. In the picture bellow it’s shown a correspondence between components domains and
functionalities succeeding the message processing timeline.
Apart of the functionalities mapped to B2B and SOA SCA, its integration across the SOA platform allows
to naturally implementing an end to end process tracking and exception handling having all exceptions
being delivered to SCA to be handled in properly. In this case in particular, the solution is covering
acknowledge to the sender that the message failed and the reasons behind the exception. This is an
extremely valuable solution feature, since most of the exceptions are typically generated from invalid
documents. This allows the sender to correct and fix the messages interactively reducing the time
needed to implement such corrections.
This is also helps the customers to fit to the market standards reducing custom made message
definitions.
Inbound
Transport callouts are assigned to Inbound/Outbound B2B channels responsible for parsing the
envelope to a B2B Internal Properties native structure. Then, two possible paths can be followed for
document parsing:
Copyright © 2015 | All Rights Reserved SOA Magazine IV 17