Talend Studio allows you to deploy and execute your Jobs on a remote JobServer when you work on either a local project, or a remote one while you are connected with the Talend Administration Center.
To run a Job on a remote JobServer, make sure that:
if you are working on local project, you have set the remote JobServer details in the Preferences > Talend > Run/Debug > Remote window of Talend Studio.
If you are working on a remote project and your Studio is connected with the Talend Administration Center, the JobServer settings are retrieved from the Talend Administration Center and are read only.
If you are working on a remote project and your Studio is disconnected with the Talend Administration Center, as no JobServer settings are retrieved and you cannot configure them in the Studio either, you cannot run a Job remotely.
the agent is running on the remote JobServer.
You can also use the CommandLine to transfer your Jobs from your Talend Studio to a remote JobServer for Job execution. To use the CommandLine, make sure that:
you have logged on to a remote project via a remote connection.
you have set the CommandLine details in your Studio.
For more information on how to set JobServer and CommandLine details in your Talend Studio, see Remote run configuration (Talend > Run/Debug).
Once these operations are complete, perform the following:
Go to the Run view of Talend Studio design workspace.
Click the Target Exec tab in the Run view.
Select the relevant remote JobServer on the list.
When working on a remote project while you are connected with Talend Administration Center, you are recommended to select a virtual server so that the Talend Administration Center will determine which physical server your Job will be executed on to achieve load balancing.
If the Enable Commandline server (Deprecated) option is selected in the Preferences > Talend > Run/Debug > Remote window, the Commandline Server list appears. From this list, select the relevant remote CommandLine server.
Click the Run button of the Basic Run tab, as usual, to connect to the server and deploy then execute in one go the current Job.
If you get a connection error, check that the agent is running, the ports are available and the server IP address is correct.
You can also execute your Job on the specified JobServer by clicking the Run button of the Memory Run tab if you want to monitor JVM resource usage during the Job execution.