tInformixSP – Docs for ESB 5.x

Component Family

Databases/Informix

Function

tInformixSP calls procedures
stored in a database.

Purpose

tInformixSP allows you to
centralise multiple and complex queries in a database and enables
you to call them more easily.

Basic settings

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 properties stored
centrally.

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

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.

Host

Database server IP address.

Port

Listening port number of DB server.

Database

Name of the database.

Schema

Name of the schema.

Username and
Password

User authentication information.

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.

Instance

Name of the Informix instance to be used. This information can
generally be found in the SQL hosts
file.

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.

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 designs. 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:

SP Name

Enter the exact name of the stored procedure (SP).

Is Function / Return result
in

Select this check box if only one value must be returned.

From the list, select the the schema column upon which the value
to be obtained is based.

Parameters

Click the Plus button and select the various Schema Columns that will be required by the
procedures. Note that the SP schema can hold more columns than there
are parameters used in the procedure.

Select the Type of
parameter:

IN: Input parameter.

OUT: Output parameter/return
value.

IN OUT: Input parameters is to be
returned as value, likely after modification through the procedure
(function).

RECORDSET: Input parameters is to
be returned as a set of values, rather than single value.

Use Transaction

Clear this check box if the database is configured in the NO_LOG
mode.

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.

tStatCatcher Statistics

Select this check box to collect log data at a 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 more information on Dynamic settings and context
variables, see Talend Studio User Guide.

Usage

This is an intermediary component. It can also be used as an entry
component. In this case, only the entry parameters are
authorized.

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

The stored procedure syntax must correspond to that of the
database.

This component requires installation of its related jar files. For more information about the
installation of these missing jar files, see the section describing how to configure the
Studio of the Talend Installation and Upgrade Guide.