You can use a graphical data map to graphically transform, route, or update an external system. For best performance and capability, you must design it to include the most appropriate transforms.
Consider the following guidance to design a graphical data map:
The function of a graphical data map is driven by the data models that define the input and the output message structures of a map. At run time, the Graphical Data Mapping engine must account for all possible states of the data when executing the transformations you have defined in the map against the data models. You may have control or not over the data models in your solution. If you can influence the data model, these are some of the key points to consider:
When you define a logical model, you can configure the cardinality of each element by setting the minoccurs and the maxoccurs properties.
Avoid, whenever possible, configuring maximum flexibility unless actually required. Only set minoccurs to 0, when an element needs to be optional. Only set maxoccurs above 1 if the element will actually repeat.
For more information, see Creating a submap.
When the transformation of an element from input to output becomes more than just a simple Move, or type conversion (xs:type), you can call on the full set of standard XPath 2.0 operators and functions to manipulate the data as required.
The Graphical Data Map editor offers the XPath functions as transform types in the pick list as well as in the content assist, "Ctrl-space" when editing expressions and conditions.
For more information, see Defining an XPath conditional expression for a transform.
At run time, if the condition evaluates to tue, you obtain similar performance results whether all the transforms are in the main map or grouped into nested maps that are associated with structural transforms.
For more information, see Using nested maps.
From a performance point of view, it is recommended that you use XPath transforms or the Custom XPath transform as your first choice, then Custom Java.
Copyright IBM Corporation 2012.
Task topic |