July 30, 2023

tMDMConnection – Docs for ESB 7.x


Opens an MDM server connection for convenient reuse in the current Job or

tMDMConnection Standard properties

These properties are used to configure tMDMConnection running in the Standard Job

The Standard
tMDMConnection component belongs to the Talend MDM family.

The component in this framework is available in all Talend

Basic settings

MDM version

By default, Server 6.0 is selected.

Although it is recommended to migrate existing
Jobs for this new version, the Server
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.


Type in the URL required to access the MDM

Username and Password

Type in the user authentication data for the MDM

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

Auto Commit

Select this check box to commit any changes to the database
automatically upon the transaction.

With this check box selected, you cannot use the corresponding
commit component to commit changes to the database; likewise, when using the
corresponding commit component, this check box has to be cleared. By
default, the auto commit function is disabled and changes must be committed
explicitly using the corresponding commit component.

In the MDM context,

  • with this check box cleared, queries sent to the Talend MDM Server will be committed and
    the trigger, if any, will be executed only if the transaction is
    successfully committed.
  • with this check box selected, queries sent to the Talend MDM Server will be committed once
    they are successfully executed, and the trigger, if any, will be executed.
    For this reason, if you need more precision in managing your transactions in
    a Job, it is recommended to use the tMDMCommit component.
Warning: The trigger event will not occur if the Talend MDM Server goes down when the
transaction is committed.

You can consult the mdm.log file to verify the execution results of the trigger. For
more information, see Testing Triggers in the Studio of the
Talend Studio User Guide.

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

This component is to be used along with the
tMDMSP, tMDMViewSearch, tMDMInput, tMDMDelete, tMDMRouteRecord, tMDMOutput,
and tMDMClose

Related scenario

For a related use case, see Deleting master data from an MDM Hub.

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