topic Re: Talend Remote Job Publish in Talend Studio

Talend Remote Job Publish

vgandra — Sat, 16 Nov 2024 00:39:23 GMT

We are trying to find the correct resources for the following flow.

Jobs are designed in Talend Studio(with context variables) behind on-prem network/firewall.
The job needs to run in a run time on a different remote network that cannot be directly accessed by the on-prem network.
The context variables need to be set to a different value at run time in the run time environment.
The job schedule(Cron,etc) needs to be configured on run time environment itself.

Limitations:

No studio on remote network environmemt
No Talend cloud. Cannot publish to Talend Cloud and from Cloud to Remote Engine.
No Talend administration center access in run time.
The remote environment will be a client environment to which we will not have any access. We will be able to only guide client admins via screen share but not directly login to machines having talend run time.

What is the best deployment approach for above flow with provided limitations?

Re: Talend Remote Job Publish

Anonymous — Mon, 22 Feb 2021 07:11:38 GMT

With these limitations, you can only export the job script from local studio as archive file, and then deliver the job script to the customer through the mobile hard disk or FTP server. After the customer get the job script, extract the archive file, and then directly execute the job or schedule the job.

Regards

Shong

Re: Talend Remote Job Publish

Alaor_Silva — Mon, 15 Mar 2021 16:35:30 GMT

@Vinay Gandra,

Make sure to OR build the Job using the correct Context, or change the context in the .bat .sh file before send your jobs to be executed wherever they will be running.

Have the information to your Environment

build the Job using the target Environment

After the you build the job and tested Ok in your environment

Go to the Job built folder

D:/path to your job/JobName/jobName.sh or JobName.bat depend on your Operational System

Open it and change the context pointing to the target Environment

There is no need to say that the environment file .properties have to exist

Cheers.