SOA Magazine IV 01.2015

Routing and document handling business rules
Service orchestration
Message enrichment
Message canonicalization/normalization
Message duplication
Mapping and transformations
Document conversion
Message splitting
Message rejection
Message deferring
Message acknowledge
Legacy system integration
Exception handling
Oracle B2B and SOA Suite, together provide a natural and integrated architecture that enables a unified
platform with end-to-end instance capabilities, empowering standardization, governance, and security.
Solution architecture
B2B as a hub assumes that it is acting both as inbound and outbound gateway sharing the same
configuration for both directions. Trading partners are connected via inbound listening channels and
trading partner channels for delivery. In the message exchange process, B2B is responsible for
identifying both the sender and recipient(s) of the message, identifying the message type and verifying if
the sender is active to send such type of message, if the recipient is able to receive it and in which
format it is able to. Message validation and parsing (from raw to XML) for inbound messages and
message construction (from XML to raw) for outbound are also performed on B2B domain.
The host trading partner will be the virtual receiver of all incoming documents and the virtual sender of
all outgoing documents eliminating any point to point relation between trading partners and
documents. All of this consolidates the possibility of document normalization, allowing the definition of
message classes. This facilitates the usage of common objects between message types and formats
Copyright © 2015 | All Rights Reserved SOA Magazine IV 16