tXMLMap properties - 6.3

Talend Open Studio for Big Data Components Reference Guide

Talend Open Studio for Big Data
Data Governance
Data Quality and Preparation
Design and Development
Talend Studio

Component family



Basic settings

Map Editor

It allows you to define the tXMLMap routing and transformation properties.

Advanced settings

tStatCatcher Statistics

Select this check box to gather the Job processing metadata at the Job level as well as at each component level.

Global Variables

ERROR_MESSAGE: the error message generated by the component when an error occurs. This is an After variable and it returns a string. This variable functions only if the Die on error check box is cleared, if the component has this check box.

A Flow variable functions during the execution of a component while an After variable functions after the execution of the component.

To fill up a field or expression with a variable, press Ctrl + Space to access the variable list and choose the variable to use from it.

For further information about variables, see Talend Studio User Guide.


Possible uses are from a simple reorganization of fields to the most complex jobs of data multiplexing or demultiplexing transformation, concatenation, inversion, filtering and so on.

When needs be, you can define sophisticated outputting strategy for the output XML flows using group element, aggregate element, empty element and many other features such as All in one. For further information about these features, see Talend Studio User Guide.

It is used as an intermediate component and fits perfectly the process requiring many XML data sources, such as, the ESB request-response processes.


If you are using a subscription-based version of the Studio, the activity of this component can be logged using the log4j feature. For more information on this feature, see Talend Studio User Guide.

For more information on the log4j logging levels, see the Apache documentation at http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/Level.html.


The limitations to be kept in mind are:

- The use of this component supposes minimum Java and XML knowledge in order to fully exploit its functionalities.

- This component is a junction step, and for this reason it cannot be a start nor an end component in the Job.

- At least one loop element is required for each XML data flow involved.

The following sections present several generic use cases about how to use the tXMLMap component, while if you need some specific examples using this component along with the ESB components to build data services, see the scenarios for the ESB components:

If you need further information about the principles of mapping multiple input and output flows, see Talend Studio User Guide.