Setting the datasource configuration file

Procedure

Set the database connection details in the MySQL datasource configuration file named datasource-mysql.xml in the <TalendRuntimePath>/add-ons/datasources/dataservice folder.

For MySQL 5.x:

<bean id="mysqlDataSource" class="com.mysql.jdbc.jdbc2.optional.
MysqlConnectionPoolDataSource">
    <property name="url" value="jdbc:mysql://localhost:3306/root"/>
    <property name="user" value="root"/>
    <property name="password" value=""/>
</bean>

<bean id="dataSource" class="org.apache.commons.dbcp.datasources.
SharedPoolDataSource" destroy-method="close">
    <property name="connectionPoolDataSource" ref="mysqlDataSource"/>
    <property name="maxActive" value="20"/>
    <property name="maxIdle" value="5"/>
    <property name="maxWait" value="-1"/>
</bean>

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

For MySQL 8.x:

<bean id="mysqlDataSource" class="com.mysql.cj.jdbc.MysqlConnectionPoolDataSource">
    <property name="url" value="jdbc:mysql://localhost:3306/root"/>
    <property name="user" value="root"/>
    <property name="password" value=""/>
</bean>

<bean id="dataSource" class="org.apache.commons.dbcp.datasources.
SharedPoolDataSource" destroy-method="close">
    <property name="connectionPoolDataSource" ref="mysqlDataSource"/>
    <property name="maxActive" value="20"/>
    <property name="maxIdle" value="5"/>
    <property name="maxWait" value="-1"/>
</bean>

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

Copy the configuration file to the deploy folder within the Talend Runtime container directory. The datasource alias jdbc/sample will be used in the MySQL database components when configuring the Job in Talend Studio. You can also change it as needed.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!

Leave your feedback here