Anypoint DataMapper User Guide and Reference
Anypoint™ DataMapper, or DataMapper for short, is a Mule transformer that delivers simple, yet powerful, visual design of complex data transformations for use in Mule flows, including:
- Extraction and loading of flat and structured data formats
- Filtering, extraction and transformation of input data using XPath and powerful scripting
- Augmenting data with input parameters and lookups from other data sources
- Live design-time previews of transformation results
- High-performance, scalable data mapping operations
Inputs and outputs can be “flat” (that is, row-structured) data like CSV files or Excel spreadsheet data, or structured data in the formats supported throughout Mule: XML, JSON, key/value Maps and trees of Plain Old Java Objects (POJOs).
In general, using the more basic Mule transformers to recreate the functionality of a single DataMapper may require a complex flow of format converters for input data, splitters, filters, For Each scopes, expressions, other transformers, aggregators, and yet more format converters for the output. A DataMapper-based implementation is faster to implement and e asier to maintain than the alternatives.
Graphical design of the complex transformations supported by DataMapper makes it simple to apply all of its capabilities with little coding beyond basic expressions and function calls to transform data.
|Full DataMapper functionality is exclusive to the Mule ESB Enterprise Edition (EE), it won't work if you're deploying your projects to Mule ESB Community Edition (CE).|
The following examples show the use of DataMapper:
|Web Service Consumer|
Turns JSON requests to XML and back. Also turns a flow variable into an outbound property.
|Salesforce to Database||Renames fields in a Salesforce record selector. See the "Batch Step 1" section.|
|Service Orchestration and Choice Routing||Transforms a message to communicate with the Samsung web service API in the "samsungOrder Flow" section.|
|XML-Only SOAP Web Service||Maps data from responses to a healthcare database for viewing by a patient, and formats questions from patients for access to a patient information web service.|
|Legacy Modernization||Maps data from a shipping order POJO into a CSV file in the "How it Works" section.|
- DataMapper Concepts
- DataMapper Visual Reference
- Defining DataMapper Input and Output Metadata
- Building a Mapping Flow in the Graphical Mapping Editor
- Updating Metadata in an Existing Mapping
- Mapping Elements Inside Lists
- Previewing DataMapper Results on Sample Data
- DataMapper Examples
- DataMapper Supplemental Topics