In this part of the course, I will show you [ navigate Talend DI ] the main view of the TOS Data Integration tool and tell you about the most important elements that allow you to quickly create data processing job. I will also explain the basic concepts you will meet in Talent (component, job, joblet).
The main view: Navigate Talend DI
In version 7.2.1, TOS data integration contains the following elements:
a. Menu bar – provides the ability to use basic project configurations and available basic functions applications, including reading and writing;
b. Toolbar – provides quick access to the most common used tool operations;
c. Repository – centralizes and stores all objects necessary to build a project;
d. Design workspace – enables the design of ETL processes;
e. Palette – allows access to all components available in a given version of the Talend tool;
f. Outline view – allows access to component parameters;
g. Code viewer – provides information about generated process code;
h. Configuration views – allow for simple and quick modification of component settings, process settings and starting data processing.
Configuration view consoles that are good to know
- job view – general information about the process (owner, version number, etc.), statistics settings
- context view – variables assigned to context which will be visible in the integration process
- component view – a view in which you set all parameters of the components placed in the designer (e.g. name of the source file, connection to the database)
- run view – in this view you will start the process in debug or normal mode and you will see the consumption of resources during processing
The each ETL tool has its own rules and concepts. If you have used any of the data processing tools before, then you probably know what I am talking about. Let’s take a closer look at them. (Navigate Talend DI)
A component can be considered in two ways. From a graphic point of view, this is only an icon, an element that we can place on the screen of the work area. However, from a technical point of view it is a functional element that performs a specific task of the process, e.g. tAggregateRow is responsible for data aggregation, tTeradataOutput for loading data into Teradata.
Job is an integration process, data flow from source to target through various transformations. It is the basic object of the TOS DI tool and focuses on translating business needs into executable code. As we are already at the source objects – in Talend they are called Input, while the target objects are Output.
The joblet is a specific type of job, but that is re-usable. They can be used in various jobs or repeatedly in the same integration process. If you need to build a transformation logic that will be used in many processes, and only the source or target will change – use the joblet instead of the job. There is only one small drawback – joblets are only available in the licensed version of Talend Data Integration.
Could You Please Share This Post? I appreciate It And Thank YOU! :) Have A Nice Day!
We are sorry that this post was not useful for you!
Let us improve this post!
Tell us how we can improve this post?