SOA Magazine IV 01.2015

Native xEngine used for supported documents
Document Callouts for custom documents processing
This functionality offers the possibility to implement custom classes to deal with document types that
are not covered out-of-the-box. In this implementation, a custom parser was implemented to generate
XSD and JAVA classes from standard language Augmented Backus–Naur Form i (ABNF) that can be
associated as B2B Document Callout to dynamically execute parsing, construction and validation of
documents. Please, bear in mind that a good architecture of this callouts is paramount to guarantee full
performance answer when processing such documents.
SCA Core processing
The message is delivered via B2BAdapter to a composite and so entering the core domain of the
solution. It is then in this domain that the message is handled and all the necessary core functionalities
are provided:
Mapping from message type structure to canonical structure. Normalizing the message allows to
reuse functionalities that become agnostic to every different message type to be processed. Those
mappings are implemented using XSLTs that are read dynamically from the MDS
Business rules are verified and deliver an outcome list of functionalities that affects the message
exchange processing
The message is orchestrated to the different core functionalities guided by rules
Communication with the B2B repository for enrichment and operations using the API provided
The message is mapped from canonical structure to the message type structure and delivered via
B2BAdapter to B2B
Outbound
Similar to the inbound. the message and envelope are constructed using the xEngine or Document
callout and delivered to the final recipient using the configured trading partner channel.
BAM Integration
The integration between the components and BAM is established on the B2B side by native integration
based in Advance Queue and from SOA SCA via sensors.
Exception Handling
The exception handling implemented transversally allows end-to-end coverage of exceptions. B2B
exceptions are communicated natively to a SCA via B2B exception handling queue. EDN infrastructure
together with B2B Exception handling and SOA Fault Handling Framework is used for exception handling
purpose guaranteeing 100% message reliability on the platform.
What about performance
Copyright © 2015 | All Rights Reserved SOA Magazine IV 18