Skip to main content Skip to complementary content

tXMLMap Standard properties

These properties are used to configure tXMLMap running in the Standard Job framework.

The Standard tXMLMap component belongs to the Processing and the XML families.

The component in this framework is available in all Talend products.

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.

Keep order for document

Select this check box to output XML elements strictly in the order specified in the output XML schema.

Global Variables

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 more information about variables, see Using contexts and variables.


Usage rule

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 Defining the output mode.

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


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:

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!