This section explains, through an example scenario, how the Canonical Data Model EIP can be implemented using WSO2 ESB. The following topics are covered:
| Table of Contents |
|---|
Introduction to Canonical Data Model EIP
The Canonical Data Model EIP minimizes dependencies when integrating applications that use different data formats. It is independent from any specific application, and requires each application to produce and consume messages in this common format. For more information, refer to http://www.eaipatterns.com/CanonicalDataModel.html.
...
Figure 1: Canonical Data Model EIP
How WSO2 ESB Implements the EIP
...
The Canonical Data Model EIP , messaging systems have to minimize the minimizes dependencies between applications which uses that use different data formats , thereby ensuring loose in messaging systems. That ensures loose-coupling between applications. The
WSO2 ESB supports a number of different data formats including POX, JSON and SOAP. Translating to a common data model (SOAP in WSO2 ESB) and vice versa back to the original format is done through using the underlying implementations of message builders and message formatters. If the receiving messages are not in the form format the back-end service requires, users can use a Translator mediator or create a new message in SOAP format using the . The Payload Factory mediator can be used for that.
Sample Also see Normalizer EIPNormalizer for sample scenarios and explanations are included in the Normalizer EIP section.
| Excerpt | ||
|---|---|---|
| ||
Canonical Data Model, Integration Patterns with WSO2 ESB |