By scheduling its run on a Remote Engine or cluster, your Job task will be executed in an on-premises secure runtime.
- Current Remote Engine sub folders tree should be reserved for internal
. ├── activemq-data ├── bin ├── data ├── deploy ├── esbrepo ├── etc ├── instances ├── lib ├── scripts ├── system └── TalendJobServersFiles
- Job generated (permanent) files can be stored in any new directory outside of <RemoteEngineInstallationDirectory>.
- Temporary files should be managed with the tCreateTemporaryFile component.
- Go to Management.
- Select the correct environment from the top menu.
Click Tasks in the correct workspace.
Select the task to run on the Remote Engine or cluster from the
You can use the filters on the left-hand side of the page to limit the results.
On the task details page, click next to Execution.
- In the Edit task wizard, select the Remote Engine or cluster on which you want to deploy the task from the Runtime drop-down list.
Select a run profile.
You can choose a previously created run profile for the selected Remote Engine or cluster to set the JVM parameters for the task execution.
Set the log level.
Select the lowest log level to be taken into account.
This feature is only available with engine versions 2.8.3 and above.
ExampleIf the log level is set to Warning, only logs flagged as Warning and Error will be displayed on the Task execution log page.
If you have scheduled the execution on a single engine, you
have the option to run your Job as another user by entering their username in
the Run as impersonated user
For more information about user impersonation, see the Configuring user impersonation for Talend Remote Engine.
- Optional: If you have chosen an engine cluster as the runtime, you can run the task on multiple engines at the same time by selecting the Allow parallel execution of this task option.
- You can also select the execution frequency from the Run type drop-down list.
- Click GO LIVE.