# tMDMInput Standard properties

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

The Standard tMDMInput 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<br>data stored centrally |
|  | Repository: Select the<br>repository file where properties are stored. The fields that follow are<br>completed automatically using the fetched data |
| Schema and Edit Schema | A schema is a row description, it defines the<br>number of fields that will be processed and passed on to the next component.<br>The schema is either built-in or remote in the Repository.<br><br>Click Edit<br>schema to make changes to the schema. If the current schema is of the Repository type, three options are available:<br><br><ul> <li> <p> <span>View schema</span>: choose this                option to view the schema only.</p> </li> <li> <p> <span>Change to built-in property</span>:                choose this option to change the schema to <span>Built-in</span> for local changes.</p> </li> <li> <p> <span>Update repository connection</span>:                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 <span>No</span> upon completion and choose this schema metadata                again in the <span>Repository Content</span>                window.</p> </li> </ul> |
|  | Built-in: The schema<br>will be created and stored for this component only. Related Topic: see *Talend Studio*<br>*User Guide*. |
|  | Repository: The schema<br>already exists and is stored in the repository. You can reuse it in various<br>projects and jobs. Related Topic: see *Talend Studio*<br>*User Guide*. |
| Use an existing connection | Select this check box if you want to use a configured<br>tMDMConnection<br>component. |
| MDM version | By default, Server 6.0 is selected. Although it is<br>recommended to migrate existing jobs for this new version, the Server 5.6 option is available<br>to ease the process of the migration of your Jobs so as to keep them working<br>without modification with a 6.0 server. To do so, an option on the server must<br>be enabled to accept and translate requests from such Jobs. |
| URL | Type in the URL to access the MDM server. |
| Username and Password | Type in user authentication data for the MDM<br>server.<br><br>To enter the password, click the [...] button next to the<br>password field, and then in the pop-up dialog box enter the password between double quotes<br>and click OK to save the settings. |
| Entity | Type in the name of the business entity that<br>holds the data you want to read. |
| Data Container | Type in the name of the data container that<br>holds the data you want to read. |
| Type | Select Master or Staging to specify the database on which the<br>action should be performed. |
| Use multiple conditions | Select this check box to filter the data using<br>certain conditions.<br><br><ul> <li> <p> <span>Xpath</span>: Enter between quotes the path and the XML node to which you want to          apply the condition.</p> </li> <li> <p> <span>Function</span>: Select an operator to be used from the list. The following          operators are available:</p> <ul> <li> <kbd>Contains</kbd>:            Returns a result which contains the word or words entered. Note that full text search            does not support special characters, for example, @, #, $.</li> <li> <kbd>Contains the              sentence</kbd>: Returns one or more results which contain the sentence            entered.</li> <li> <kbd>Joins With</kbd>:            This operator is reserved for future use.</li> <li> <kbd>Starts With</kbd>:            Returns a result which begins with the string entered.</li> <li> <kbd>Equal</kbd>:            Returns a result which matches the value entered.</li> <li> <kbd>Not Equal</kbd>:            Returns a result of any value other than the null value and the value entered.</li> <li> <kbd>is greater              than</kbd>: Returns a result which is greater than the numerical value entered.            Applies to number fields only.</li> <li> <kbd>is greater or              equal</kbd>: Returns a result which is greater than or equal to the numerical            value entered. Applies to number fields only.</li> <li> <kbd>is lower            than</kbd>: Returns a result which is less than the numerical value entered.            Applies to number fields only.</li> <li> <kbd>is lower or              equal</kbd>: Returns a result which is less than or equal to the numerical value            entered. Applies to number fields only.</li> <li> <kbd>whole content              contains</kbd>: Performs a plain text search using the specified <span>Xpath</span> field in the selected data            container. If you enter an empty string "" in the <span>Xpath</span> field and select <em>whole content contains</em> from the <span>Function</span> list, searches will be performed in all the            fields of all entities in the selected data container. </li> <li> <kbd>is empty or              null</kbd>: Returns an empty field or a null value.</li> </ul> <p>Before using the conditions, bear in mind the          following:</p> <ul> <li> <p>Depending on the type of field the <span>Xpath</span> points to, only certain operators              apply. For example, if the field is a boolean, only the <em>Equal</em> or <em>Not Equal</em>              operators are appropriate.</p> </li> <li> <p>Searches in the master database support both full              text search and standard SQL search, while searches in the staging database only              support standard SQL search. For more information about how to manage database search              modes, see <em> <cite>Talend                  Installation and Upgrade Guide</cite> </em>.</p> </li> <li> <p>Standard SQL search considers the search content as              an integrate phrase to be matched, while full text search interprets the search              content as a phrase which contains multiple words, and the records that match any of              the words will be returned. For example, if the search content is "test first name",              full text search considers it as three independent words "test", "first", and "name",              while standard SQL search considers it as one phrase "test first name".</p> </li> <li> <p>The operator <em>Not                Equal</em> does not support multi-occurrence fields or complex type fields.</p> </li> </ul> </li> <li> <span>Value</span>: Enter                        between inverted commas the value you want to use. Note that if the value                        contains XML special characters such as /, you must also enter the value in                        single quotes ("'ABC/XYZ'") or the value will be considered as an                        XPath.</li> <li> <p> <span>Predicate</span>: Select a predicate from the drop-down list.</p> <p>The predicates            <kbd>none</kbd> (default), <kbd>or</kbd>, <kbd>and</kbd>, and <kbd>Not</kbd> are now available for use. The other predicates are          reserved for future.</p> <ul> <li> <kbd>none</kbd>            (default): is interpreted as <kbd>and</kbd> by            default.</li> <li> <kbd>or</kbd>: returns a            record if any of the conditions separated by it is true.</li> <li> <kbd>and</kbd>: returns            a record if all the conditions separated by it are true.</li> <li> <kbd>Not</kbd>: returns a record if the            condition on which it is defined is not true.</li> </ul> <div><span>Information note</span><span>Note:</span> The <kbd>or</kbd> predicate is interpreted only if it is defined on all          conditions, except the last condition. Otherwise the <kbd>or</kbd> predicate          is always interpreted as <kbd>and</kbd>. For more information, see the related          description of behaviors of filters using multiple conditions and predicates in Talend            MDM on <span>Talend Help Center</span> (<a href="https://help.talend.com/" target="_blank">https://help.talend.com</a>).</div> </li> </ul><br><br>If you clear this check box, you have the<br>option of selecting particular IDs to be displayed in the ID value column of the<br>IDS table.<br><br>Information noteNote:<br><br>If you clear the Use multiple conditions check box, the<br>Batch Size option<br>in the Advanced<br>Settings tab will no longer be available |
| Skip Rows | Enter the number of lines to be ignored. |
| Max Rows | Maximum number of rows to be processed. If<br>Limit = 0, no row is read or processed. |
| Die on error | Select this check box to skip the row in error<br>and complete the process for error-free rows. If needed, you can retrieve the<br>rows in error via a Row<br>&gt; Rejects<br>link. |

