3

I am currently trying to run a Talend job from the command line. Since my production environment parameters are different from what I have on my local workstation, I have to provide context parameters when launching the job on the target server:

kaffein@coffeeshop:~$ ./job_run.sh --context_param port=1234 --context_param server=myserver

When I exported the job though, Talend Open Studio (for data integration) generated Default.properties files for all my subjob folders. These files contain my local default context parameters.

Launching my job with the production parameters (like shown above) then fails because it seems that the "local" parameters cannot be overriden by the command-line parameters (--context_param arguments) provided.

Can someone help me on this issue please ?

Brian Tompsett - 汤莱恩
  • 5,753
  • 72
  • 57
  • 129
kaffein
  • 1,766
  • 2
  • 28
  • 54
  • Did you call subjobs with tRunJob component ? If yes, make sure you check the checkbox to propagate the whole context variables to the subjob. Otherwise, the default subjob context will be used – Julien Boulay Jan 07 '14 at 21:01
  • @JulienBoulay thanks but I have already checked this checkbox when building the job. I thought that it would get the context propagated to the child jobs too. It didn't work that way though. What I have done so far is having the params hardcoded in Default.properties file. Obviously not the best approach since it involves a lot of boilerplate copy/paste. – kaffein Jan 08 '14 at 15:40

3 Answers3

2

It may be easier to use Implicit context load under Job Settings in the Project Settings.

Here you can define a file (such as a CSV) of environment parameters such as connection settings and as long as they share the same file path you can then just put the different context variables in the file on the different environments and have Talend load them as part of the job.

Now when you run the job it should use the environment specific context variables as they are loaded from the file.

ydaetskcoR
  • 53,225
  • 8
  • 158
  • 177
  • It's MUCH easier to use it this way. – Balazs Gunics Jan 09 '14 at 21:35
  • To clarify, the format is `key,value` where the comma `,` is a delimiter of choice. Try to get this right the first time, because there is some strong caching that happens on it, and if you change it later it's very hard to get it to propagate. – mastaBlasta Feb 23 '17 at 19:14
1

If you have groups of contexts such as DEV,UAT,PROD etc you can set this param inside your shell script - so if you wanted PROD you would add this param to your shell 

--context=PROD

This will load your PROD parameters from your PROD context properties file, on each build we have modified all our shell scripts to add a check to determine what environment it's on and then passes in the correct context.

RobF
  • 2,758
  • 1
  • 20
  • 25
Governator
  • 11
  • 1
1

I had a similar problem, had also selected the check box for propagating, but then found this

Passing parameters to sub-jobs

In structured applications a Job can call another Job and it's necessary to transmit parameters to sub-jobs. In Talend Open Studio this task is easy. When you create a sub job (that is a job who calls another job) simply click its Component tab and make sure Transmit whole context is checked.

Note that the Component Tag exists in the parent JOB.

I found the solution here http://www.robertomarchetto.com/how_to_parameter_values_talend_job_command_line

Worked for me.

Rob

Rob
  • 11
  • 1