tSystem – Docs for ESB 5.x

Component family

System

Function

tSystem executes one or more
system commands.

Purpose

tSystem can call other processing
commands, already up and running in a larger Job.

Basic settings

Use home directory

Select this check box to change the name and path of a dedicated
directory.

Use Single Command

When the required command is very simple, to the degree that, for
example, only one parameter is used and without space, select this
option to activate its Command
field. In this field, enter the simple system command. Note that the
syntax is not checked.

Use Array Command

Select this option to activate its Command field. In this field, enter the system
command in array, one parameter per line.

For example, enter the following command with consecutive spaces
in array for
Linux:

Standard
Output and Error
Output

Select the type of output for the processed data to be transferred
to.

to console: data is passed on to
be viewed in the Run view.

to global variable: data is
passed on to an output variable linked to the tSystem component.

to console and to global variable: data is passed on to
the Run view and to an output
variable linked to the tSystem
component.

normal: data is passed on to the
component that comes next.

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.

Since version 5.6, both the Built-In mode and the Repository mode are
available in any of the Talend solutions.

Click Edit schema to make changes to the schema. If the
current schema is of the Repository type, three options are
available:

Click Sync columns to retrieve
the schema from the preceding component in the Job.

Built-in: You create and store the schema locally for
this component only. Related topic: see Talend Studio User Guide.

Repository: You have already created the schema and
stored it in the Repository. You can reuse it in various projects
and job flowcharts. Related topic: see Talend Studio User Guide.

Environment variables

Click the [+] button to add as
many global variables as needed.

name: Enter the syntax of the new
variable.

value: Enter a value for this
variable according to the context.

Advanced settings

tStatCatcher Statistics

Select this check box to collect log data at the component level.

Usage

This component can typically used for companies which already
implemented other applications that they want to integrate into
their processing flow through Talend.

Global Variables

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.

OUTPUT: the standard output from a process. This is an
After variable and it returns a string.

ERROROUTPUT: the erroneous output from a process. This is
an After variable and it returns a string.

EXIT_VALUE: the exit code from a process. This is an
After variable and it returns an integer.

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.

Connections

Outgoing links (from this component to another):

Row: Main.

Trigger: On Subjob Ok; On Subjob
Error; Run if.

Incoming links (from one component to this one):

Row: Main; Reject; Iterate.

Trigger: On Subjob Ok; On Subjob
Error; Run if; On Component Ok; On Component Error; Synchronize;
Parallelize.

For further information regarding connections, see
Talend Studio User
Guide.

Log4j

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.

Limitation

n/a