Select a type of database from the list and click
Apply.

Property type

Either Built-in or
Repository

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.

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.

DB Version

List of database versions.

Host

Database server IP address.

Port

DB server listening port number.

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 using CDC and Edit
Schema

A schema is a row description, it defines the number of fields to
be processed and passed on to the next component. The schema is
either Built-in or stored remotely
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.

Built-In: You create and store the schema locally for this component
only.

Repository: You have already created the schema and stored it in the
Repository. You can reuse it in various projects and Job designs.

Table

Select the source table from which any changes made to data are to
be captured.

Subscriber

Enter the name of the application that will use the change
table.

Events to catch

Insert: Select this check box to
catch the data inserted in the change table since the last
extracion.

Update: Select this check box to
catch the data updated in the change table since the last
extracion.

Delete: Select this check box to
catch the data deleted in the change table since the last
extracion.

Additional JDBC Parameters

Specify additional JDBC parameters for the
database connection created.

This property is not available when the Use an existing connection
check box in the Basic settings view is selected.

Keep data in CDC Table

Select this check box to keep the changes made available to one or
more target systems, even after they have been consulted.

Use cursor

Select this check box to specify the number of rows you want to
work with at at any given time. This option optimises
performance.

Trim all the String/Char columns

Select this check box to delete any spaces found at the beginning
or end of fields, in all of the columns containing character
strings.

Trim column

Remove leading and trailing whitespace from defined
columns.

tStatCatcher Statistics

Select this check box to collect the log data at component
level.

Note that when parallel execution is enabled, it is not possible to use global
variables to retrieve return values in a subjob.

Global Variables

NB_LINE: the number of rows read by an input component or
transferred to an output component. This is an After variable and it returns an
integer.

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.

A Flow variable functions during the execution of a component while an After variable
functions after the execution of the component.

Usage rule

This component is used as a start component. It requires an output
component and a row Main link.