Using centralized metadata in a Job - 7.3

Talend Open Studio User Guide

Version
7.3
Language
English
Product
Talend Open Studio for Big Data
Talend Open Studio for Data Integration
Talend Open Studio for Data Quality
Talend Open Studio for ESB
Module
Talend Studio
Content
Design and Development
Last publication date
2023-10-11
Available in...

Open Studio for Big Data

Open Studio for Data Integration

Open Studio for ESB

About this task

For recurrent use of files and database connections in various Jobs, we recommend you to store the connection and schema metadata in the Repository tree view under the Metadata node. Different folders under the Metadata node will group the established connections including those to databases, files and systems.

Different wizards will help you centralize connection and schema metadata in the Repository tree view.

Once the relevant metadata is stored under the Metadata node, you will be able to drop the corresponding components directly onto the design workspace.

Procedure

  1. In the Repository tree view of the Integration perspective, expand Metadata and the folder holding the connection you want to use in your Job.
  2. Drop the relevant connection or schema onto the design workspace.
    A dialog box prompts you to select the component you want to use among those offered.
  3. Select the component and then click OK. The selected component displays on the design workspace.

Results

Alternatively, according to the type of component (Input or Output) you want to use, perform one of the following operations:

  • Output: Press Ctrl on your keyboard while you are dropping the component onto the design workspace to directly include it in the active Job.

  • Input: Press Alt on your keyboard while you drop the component onto the design workspace to directly include it in the active Job.

If you double-click the component, the Component view shows the selected connection details as well as the selected schema information.

Note:

If you select the connection without selecting a schema, then the properties will be filled with the first encountered schema.