Operations in Talend Cloud and their terms and definitions
Talend Cloud provides the elements to centrally define, manage, orchestrate, execute, and promote artifacts published from Talend Studio or Talend Cloud Pipeline Designer.
The following elements facilitate the operations:
| Element | Description |
|---|---|
| Environment | A self-contained space with the required resources that allow the execution of tasks in isolation, without any impact on other environments. |
| Cloud Engine | A compute resource managed by Talend in the cloud that executes tasks. A Cloud Engine is available to an environment. |
| Remote Engine | A compute resource managed by Talend in the cloud that executes tasks. Remote Engines are assigned to environments and workspaces. |
| Remote Engine Cluster | Remote Engines can be grouped together. Any number of clusters can be created
in an environment. Information noteNote: Remote Engines added to a cluster cannot be used as remote
execution server to execute tasks directly from Talend Studio.
|
| Remote Engine Gen2 | A compute resource managed by Talend in the cloud that executes pipeline tasks. |
| Run profile | Run profiles contain the set of configurations for executing tasks. You can define the right resource allocation and advanced properties used at runtime in the run profiles. |
| Workspace | Enables selected users to work together preparing tasks and resources for execution. Any number of workspaces can be created in an environment. Workspaces are used to share tasks, connections, and resources. Users can be added to a workspace with predefined permissions. A user's roles have no impact in a workspace. Groups cannot be added to a workspace. |
| Artifact | A Job, Route, Data Service created in Talend Studio or pipeline created in Talend Cloud Pipeline Designer and published to Talend Cloud. Artifacts are published to a workspace. |
| Connection | Predefined parameter values to access external systems. Connections are created in a workspace. |
| Resource | A cloud data source to store files and directories. Resources are created in a workspace. |
| Task | An artifact with a specific execution configuration created in a workspace. For example, Artifact-1 using Connection-1 executing on RemoteEngine-1. Properly named context variables indicate that an appropriate connection and/or resource must be specified during task configuration. |
| Plan | Scheduled tasks organized into a combination of sequential and parallel steps. Plans are created in a workspace, but may reference tasks from other workspaces in the same environment. |
| Promotion | Provides the mechanism to copy elements from one environment to another. Once tasks and plans have been verified, the promotion is used to advance the elements to the next logical environment. |
The diagram below provides a conceptual example of an environment in Talend Cloud using
Talend Studio
and the elements outlined above.
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!