tOracleConfiguration properties for Apache Spark Batch

Property type

Either Built-In or Repository.

Built-In: No property data stored centrally.

Repository: Select the repository file where the properties are stored.

Connection type

The available drivers are:

• Oracle OCI: Select this connection type to use Oracle Call Interface with a set of C-language software APIs that provide an interface to the Oracle database.

• Oracle Custom: Select this connection type to access a clustered database. With this type of connection, the Username and the Password fields are deactivated and you need to enter the connection URL in the URL field that is displayed.

  For further information about the valid form of this URL, see JDBC Connection strings from the Oracle documentation.

• Oracle Service Name: Select this connection type to use the TNS alias that you give when you connect to the remote database.

• WALLET: Select this connection type to store credentials in an Oracle wallet.

• Oracle SID: Select this connection type to uniquely identify a particular database on a system.

DB Version

Select the version of the Oracle database to be used.

Use tns file

Select this check box to use the metadata of a context included in a tns file.

Note that one tns file may have many contexts.

TNS File: Enter the path to the tns file manually or browse to the file by clicking the [...] button next to the field.

Select a DB Connection in Tns File: Click the [...] button to display all the contexts held in the tns file and select the desired one.

Host

Enter the IP address of the database server.

Port

Enter the listening port number of the database server.

Database

Enter the name of the database to be used.

Schema

Enter the name of the schema.

Username and Password

Enter the user authentication data.

To enter the password, click the [...] button next to the password field, enter the password in double quotes in the pop-up dialog box, and click OK to save the settings.

Additional JDBC parameters

Specify additional connection properties for the database connection you are creating. The properties are separated by semicolon and each property is a key-value pair, for example, encryption=1;clientname=Talend.

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

connection pool

In this area, you configure, for each Spark executor, the connection pool used to control the number of connections that stay open simultaneously. The default values given to the following connection pool parameters are good enough for most use cases.

• Max total number of connections: enter the maximum number of connections (idle or active) that are allowed to stay open simultaneously.

  The default number is 8. If you enter -1, you allow unlimited number of open connections at the same time.

• Max waiting time (ms): enter the maximum amount of time at the end of which the response to a demand for using a connection should be returned by the connection pool. By default, it is -1, that is to say, infinite.

• Min number of idle connections: enter the minimum number of idle connections (connections not used) maintained in the connection pool.

• Max number of idle connections: enter the maximum number of idle connections (connections not used) maintained in the connection pool.

Evict connections

Select this check box to define criteria to destroy connections in the connection pool. The following fields are displayed once you have selected it.

• Time between two eviction runs: enter the time interval (in milliseconds) at the end of which the component checks the status of the connections and destroys the idle ones.

• Min idle time for a connection to be eligible to eviction: enter the time interval (in milliseconds) at the end of which the idle connections are destroyed.

• Soft min idle time for a connection to be eligible to eviction: this parameter works the same way as Min idle time for a connection to be eligible to eviction but it keeps the minimum number of idle connections, the number you define in the Min number of idle connections field.

Usage rule

This component is used with no need to be connected to other components.

The configuration in a tOracleConfiguration component applies only on the Oracle related components in the same Job. In other words, the Oracle components used in a child or a parent Job that is called via tRunJob cannot reuse this configuration.

This component, along with the Spark Batch component Palette it belongs to, appears only when you are creating a Spark Batch Job.

Note that in this documentation, unless otherwise explicitly stated, a scenario presents only Standard Jobs, that is to say traditional Talend data integration Jobs.

Spark Connection

This connection is effective on a per-Job basis.