Deploying Service using Datasource via TAC

anna_talend — Sat, 16 Nov 2024 01:02:01 GMT

Hi,

I created a simple service, that will write rows in a Database (Microsoft SQL Server).

To run it in talend runtime I installed the microsoft jdbc drivers and defined a datasource in the runtime. (See https://help.talend.com/reader/T7hdMN16K129AtayaQluAA/hYXPpRqbRueFk0F49kCBBg)

According to the documentation, the datasources name should be ds-sqlserver, but the name of the datasource differs from that in the documentation. It's SAM. I wonder if there is a mistake or if something changed that is not documented?

Queries like "

jdbc:query jdbc/sam

"select ..."" work and return correct data from my database.

In the database component I checked "use datasource" and filled in the name jdbc/sam.

I did not remove

connection data (host/user/password etc.) they were filled with context variables. Then I tried to deploy my servers with the esb-conductor.

The deployment worked but the service is not using my datasource. It's using the values from context.

Then I tried to clear the connection-data in the db-component. Deployment was possible, but the service produces "500 - Server error". The last thing I tried was to change the jdbc-provider in the db-component from "open source JTDS" to "microsoft". This ended in a deployment failure.

Then I tried the same with my openStudio. I installed a datasource (postgresql) and again it's name was sam. I deployed my service in the deployment folder and everything worked as expected. It ignores the connection data filled in the db-componet and uses datasource jdbc/sam.

What is the right way to deploy a service with the ESB-conductor? Why is the name of every newly installed datasource sam?

Thanks for any help

anna.talend

topic Deploying Service using Datasource via TAC in Talend Studio

Deploying Service using Datasource via TAC