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

Announcements
Qlik Connect 2026 Agenda Now Available: Explore Sessions
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

Passing context variable from one shell script to another.

Hi there,

 

I have the following problem: While using the "Build Job" option in Talend to create a executable shell script, this script gets cleary overwritten when I use the "Build Job" option again (e.g. a newer version of the job is created). This means, that all of my declared context variables inside the script are getting deleted. Therefore I want to write a second shell script, in which all of my context is declared and, calls the executable shell script from the "Build Job" option and passes the context to it. 

 

So here is my question: Is it possible to pass context variables from a arbitrary shell script to the executable shell script, without editing the executable shell script?

 

Best regards

 

Kanopus

Labels (2)
4 Replies
Anonymous
Not applicable
Author

Hi
I am trying to understand your issue. Why you said the context variable are deleted? If you build the same job and with the same path, the context variable are still export in the executable script.

Did you edit the script and pass the new value to context variables?

Regards
Shong

Anonymous
Not applicable
Author

you can pass context to the generated scripts by using the arguments: ./jobName_run.sh --context_param VAR1=VALUE1 --context_param VAR2=VALUE2
Anonymous
Not applicable
Author

./jobName_run.sh --context_param VAR1=VALUE1 --context_param VAR2=VALUE2

 

Can some please tell me how to pass the variable value from my shell script to talend context ?

 

I want send to tsoap  from the shell script output values. if you guys have any step by step guidance.

 

thanks 

 

 

 


variable.JPG
Anonymous
Not applicable
Author

Hi

When you build a job, it's build the job with the parameters that are in your context.

If you are using differents parameters to run the job, you have two options :

 

1- You create many contexts : Default, Test, Prod, Dev, ...

And simply use the appropriate context when running the job

 

2. You can create a file with the parameters you want to use in the job, and load it with tContextLoad

 

Hoping that this will help

 

Regards

Maurice