Skip to main content Skip to complementary content

Creating Remote Engines

Create Remote Engine logical entities in Talend Management Console to be associated with the engine physical entity you have installed.

Before you begin

  • You must have Infrastructure Administrator role in Talend Management Console.


  1. Open Talend Management Console.
  2. Open the Processing page then click the Engines tab.
  3. Click Add and select Remote Engine from the drop-down list.
  4. Select the environment in which to create the engine.
    The current environment is selected by default.
  5. Select the workspace to which you want to assign your engine.
    By default, engines can be used in all the workspaces of the environment.
    To restrict the access to the engine, allocate the engine to be available in only one specific workspace. Only users with the Execute permission on the workspace can access and use the engine.
  6. Enter a name for the engine.
  7. Optional: Select a run profile based on the type of tasks you want to run.
    • Job (set by default)
    • Microservice
    • Talend Runtime (OSGi)
    To deploy data services or Routes from Talend Management Console, you must configure a microservice or OSGi run profile. These profile types can only be configured when creating or editing the Remote Engine, they cannot be added using the Add profile option in the Engine details blade.
  8. If you have chosen a microservice or OSGi run profile, select the Talend Studio version with which your artifact, and both your Talend Remote Engine and Talend Runtime versions are compatible with. For more information, see Compatible Java Environments.
    The system check will prevent you from executing a task on an incompatible Remote Engine version.
  9. Optional: Add a description for the engine.
  10. Click Save.


Your Remote Engine is created. Its status is Not Paired.

What to do next

Click the name of the new Remote Engine to open the Engine details tab. You can find the Remote Engine key to use during the pairing stage on the Manage page. In the documentation, this key is also referred to as a pre-authorization or pairing key.

Screenshot of Remote Engine key in Engine details window.

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 – let us know how we can improve!