Skip to main content Skip to complementary content
Qlik Resources
Announcements
Loading SearchUnify's search If you need assistance with your product, please contact Qlik Support.
Qlik Customer Portal
Loading SearchUnify's search If you need assistance with your product, please contact Qlik Support.
Qlik Customer Portal

Executing Artifacts on a Remote Engine from Talend Studio

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 the Talend Management Console User Guide.
  • The selected Remote Engine is running.
  • 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.

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 the Talend Management Console User Guide.

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

    Example

  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

  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 Studio run operation, build it as a Standalone Job. For instructions, see Troubleshooting Remote Engine executions.

In this section

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!

Leave your feedback here