tMDMTriggerInput Standard properties - 7.3

MDM event processing

Version
7.3
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-21

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

The Standard tMDMTriggerInput component belongs to the Talend MDM family.

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

Basic settings

Property Type

Either Built-in or Repository.

 

Built-in: No property data stored centrally.

tMDMTriggerInput is expected to use this option in order to apply the default read-only schema. MDM_message is the only column of this schema.

 

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

As tMDMTriggerInput provides a fixed read-only schema, you are expected to use the Built-in option.

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. Related Topic: see Talend Studio User Guide.

This is the default option for tMDMTriggerInput. With this option, the read-only schema is used to deal with the XML-format MDM message.

 

Repository: The schema already exists and is stored in the repository. You can reuse it in various projects and jobs. Related Topic: see Talend Studio User Guide.

As tMDMTriggerInput provides a fixed read-only schema, you are expected to use the Built-in option.

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 further information about variables, see Talend Studio User Guide.

Usage

Usage rule

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

To receive the message from MDM, you need to deploy the Job using this component on your MDM server and generate the corresponding trigger and process in MDM to invoke this Job.

For further information about how to deploy a Job onto MDM server and how to generate a trigger or a process, see Talend Studio User Guide.

For further information about how to change a record in MDM, see Talend MDM Web UI User Guide.