WebSphere Message Broker, Version 8.0.0.7 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Graphical data mapping overview

The graphical data map(.map files) graphically represent your input and output message data. Use drag actions to make connections, select transforms, and build logic to transform your message data without programming.

Input and output objects are defined by reference to message models, which provide a definition of the message structure and type through the following components:
  • Simple elements and attributes, which define the type, range, and default values
  • Complex elements, which build the structure of the message
  • Repeating simple or complex elements
  • Other (embedded) messages

The message assembly contains the message body. The message body must be defined by a user-provided message model if it is to be transformed by using a graphical data map. The message assembly can also contain:

The Mapping node copies headers and folders from input to output, unchanged. To modify any of these headers and folders, add the header or folder to the input and output assembly in the map, and provide transformations. To delete a header, add it to the input Message Assembly, but not the output. To create a header or folder, add it only to the output.

When the transformations in the map are constructed, the values for output message elements can be derived from:
  • Input message elements, through mapping operations that include:
    • Move, Convert, and other built-in transforms in the Graphical Data Mapping editor.
    • XPath 2.0 functions (prefix fn:). All XPath 2.0 functions are supported by the Mapping node. For more information about XPath, see W3C XML Path Language (XPath) 2.0
    • Input from a database by using a database Select transform
    • Schema type casts; for more information, see Mapping casts
  • Additional functions, which allow multiple input values to produce the output value, such as concat and join
  • The result of database Select, Insert, Update, Delete, and Database Routine transforms
  • Constant values, through an assign operation that uses a supplied value
  • Custom functions, user-defined XPath, Java™, or ESQL

Database tables can be set as additional outputs of the graphical data map when using database Insert, Update, Delete or Database Routine transforms.

For information about the supported transform types, see Transform types in the Graphical Data Mapping editor.

The logic to derive values can be simple or complex. In addition to the transformation operations that set an output value, structural transforms are provided to enable conditional statements, loops, and nesting of transform logic into local maps.

You can also create a reusable form of map known as a Submap. Submaps enable you to use a set of mapping functions in multiple maps to transform a common set of elements in the input object to the output object.

Local maps are navigation aids that enable you to view the map elements in a hierarchical way. Unlike submaps, local maps are not separate files and they are not reusable, but they provide a way of breaking up a large map into nested groups of mapping elements and processing the complex elements of the whole message.

You must have message models for any messages that you want to include in a mapping. You can select the message model from your existing message models in your application or library when you create a message map. The mapping facility supports message models that are provided in DFDL and XML schema files or MRM message sets. If your message model includes user-defined data elements, wildcards, or "xsd:any", you can use a cast operation to redefine these data elements to a global type or element from any message schema in your application

You must have a database definition file (.dbm file) in an available Data Design project for each database that you want to access, modify, or call a stored procedure from in a graphical data map transform. You can start the wizard to create a database definition file, when you create a database transform in a graphical data map.

The output message assembly that is set in the output message assembly properties of the map sets the message domain in which the message body is to be built. The following message domains are supported:
  • DFDL
  • XMLNSC
  • SOAP
  • DataObject
  • MRM
  • BLOB

The Mapping node does not support the JSON message domain, because no JSON message modeling is supported.

Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2016Copyright IBM Corporation 1999, 2016.

        
        Last updated:
        
        Last updated: 2016-05-23 14:48:26


Concept topicConcept topic | Version 8.0.0.7 | br28801_