Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Join us in Toronto Sept 9th for Qlik's AI Reality Tour! Register Now
cancel
Showing results for 
Search instead for 
Did you mean: 
MattE
Creator II
Creator II

How to publish a job with a password in Talend 7.3.1 Remote Engine

This is a follow on from another topic (https://community.talend.com/s/question/0D55b00006c7WOGCA2/the-job-includes-at-least-one-password-ty...), I've actually got a support ticket open but thought I'd ask in here in case anyone has encountered and solved the same issue.

I've recently upgraded Studio from 7.1 to 7.3. Now, if i create a new job in 7.3 and publish to the remote engine it runs fine. however, if i try and republish a job which was created in a version prior to 7.3 the job fails in the remote engine. The error i get is complaining about passwords

 

[Amazon][JDBC](10100) Connection Refused: [Amazon][JDBC](11640) Required Connection Key(s): PWD; 

 

but I'm able to log these to confirm they are correct so I'm not convinced this is the true problem although if i change the password type from password to string then it works., however, sending a database password as a string is not good practice.

 

Talend's first suggestion was that this is a known issue with the Remote Engine and I should upgrade to the latest at the time (2.11.2) which i have done but the problem still persists.

Labels (2)
3 Replies
Anonymous
Not applicable

Hi

This sounds like a bug on the job migration, you had better provide an example job in the ticket for our support team to reproduce the issue.

 

Regards

Shong

 

 

MattE
Creator II
Creator II
Author

Thanks i will. I have found a work around. If you make sure that the box Transmit whole context is ticked on every tRunJob in the task then the job will run correctly. I'm not sure if this is a bug or a new requirement as you did not need to do this in Studio 7.1 and Remote Engine prior to 2.11.2.

Anonymous
Not applicable

if main job and child job have the same context variable, and you expect the variable always have the same value even though the value is loaded dynamically in main job, you should check the 'Transmit whole context' box on tRunJob.