Component family |
Databases/DB2 | ||
Basic settings |
Property type |
Either Built-in or Repository. Since version 5.6, both the Built-In mode and the Repository mode are available in any of the Talend solutions. | |
|
|
Built-in: No property data stored centrally. | |
|
|
Repository: Select the repository file in which the properties are stored. The fields that follow are completed automatically using the data retrieved. | |
|
|
Click this icon to open a database connection wizard and store the database connection parameters you set in the component Basic settings view. For more information about setting up and storing database connection parameters, see Talend Studio User Guide. | |
|
Use an existing connection |
Select this check box and in the Component List click the relevant connection component to reuse the connection details you already defined. NoteWhen a Job contains the parent Job and the child Job, if you need to share an existing connection between the two levels, for example, to share the connection created by the parent Job with the child Job, you have to:
For an example about how to share a database connection across Job levels, see Talend Studio User Guide. | |
|
Host |
Database server IP address | |
|
Port |
Listening port number of DB server. | |
|
Database |
Name of the database | |
|
Schema |
Name of the schema. | |
|
Username and Password |
DB user authentication data. 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. | |
|
Schema and Edit Schema |
A schema is a row description. It defines the number of fields (columns) to be processed and passed on to the next component. The schema is either Built-In or stored remotely in the Repository. Since version 5.6, both the Built-In mode and the Repository mode are available in any of the Talend solutions. | |
|
|
Built-in: The schema is created and stored locally for this component only. Related topic: see Talend Studio User Guide. | |
|
|
Repository: The schema already exists and is stored in the Repository, hence can be reused. Related topic: see Talend Studio User Guide. | |
Click Edit schema to make changes to the schema. If the current schema is of the Repository type, three options are available:
| |||
|
Table name |
Select the source table where to capture any changes made on data. | |
|
Query type and Query |
Enter your DB query paying particularly attention to properly sequence the fields in order to match the schema definition. | |
|
Specify a data source alias |
Select this check box and specify the alias of a data source created on the Talend Runtime side to use the shared connection pool defined in the data source configuration. This option works only when you deploy and run your Job in Talend Runtime. For a related use case, see Scenario 4: Retrieving data from a MySQL database using the data source on Talend Runtime side to set up the database connection. This check box is not available when the Use an existing connection check box is selected. | |
|
Data source alias |
Enter the alias of the data source created on the Talend Runtime side. This field is available only when the Specify a data source alias check box is selected. | |
Advanced settings |
Additional JDBC parameters |
Specify additional connection properties for the DB connection you are creating. NoteYou can set the encoding parameters through this field. | |
Trim all the String/Char columns |
Select this check box to remove leading and trailing whitespace from all the String/Char columns. | ||
|
Trim column |
Remove leading and trailing whitespace from defined columns. | |
|
tStat Catcher Statistics |
Select this check box to collect log data at the component level. | |
Dynamic settings |
Click the [+] button to add a row in the table and fill the Code field with a context variable to choose your database connection dynamically from multiple connections planned in your Job. This feature is useful when you need to access database tables having the same data structure but in different databases, especially when you are working in an environment where you cannot change your Job settings, for example, when your Job has to be deployed and executed independent of Talend Studio. The Dynamic settings table is available only when the Use an existing connection check box is selected in the Basic settings view. Once a dynamic parameter is defined, the Component List box in the Basic settings view becomes unusable. For examples on using dynamic parameters, see Scenario 3: Reading data from MySQL databases through context-based dynamic connections and Scenario: Reading data from different MySQL databases using dynamically loaded connection parameters. For more information on Dynamic settings and context variables, see Talend Studio User Guide. | ||
Global Variables |
NB_LINE: the number of rows processed. This is an After variable and it returns an integer. QUERY: the query statement being processed. This is a Flow variable and it returns a string. 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 |
This component covers all possible SQL queries for DB2 databases. | ||
Log4j |
If you are using a subscription-based version of the Studio, the activity of this component can be logged using the log4j feature. For more information on this feature, see Talend Studio User Guide. For more information on the log4j logging levels, see the Apache documentation at http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/Level.html. | ||
Limitation |
This component requires installation of its related jar files. For more information about the installation of these missing jar files, see the section describing how to configure the Studio of the Talend Installation and Upgrade Guide. Note that the DB2 10.5 driver doesn't support JDK 8. To use this component with DB2 10.5, you need to install JDK 7 or an earlier version. |