# Executing Artifacts on a Remote Engine from Talend Studio

Available in...

* Cloud API Services Platform
* Cloud Big Data
* Cloud Big Data Platform
* Cloud Data Fabric
* Cloud Data Integration
* Cloud Data Management Platform
* Data Fabric
* Qlik Talend Cloud Enterprise Edition
* Qlik Talend Cloud Premium Edition

Talend Studio allows you to deploy and execute your designs on a Remote Engine/JobServer when you work on either a local project or a remote project connected to Talend Management Console.

## Before you begin

* The remote run feature has been enabled for the Remote Engine in Talend Management Console. For more information, see [Enabling remote run in Talend Studio for Job debugging](https://help.qlik.com/talend/en-US/remote-engine-user-guide-linux/Cloud/enabling-remote-run-in-talend-studio).
* The selected Remote Engine is running.
  * Available in:
  * Cloud API Services Platform
  * Cloud Data Fabric
  * Data Fabric
  * Qlik Cloud Enterprise Edition
  * Qlik Talend Cloud Enterprise Edition
  * Qlik Talend Cloud Premium Edition
* If you are deploying Routes or Data Services, ensure that Talend Runtime is running on the same machine as the Remote Engine.
* You have been assigned to a remote project in Talend Management Console.
* If Job artifacts are signed with a custom key, ensure that the Remote Engine is configured to verify them. See [Running trusted tasks with your custom signature](https://help.qlik.com/talend/en-US/run-trusted-artifact-on-re/Cloud/use-custom-signature-key-to-run-tasks). For on-premises servers, see [Configuring a custom Job artifact signature](https://help.qlik.com/talend/en-US/studio-user-guide/8.0-R2026-09/configuring-custom-java-keystore-for-artifact-signature "By default, Talend Studio signs Job artifacts using a signing key stored in a keystore issued by Talend, to prevent accidental or malicious modification of Job artifacts.").

## Procedure

1. Start Talend Studio.
2. Connect to the remote project you have been assigned to by the Project Administrator in Talend Management Console.

   For instructions on how to connect to a remote project, see [Accessing remote projects from Studio](https://help.qlik.com/talend/en-US/studio-user-guide/8.0/tmc-access-projects).

   The Remote Engines available in your account are automatically added to the remote server list in Talend Studio (Window > Preferences > Talend > Run/Debug > Remote).
   ### Example

   ![Remote view in the Preferences dialog box.](https://help.qlik.com/talend/en-US/studio-user-guide/Resources/images/cloud_remote_engine_settings.png)
3. Open your Artifact.
4. Open the Run view underneath the design workspace.
5. Click the Target Exec tab.
6. Select the relevant Remote Engine from the drop-down list.
   ### Example

   ![Target Exec view.](https://help.qlik.com/talend/en-US/studio-user-guide/Resources/images/cloud_remote_run_target_exec.png)
7. Click Run in the Basic Run tab, as usual, to connect to the server and deploy and execute the current Artifact.

   Information noteNote:

   If you receive a connection error, ensure that the agent is running, the ports are available, and the server IP address is correct.
8. Optional: To monitor JVM resource usage during the Artifact execution, you can execute it on the specified Remote Engine/JobServer by clicking Run in the Memory Run tab.
9. Optional: If you want to debug your Artifact, open the Debug Run tab in the Run view, select Traces Debug or Java Debug from the drop-down list, then click the button.

Troubleshooting: If your execution has failed on the Remote Engine, but not during a simple Talend Studio run operation, build it as a Standalone Job. For instructions, see [Troubleshooting Remote Engine executions](https://help.qlik.com/talend/en-US/studio-user-guide/8.0/troubleshooting-remote-engine-executions).

### In this section

* [Troubleshooting Remote Engine executions](https://help.qlik.com/talend/en-US/studio-user-guide/8.0-R2026-09/troubleshooting-remote-engine-executions)