XML maps versus business object maps
You can perform the same data transformations using either XML maps or business object maps. How do you decide which one to use? In general, use an XML map in a Mapping primitive. However, in some specific situations, you need to use a business object map.
Although both types of maps perform transformations, there are functional differences between them. When you use an XML map, standard XSL is generated and used at run time to perform the data transformation. When you use a business object map, you can set the order of the transforms within the business object map. You can use the result of one transform as input to another transform, and also override a transform.
In most situations, you should use
XML maps because they provide industry standard XSLT and XPath transformations.
IBM Integration Designer provides tools to iteratively test XML maps
in the XML map editor. Use business objects maps only if you need
the following specializations:
- Mapping of business graphs. For example, you have a business graph that needs its change summary updated. See Business graphs.
- Custom transformations based on SDO data access.
- Strict ordering of transformation steps, for example:
- The use of temporary variables as collection points for data. In this case, the transform or set of transforms that populates the temporary variable must be executed before the resulting value of the temporary variable value is moved or transformed into the target field.
- A target field needs to be populated first, and the data of that field is then moved to another field.
- Move a complex type and then move a field within the complex type.
- If you need to maintain non-static relationships across the mapping, use a business object map in a business module.
- Static relationships with business object roles.