tMDMReceive Standard properties

Property Type

Either Built in or Repository.

Built-in: No property data stored centrally.

Repository: Select the repository file where properties are stored. The fields that follow are completed automatically using the fetched data.

Schema and Edit Schema

A schema is a row description, it defines the number of fields that will be processed and passed on to the next component. The schema is either built-in or remote in the Repository.

Click Edit schema to make changes to the schema. If the current schema is of the Repository type, three options are available:

• View schema: choose this option to view the schema only.

• Change to built-in property: choose this option to change the schema to Built-in for local changes.

• Update repository connection: choose this option to change the schema stored in the repository and decide whether to propagate the changes to all the Jobs upon completion.

  If you just want to propagate the changes to the current Job, you can select No upon completion and choose this schema metadata again in the Repository Content window.

Built-in: The schema will be created and stored for this component only. For more information about a component schema in its Basic settings tab, see Basic settings tab.

Repository: The schema already exists and is stored in the repository. You can reuse it in various projects and Jobs. For more information about a component schema in its Basic settings tab, see Basic settings tab.

XML Record

Enter the context parameter allowing to retrieve the last changes made to the Talend MDM Server. For more information about creating and using a context parameter, see Using contexts and variables.

XPath Prefix

If required, select from the list the looping xpath expression which is a concatenation of the prefix + looping xpath.

/item: select this xpath prefix when the component receives the record from a process because processes encapsulate the record within an item element only.

/exchange/item: select this xpath prefix when the component receives the record from a trigger because triggers encapsulate the record within an item element which is within an exchange element.

Loop XPath query

Set the XML structure node on which the loop is based.

Mapping

Column: reflects the schema as defined in the Edit schema editor.

XPath query: Type in the name of the fields to extract from the input XML structure.

Get Nodes: Select this check box to retrieve the XML node together with the data.

Limit

Maximum number of rows to be processed. If Limit = 0, no row is read or processed.

Die on error

This check box is selected by default. Clear the check box to skip the row on error and complete the process for error-free rows. If needed, you can retrieve the rows on error via a Row > Reject link.

tStatCatcher Statistics

Select this check box to gather the 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.

NB_LINE: the number of rows processed. This is an After variable and it returns an integer.

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

Use this component as a start component. It needs an output flow.