## Advanced settings

| Batch Size | Number of lines in each processed batch.<br><br>Information noteNote:<br><br>This option is not displayed if you have<br>cleared the Use multiple<br>conditions check box in the Basic settings view. |
| --- | --- |
| Loop XPath query | The XML structure node on which the loop is<br>based. |
| Mapping | Column: reflects the<br>schema as defined in the Edit schema editor.<br><br><br>XPath query: Type in<br>the name of the fields to extract from the input XML structure.<br><br><br>Get Nodes: Select this<br>check box to retrieve the Xml node together with the data. |
| tStatCatcher Statistics | Select this check box to gather the processing<br>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<br>error occurs. This is an After variable and it returns a string. This variable functions<br>only if the Die on error check box<br>is cleared, if the component has this check<br>box.<br><br><br>NB\_LINE:<br>the number of rows processed. This is an After variable and it returns an integer.<br><br>A Flow variable functions during the execution of a component<br>while an After variable functions after the execution of the component.<br><br>To fill up a field or expression with a<br>variable, press Ctrl + Space to<br>access the variable list and choose the variable to use from it.<br><br>For further information about variables, see *Talend Studio*<br>*User Guide*. |
| --- | --- |

## Usage

| **Usage rule** | Use this component as a start component. It<br>needs an output flow.<br><br>If an MDM entity has a large number of foreign key fields, it<br>may take you a long time to query data records that pertain to the entity using<br>the tMDMInput component.<br><br>For more information about the<br>workaround, see the article How to read data effectively that pertains to an<br>MDM entity with many foreign key fields.<br><br>For more information about the<br>workaround, see the article How to read data effectively that pertains to an<br>MDM entity with many foreign key fields on Talend Help Center ([https://help.talend.com](https://help.talend.com/)).<br><br>You can increase the timeout values for a Job using this component<br>to help process a large number of data records. For more information, see advanced<br>execution settings for JVM parameters in the article *Timeout values for a Job using<br>MDM components*<br>on Talend Help Center ([https://help.talend.com](https://help.talend.com/)). |
| --- | --- |