tJDBCSP – Docs for ESB 5.x

Component family

Databases/JDBC

Function

tJDBCSP calls the specified
database stored procedure.

Purpose

tJDBCSP offers a convenient way
to centralize multiple or complex queries in a database and call
them easily.

Basic settings

JDBC URL

Type in the database location path

Driver JAR

Click the plus button under the table to add lines of the count of
your need for the purpose of loading several JARs. Then on each
line, click the three dot button to open the [Select Module] wizard from which you can select a
driver JAR of your interest for each line.

Class Name

Type in the Class name to be pointed to in the driver.

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

In SP principle, the schema is an input parameter.

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

SP Name

Type in the exact name of the Stored Procedure.

Is Function / Return result
in

Select this check box , if a value only is to be returned.

Select on the list the schema column, the value to be returned is
based on.

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.

Select this check box and specify the alias of a data source created on the Talend Runtime side to use the shared connection pool defined in the data source configuration.
This option works only when you deploy and run your Job in Talend Runtime.

This check box is not available when the Use an existing
connection check box is selected.

Advanced settings

tStatCatcher 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 more information on Dynamic settings and context
variables, see Talend Studio User Guide.

Usage

This component is used as intermediary component. It can be used
as start component but only input parameters are thus allowed.

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 Procedures syntax should match the Database syntax.