tMDMRouteRecord Standard properties - Cloud - 8.0

MDM event processing

Version
Cloud
8.0
Language
English
Product
Talend Data Fabric
Talend MDM Platform
Module
Talend MDM Server
Talend Studio
Content
Data Governance > Third-party systems > MDM components > MDM event processing components
Data Quality and Preparation > Third-party systems > MDM components > MDM event processing components
Design and Development > Third-party systems > MDM components > MDM event processing components
Last publication date
2024-02-20

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

The Standard tMDMRouteRecord component belongs to the Talend MDM family.

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

Basic Settings

Use an existing connection

Select this check box if you want to use a configured tMDMConnection component.

MDM version

By default, Server 6.0 is selected. Although it is recommended to migrate existing Jobs for this new version, the Server 5.6 option is available to ease the process of the migration of your Jobs so as to keep them working without modification with a 6.0 server. To do so, an option on the server must be enabled to accept and translate requests from such Jobs.

URL Type in the URL of the Talend MDM Server.

Username and Password

Type in the user authentication data for the Talend MDM Server.

To enter the password, click the [...] button next to the password field, enter the password in double quotes in the pop-up dialog box, and click OK to save the settings.

Data Container

Type in the name of the data container that holds the record you want Event Manager to read.

Type

Select Master or Staging to specify the database on which the action should be performed.

Entity Name

Type in the name of the business entity that holds the record you want Event Manager to read.

IDs

Specify the primary key(s) of the record(s) you want Event Manager to read.

The key of the event record is different depending on the working mode of your MDM server:

  • for the standalone mode, the key is composed of the Source value and the TimeInMillis value of the record, concatenated using a period, for example, genericUI.1552964721309.
  • for the cluster mode, the key is the UUID value of the record, for example, 814da0a4-1c55-453d-bfab-312c2d8e2165.

Advanced settings

tStatCatcher Statistics

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

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

Usage rule

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

You can increase the timeout values for a Job using this component to help process a large number of data records. For more information, see advanced execution settings for JVM parameters in the article Timeout values for a Job using MDM components.

Connections

Outgoing links (from this component to another):

Row: Iterate

Trigger: Run if; On Component Ok; On Component Error, On Subjob Ok, On Subjob Error.

Incoming links (from one component to this one):

Row: Iterate;

Trigger: Run if, On Component Ok, On Component Error, On Subjob Ok, On Subjob Error

For further information regarding connections, see Using connections in a Job.