August 15, 2023

tFileInputLDIF – Docs for ESB 6.x

tFileInputLDIF

Reads an LDIF file row by row to split them up into fields and sends the fields as
defined in the schema to the next component using a Row connection.

tFileInputLDIF Standard properties

These properties are used to configure tFileInputLDIF running in the Standard Job framework.

The Standard
tFileInputLDIF component belongs to the File family.

The component in this framework is generally available.

Basic settings

Property type

Either Built-in or Repository.

 

Built-in: No property data stored
centrally.

 

Repository: Select the repository
file where the properties are stored. The fields that follow are
completed automatically using the data retrieved.

File Name

Name of the file and/or variable to be processed.

For further information about how to define and use a variable in
a Job, see
Talend Studio

User Guide.

add operation as prefix when the entry is modify
type

Select this check box to display the operation mode.

Value separator

Type in the separator required for parsing data in the given file.
By default, the separator used is ” ,“.

Die on error

Select this check box to stop the execution of the Job when an
error occurs. Clear the check box to skip the row on error and
complete the process for error-free rows. If needed, you can collect
the rows on error using a Row >
Reject link.

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

Advanced settings

Encoding

Select the encoding type from the list or select Custom and define it manually. This field
is compulsory for DB data handling.

Use field options (for Base64 decode
checked)

Select this check box to specify the Base64-encoded columns of the
input flow. Once selected, this check box activates the Decode Base64 encoding values table to
enable you to precise the columns to be decoded from Base64.

Note:

The data type of the columns to be handled by this check box
is byte[] that you define in
the input schema editor.

tStatCatcher Statistics

Select this check box to gather the Job processing metadata at a
Job level as well as at each component level.

Global Variables

Global Variables

NB_LINE: the number of rows processed. This is an After
variable and it returns an integer.

ERROR_MESSAGE: the error message generated by the
component when an error occurs. This is an After variable and it returns a string. This
variable functions only if the Die on error check box is
cleared, if the component has this check box.

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

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.

Usage

Usage rule

Use this component to read full rows in a voluminous LDIF file.
This component enables you to create a data flow, using a Row > Main link, and to create a reject flow with a
Row > Reject link filtering the data which type does not
match the defined type. For an example of usage, see Procedure from tFileInputXML.

Limitation

Due to license incompatibility, one or more JARs required to use this component are not
provided. You can install the missing JARs for this particular component by clicking the
Install button on the Component tab view. You can also find out and add all missing JARs easily on the
Modules tab in the
Integration
perspective of your
studio. You can find more details about how to install external modules in Talend Help Center (https://help.talend.com).

Related scenario


Document get from Talend https://help.talend.com
Thank you for watching.
Subscribe
Notify of
guest
0 Comments
Inline Feedbacks
View all comments
0
Would love your thoughts, please comment.x
()
x