Exporting Talend-job as a standalone-job

[Tugce_Gueduek]

Hello,

im using Talend Cloud Data Management Platform

Version: 8

Build id: 20250822_0619-patch

R2025-08

I am exporting a Talend job as a standalone job using the “Build Job” function in Talend Studio.
This process generates a ZIP archive that contains all required artifacts to run the job independently, including a shell script and context files.

During the export, it is possible to select a context. In our case, we use two contexts: PROD and DEV.
I exported the job with the PROD context selected. Inside the generated ZIP archive, a file named PROD.properties is present.

When I run the standalone job on a Linux (Ubuntu) virtual machine, the job does not use the configuration values from PROD.properties.
Instead, it continues to use the context values that are defined directly within the Talend job itself.

Running the job without parameters:

/home/administrator/talend_jobs/prod/demo/CassandraPomJob_0.1_PROD/CassandraPomJob/CassandraPomJob_run.sh

Running the job while explicitly specifying the context and the properties file:

/home/administrator/talend_jobs/prod/demo/CassandraPomJob_0.1_PROD/CassandraPomJob/CassandraPomJob_run.sh \ --context=PROD \ --context_param_file=/home/administrator/talend_jobs/prod/demo/CassandraPomJob_0.1_PROD/CassandraPomJob/src/main/resources/data_demo/cassandrapomjob_0_1/contexts/PROD.properties

In both cases, the job does not apply the values from PROD.properties.

When I override individual context variables directly via the command line using --context_param, the values are applied correctly. For example:

/home/administrator/talend_jobs/prod/demo/CassandraPomJob_0.1_PROD/CassandraPomJob/CassandraPomJob_run.sh \

--context=PROD \ --context_param broker_host=XX

Why is the standalone job not using the values from the PROD.properties file, even though the file exists in the exported ZIP and is explicitly referenced via --context_param_file?

What is the correct or recommended way to run a Talend standalone job so that it uses the values defined in a context .properties file?

Thanks a lot in advance.

Best regards,

Tugce

[Shicong_Hong]

@Tugce_Gueduek Select the context during building the Job, the context will be set in the jobName_run.bat/jobName_run.sh file, such as:

 ... --context=PROD "$@"

To verify this, open the "jobName_run.sh" file and confirm that it contains the string value "--context=PROD".

By default, the Job will use the values defined in the context "PROD".

Regards

Shicong

[Tugce_Gueduek]

@Shicong_Hong 

Thank you for your support.

I can confirm that the *_run.sh script contains the string --context=PROD. However, my requirement is to change the context values after the job has been exported.

The correct configuration values are maintained in TMC, and therefore I would like the standalone job to use the values from the PROD.properties file.
Currently, even after modifying PROD.properties, the job continues to run with the values that were defined at export time.

Could you please advise how the exported standalone job can be configured to use the values from PROD.properties instead of the hard-coded values?

Thanks a lot in advance

Kind regards

Tugce

[Gjeremy]

Hi @Tugce_Gueduek , you are not using the right context files :

/home/administrator/talend_jobs/prod/demo/CassandraPomJob_0.1_PROD/CassandraPomJob/src/main/resources/data_demo/cassandrapomjob_0_1/contexts/PROD.properties

there is another folder that should be like this :

/home/administrator/talend_jobs/prod/demo/CassandraPomJob_0.1_PROD/CassandraPomJob/data_demo/cassandrapomjob_0_1/contexts

And if you change the value in the context.properties files of this folder it will be taken into account.

Best regards
Jérémy