tAS400Input - 6.3

Talend Components Reference Guide

EnrichVersion
6.3
EnrichProdName
Talend Big Data
Talend Big Data Platform
Talend Data Fabric
Talend Data Integration
Talend Data Management Platform
Talend Data Services Platform
Talend ESB
Talend MDM Platform
Talend Open Studio for Big Data
Talend Open Studio for Data Integration
Talend Open Studio for Data Quality
Talend Open Studio for ESB
Talend Open Studio for MDM
Talend Real-Time Big Data Platform
task
Data Governance
Data Quality and Preparation
Design and Development
EnrichPlatform
Talend Studio

Function

tAS400Input reads a database and extracts fields based on a query.

Purpose

tAS400SInput executes a DB query with a strictly defined statement which must correspond to the schema definition. Then it passes on the field list to the next component via a Main row link.

tAS400Input properties

Component family

Databases / AS/400

 

Basic settings

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.

Note

When 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:

  1. In the parent level, register the database connection to be shared in the Basic settings view of the connection component which creates that very database connection.

  2. In the child level, use a dedicated connection component to read that registered database connection.

For an example about how to share a database connection across Job levels, see Talend Studio User Guide.

 

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.

 

DB Version

Select the AS 400 version in use

 

Host

Database server IP address

 

Port

Listening port number of DB server.

 

Database

Name of the database

 

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.

This component offers the advantage of the dynamic schema feature. This allows you to retrieve unknown columns from source files or to copy batches of columns from a source without mapping each column individually. For further information about dynamic schemas, see Talend Studio User Guide.

This dynamic schema feature is designed for the purpose of retrieving unknown columns of a table and is recommended to be used for this purpose only; it is not recommended for the use of creating tables.

 

 

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:

  • 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.

 

Query type and Query

Enter your DB query paying particularly attention to properly sequence the fields in order to match the schema definition.

Warning

If using the dynamic schema feature, the SELECT query must include the * wildcard, to retrieve all of the columns from the table selected.

Advanced settings

Additional JDBC parameters

Specify additional connection properties for the DB connection you are creating. This option is not available if you have selected the Use an existing connection check box in the Basic settings.

 

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.

Usage

This component offers the flexibility of the DB query and covers all possible SQL queries.

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.

Scenario: Handling data with AS/400

This scenario describes a Job that writes the user information into AS/400, and then reads the information in AS/400 and displays it on the console.

Adding and linking the components

  1. Create a new Job and add a tFixedFlowInput component, a tAS400Output component, a tAS400Input component, and a tLogRow component by typing their names in the design workspace or dropping them from the Palette.

  2. Connect tFixedFlowInput to tAS400Output using a Row > Main connection.

  3. Do the same to connect tAS400Input to tLogRow.

  4. Connect tFixedFlowInput to tAS400Input using a Trigger > OnSubjobOk connection.

Configuring the components

Writing the data into AS/400

  1. Double-click tFixedFlowInput to open its Basic settings view.

  2. Click the [...] button next to Edit schema and in the [Schema] dialog box define the schema by adding three columns: id of Integer type, and name and city of String type.

    Click OK to close the [Schema] dialog box and accept the propagation prompted by the pop-up dialog box.

  3. In the Mode area, select Use Inline Content (delimited file) and enter the following user information in the Content field.

    1;George;Bismarck
    2;Abraham;Boise
    3;Taylor;Nashville
    4;William;Jefferson City
    5;Alexander;Jackson
    6;James;Boise
    7;Gerald;Little Rock
    8;Tony;Richmond
    9;Thomas;Springfield
    10;Andre;Nashville
  4. Double-click tAS400Output to open its Basic settings view.

  5. In the Host, Database, Username and Password fields, enter the information required for the connection to AS/400.

  6. In the Table field, specify the table into which you want to write the data. In this example, it is doct1018.

  7. Select Drop table if exists and create from the Action on table drop-down list, and select Insert from the Action on data drop-down list.

Retrieving the data from AS/400

  1. Double-click tAS400Input to open its Basic settings view.

  2. In the Host, Database, Username and Password fields, enter the information required for the connection to AS/400.

  3. Click the [...] button next to Edit schema and in the [Schema] dialog box define the schema by adding three columns: id of Integer type, and name and city of String type. The data structure is same as the structure you have defined for tFixedFlowInput.

  4. In the Table Name field, enter or browse to the table into which you write the data. In this example, it is doct1018.

  5. In the Query field, enter the SQL query sentence to be used to retrieve the user data from AS/400. In this example, it is SELECT * FROM doct1018.

  6. Double-click tLogRow to open its Basic settings view.

  7. In the Mode area, select Table (print values in cells of a table) for better readability of the result.

Saving and executing the Job

  1. Press Ctrl + S to save the Job.

  2. Press F6 or click Run on the Run tab to run the Job.

    As shown above, the user information is written into AS/400, and then the data is retrieved from AS/400 and displayed on the console.