July 30, 2023

tMDMTriggerInput – Docs for ESB 7.x


Reads the XML message (Document type) sent by MDM and passes
the information to the component that follows.

Every time when you save a change in your MDM, the corresponding record is
generated in XML format. At runtime, this component reads this record and sends the relative
information to the following component. With tMDMTriggerInput, you do not
need to configure your Job any more in order to communicate the data changes from MDM to your


This component works alongside the new trigger service and process plugin
in MDM version 5.0 and higher. The MDM Jobs, triggers and processes developed in
previous MDM versions remain supported. However, we recommend using this component
when designing new MDM Jobs.

tMDMTriggerInput Standard properties

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

Basic settings

Property Type

Either Built-in or Repository.


Built-in: No property data stored

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

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
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


Built-in: The schema will be
created and stored for this component only. Related Topic: see

Talend Studio User

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 +
to access the variable list and choose the variable to use from it.

For further information about variables, see
Talend Studio

User Guide.


Usage rule

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

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

Exchanging the event information about an MDM record

This scenario applies only to Talend MDM Platform and Talend Data Fabric.

In this scenario, a four-component Job is used to exchange the event
information about a product record. Using an MDM connection established from the
Repository, this Job is called by an
eligible trigger once you update an existing product record.

To replicate this scenario, accomplish the following tasks

  1. Create an MDM connection of the Receive type in the Repository of the Studio. This connection is to the
    MDM hub holding the record you want to update.

  2. Create the Job to receive and send the MDM update

  3. Generate the trigger to invoke this Job created.

  4. Update a product record.

To create the MDM records, data model and data container used in this
scenario, you can execute the Jobs in the MDM demo project in Talend Studio and then update the MDM server to deploy the objects thus
created for them to be taken into account at runtime. You will use this server
throughout this scenario.

You can search for further information about MDM event
management, how to import a demo project and how to deploy objects to the MDM
server on Talend Help Center (https://help.talend.com).

Creating an MDM connection to retrieve entities

Make sure the MDM server with which you need to communicate the update message is up
and running.

  1. In the Integration perspective of Talend Studio, expand
    the Metadata node in the Repository.
  2. Right-click the Talend
    item and select Create MDM


  3. Enter the Name you want
    to use for this connection and if required, added the Purpose and the Description in the corresponding fields.

    For example, name this connection Receive.
  4. In the Next step, enter
    the credentials for connecting to the MDM server which holds the record to be

    Once you click the Check button and the
    connection is shown successful, the Next
    button becomes clickable.

  5. In the Next step, select
    the Data model and the Data Container used by the record to be updated.

    In this scenario, the model and the container are both
  6. Click Finish to validate
    the creation.

    The connection created is displayed under the Metadata node in the Repository.

Retrieving entities using the MDM connection

  1. Right-click the connection created and from the contextual
    menu, select Retrieve Entity.
  2. Select Receive MDM in
    the dialog box and click Next to


  3. Select the entity to be retrieved, and click

    In this scenario, select Product, and the
    Name field is populated automatically.

  4. Drop the elements you need to retrieve from the Source Schema area to the Target Schema area.

    In this scenario, the Features element is the field to
    be looped and the Id, Name and
    Description elements are the fields to be

  5. Keep the default schema description and click Finish to finalize retrieving the schema of the
    Product entity.

    You can see more information about the data
    container and the data model used by Talend MDM on
    Talend Help Center (https://help.talend.com).

Creating a Job and linking the components for communicating the MDM message

  1. Create a Job named update_product.
  2. Drop tMDMTriggerInput, tXMLMap,
    tMDMTriggerOutput and tLogRow
    from Palette onto the workspace.
  3. Right-click tMDMTriggerInput and from the contextual
    menu, select the Row > Main link to connect it to tXMLMap.
  4. Do the same to connect tXMLMap to
    tMDMTriggerOutput, and name the connection output.
  5. Double-click tMDMTriggerOutput to open its
    Component view.
  6. Click the […] button next to Edit
    to open the editor.
  7. Select the single pre-defined column of
    tMDMTriggerOutput, and then click tMDMTriggerInput_6.png to
    reproduce this column on the input side (left).
  8. Connect tMDMTriggerOutput to
    tLogRow using the Row > Main connection.


Configuring the transformation of the MDM message in the Job

  1. Double-click tXMLMap to
    open its editor.
  2. In the table representing the input flow (upper left of the
    editor), right-click the column name MDM_Message on the top of the XML tree and select Import From Repository.

    The Metadata wizard is displayed.
  3. Select the entity schema ProductReceive
    retrieved earlier using the Receive MDM
    model, then click OK.
  4. Click OK in the dialog
    box that prompts you to add the schema of the Update Report to the input XML

    This builds a complete input document for an MDM event. In the input XML tree,
    the Features element is set as the loop element

  5. In the table representing the output flow (upper right of the
    editor), develop the output XML tree as presented in the figure below.

    This tree is constructed depending on the required static model of the MDM
    output report.
    The XML construct required to return the validation-success message is
    , and the XML
    construct required to return the validation-failure message is

  6. Map the OperationType element on the input side to the
    message element on the output side.

    This will output the information about the type of the event occurring on the
    MDM record.
  7. In the Expression
    column, enter "info" in the row corresponding
    to @type.
  8. Click the pincer icon to display the output settings panel, and
    then set the All in one option to
  9. Click OK to close the
    editor and validate these changes.
  10. Double click tLogRow to
    open its Component view, then, click
    Sync columns.

Deploying the Job onto the MDM server

  1. Switch to the MDM perspective, and expand the Job
    node in the MDM Repository tree
  2. Right-click the Job update_product
    created previously in this scenario, and select Deploy To… from the contextual menu.

    The deployment wizard is displayed.
  3. From the server list, select the MDM server you are using, and
    then click OK.
  4. In the Deploy to Talend
    window that pops up, keep the default settings: Export type is Hosted
    and Context scripts
    is Default.

    You can see more information about these settings on
    Talend Help Center (https://help.talend.com).

  5. Click Finish to validate
    these settings and start the deployment.

    When the deployment is done, a message box pops up to indicate that the
    deployment is successful.
  6. Click OK to close this
    message box.

    A window pops up to indicate that the Job
    update_product is deployed successfully.
  7. Click OK to finalize the

Generating the trigger used to call the Job

  1. Right-click the Job update_product and
    select Generate Talend Job Caller Trigger
    from the contextual menu.
  2. In the pop-up window, keep the default settings for this
    scenario: Integrated and Embedded.


  3. Click Generate to start
    the generation.

    Once done, a trigger named CallJob_update_product is
    displayed under the Trigger node in MDM
  4. Right-click this trigger, and then select Deploy To… from the contextual menu to deploy
    it onto the MDM server.
  5. In the pop-up wizard, select the server you are using, and
    click OK.
  6. Click OK to finalize the

Updating a product record

  1. Log in to the web user interface.
  2. In the Actions panel on the
    right side, select Product for both the Data Container and the Data
  3. In the Master Data Browser
    page, launch the search in the Product entity to list all the
    available product records.
  4. Select the product record you need to update from the list, for
    example, Talend Trucker Hat.

    The details of this record are displayed in the Product
    tab view.
  5. Update one of its attributes.

    In this example, update the price to 11.00 and then
    click Save.
    The message about the operation type of this event has been sent to the MDM
    server and this message is displayed on the window of this MDM server.

Document get from Talend https://help.talend.com
Thank you for watching.
Notify of
Inline Feedbacks
View all comments
Would love your thoughts, please comment.x