Using centralized metadata in a Job - Cloud

Talend Cloud API Services Platform Studio User Guide

author
Talend Documentation Team
EnrichVersion
Cloud
EnrichProdName
Talend Cloud
task
Design and Development
EnrichPlatform
Talend Management Console
Talend Studio

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. For more information about the Metadata Manager wizards, see Centralizing database metadata.

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.