Run profiles

Run profiles for Jobs

Run profiles allow you to define the resource configuration for executing Jobs on Talend Remote Engine or on an engine cluster. You enter custom values or choose from the drop-down list via the Engines > <RemoteEngine/Cluster_name> > Run profiles > ADD PROFILE > JVM arguments path.

You can create multiple run profiles for the same engine or cluster, but a run profile belongs only to a single runtime. If you want to use the same profile settings on another engine or cluster, you must create a new run profile for them.

When creating or editing a Job task, you can select which run profile to use for its execution.

Run profiles for data services and Routes

Depending on the type of the task, the selected Remote Engine must have the corresponding run profile set either when the engine is created, or later in the Edit engine wizard accessible via the Engines > <RemoteEngineName> > path. Run profiles allow you to activate Talend Runtime or the microservice runner on a Talend Remote Engine.

When adding Remote Engines to the cluster, they will retain their run profile type.

Run profiles for pipelines

Run profiles contain the set of configurations for executing pipelines on a Remote Engine Gen2 or on a Cloud Engine for Design, according to your license type. You can define the right resource allocation and advanced properties used at runtime in the run profiles. Based on your license and engine type, different run profile types are available.

A Remote Engine Gen2 can have several run profiles, but a run profile can belong only to a single Remote Engine Gen2.

After you add a run profile to an engine, you must refresh the Talend Cloud Pipeline Designer page for it to be visible in the run profile list.