tMDMBulkLoad Standard properties

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.

Click Sync columns to collect the schema from the previous component.

Built-in: You create the schema and store it locally for this component only. For more information about a component schema in its Basic settings tab, see Basic settings tab.

Repository: You have already created the schema and stored it in the Repository. You can reuse it in various projects and Job designs. For more information about a component schema in its Basic settings tab, see Basic settings tab.

XML field

Select the name of the column in which you want to write the XML data.

URL

Type in the URL required to access 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 Model

Type in the name of the data model against which the data to be written is validated.

Data Container

Type in the name of the data container where you want to write the master data.

Entity

Type in the name of the entity that holds the data record(s) you want to write.

Type

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

Validate

Select this check box to validate the data you want to write onto the Talend MDM Server against validation rules defined for the current data model.

Note that for the PROVISIONING Data Container, validation checks will always be performed on incoming records, regardless of whether or not this check box is selected.

For more information on how to set the validation rules, see Adding validation rules.

Generate ID

Select this check box to generate an ID number for all of the data written.

This check box is not available when the Validate or Fire Create/Update event check box is selected. The auto-generated ID will be used to create the record if this check box is not available and the ID is not provided.

Insert only

Select this check box to skip the step of checking whether the data records to be inserted already exist on the Talend MDM Server, thus achieving a better performance.

However, before using this option, you need to make sure that the data records do not exist in the database.

Commit size

Type in the row count of each batch to be written onto the Talend MDM Server.

Use Transaction

Select this check box then, in the Component List, click an existing connection component which will be used to commit the transaction.

Select this check box to add the actions carried out to a modification report. In the Source Name field displayed, enter the name of the application to be used to carry out the modifications between double quotation marks.

This check box is available only when Master is selected from the Type drop-down list.

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.

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

This component needs always an incoming link to offer XML structured data. If your data offered is not yet in the XML structure, you need use components like tWriteXMLField to transform this data into the XML structure. For further information about tWriteXMLField, see tWriteXMLField.

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.

If you use a Job with the component tMDMBulkLoad to bulk load large volumes of data into MDM, you can tune the bulk load operation by adding a specific JVM argument (for example, bulkload.concurrent.http.requests=25) in the Advanced settings tab of the Job to limit the maximum number of concurrent requests sent to the Talend MDM Server. This avoids consuming all available Tomcat application server connections, which will lead to transaction and deadlock issues.

Connections

Outgoing links (from this component to another):

Row: Main,

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

Incoming links (from one component to this one):

Row: Main

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.