By scheduling its run on a Remote Engine or cluster, your Job task will be executed in an on-premises secure runtime.
By default, you can run 3 different or identical tasks in parallel on a single Remote Engine. For further information about the related configuration, see Running tasks in parallel on a single Remote Engine.
- Current Remote Engine sub folders tree should be reserved for internal
use.
. ├── 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.
Procedure
-
On the task details page, click
next to
Trigger.
- Optional:
Set the task execution timeout by selecting one of the following options:
-
Custom then entering a value.
The default value is 5 minutes and the minimum is 1.
-
Smart Timeout.
For more information on smart timeout, see Enabling smart task timeout.
-
Custom then entering a value.
-
In the Schedule step, click the Add
trigger icon then select the execution frequency and if necessary the
trigger timeout.
You can add one or more triggers to schedule your task or you can manually start the task without a trigger.
Trigger timeout overrides task timeout. By default, the trigger timeout value is the same as the task timeout.
For more information, see Scheduling Job tasks.
Results
