About this task
To add an execution task from Talend Administration Center, complete the following:
From the toolbar on the ESB Conductor page, click
Add to clear the Edition
Enter/select the following information as necessary.
Type in the name of the task to be triggered.
Provide any useful information regarding the task to be carried out.
Type in or select in the list the name of the group in which you want to group your task.
Click the Select Feature button to select from the Artifact repository the artifact you want to deploy and start. The Select Feature from Artifact repository wizard opens.
- In the Repository list, select the repository in which the artifact has been published.
- In the tree view, select the group in which the artifact has been published, then select the feature corresponding to the artifact that has been published, and click OK.
The Repository, URL, Name and Version fields are automatically populated.
Name of the Artifact repository on which the artifact (Service, Route or Generic) has been published. This field is automatically filled in when selecting the feature but you can also type it in manually.
If you selected the artifact to deploy in the Feature field through the Select Feature button, the URL field will automatically be filled in with the Maven URL of the Feature to deploy and start.
But you can also directly type in this URL if you know it. The format of this URL is:
mvn:<groupID>/<artifactID>/<version>/xml. For example: mvn:org.example/route_cFile-feature/0.2/xmlNote: The Repository must have been defined before entering the URL manually.
Select the name of the Feature you want to deploy and start, as an artifact can be made of several features.
The version of the Feature to deploy and start is automatically retrieved.
Select the type of artifact to be deployed and started. It can be: Route, Service or Generic.
If several contexts are available for the selected Feature, select the relevant context.
Select the server on which the task should be deployed and started. Only Talend Runtime servers are available in this list.
If the relevant server does not appear on the list, check the Servers page and make sure the server is correctly configured. For more information regarding the execution server configuration, see Configuring execution servers.
If a virtual server is selected which still has a Cellar Group, a dialog will be shown prompting you to remove the cluster configuration from the virtual server as the Cellar Group option is not supported from version 6.0:
Property ID (PID)
This field is automatically filled in with the identifier of the artifact (the name of the Route, Service or Generic OSGi feature) when this artifact is using a context or a configuration file. So if the artifact does not use any context or configuration file, this field will remain empty.Note: The PID of the task can be manually changed if needed.
Click Save to validate the configuration or
Cancel to cancel the creation of the task.
Tip: If you click on any of the tasks in the list before finalizing the creation or modification of the current task, a dialog box pops up prompting you to save the parameters in the configuration panel before switching to another task. Click Cancel to return to the configuration panel and save the parameters.