Talend Connect
Virtual Summit
JOIN US!
And visit the Customer
& Community Lounge.
May 27-28, wherever you are.

How to exclude jdbc driver from job build

Highlighted
One Star

How to exclude jdbc driver from job build

My talend DI job contains PostgresqlConnection component. Assembled DI job includes the postgresql jdbc driver. But the jdbc driver already is installed in the Talend ESB container. How to exclude jdbc driver from build job?
I use Talend DI 6.1.1.

Highlighted
Employee

Re: How to exclude jdbc driver from job build

You will want to use the shared destination approach and then define your postgress data source for the ESB container.
Thomas Steinborn
VP Product Management
Highlighted
One Star

Re: How to exclude jdbc driver from job build

I use the shared destination approach:
   - define "Data source alias" in section Data source on component tPostgresql Connection, use options "Use exists connection" in component tPostgresqlOutput;
 - create shared pool in Talend ESB container.

File $TALEND_ESB_RUNTIME/container/deploy/datasource_ctlproc_owner.xml

<?xml version="1.0" encoding="UTF-8"?>
<blueprint xmlns="">
<bean id="dataSource" class="org.postgresql.ds.PGPoolingDataSource">
  <property name="user" value="ctlproc_owner"/>
  <property name="password" value="pw"/>
  <property name="serverName" value="10.18.40.121"/>
  <property name="databaseName" value="ctlproc_db"/>
  <property name="portNumber" value="5432"/>
  <property name="initialConnections" value="3"/>
  <property name="dataSourceName" value="ctlprocownerPgDS"/>
</bean>



<service interface="javax.sql.DataSource" ref="dataSource">
  <service-properties>
    <entry key="osgi.jndi.service.name" value="jdbc/ctlprocowner_pg_ds"/>
    <entry key="datasource.name" value="ctlprocownerPgDS"/>
  </service-properties>
</service>
</blueprint>


But jdbc driver contains in deploy jar.

2019 GARTNER MAGIC QUADRANT FOR DATA INTEGRATION TOOL

Talend named a Leader.

Get your copy

OPEN STUDIO FOR DATA INTEGRATION

Kickstart your first data integration and ETL projects.

Download now

Best Practices for Using Context Variables with Talend – Part 2

Part 2 of a series on Context Variables

Blog

Best Practices for Using Context Variables with Talend – Part 1

Learn how to do cool things with Context Variables

Blog

Migrate Data from one Database to another with one Job using the Dynamic Schema

Find out how to migrate from one database to another using the Dynamic schema

Blog