Adding a Dynamic Engine instance and its environment
Add and associate the logical entities of a Dynamic Engine and Dynamic Engine environment to get the manifest files for deployment.
The following sections contain examples of how to use Qlik Talend APIs to perform specific actions.
Setting up a Dynamic Engine instance and its environment using API.
Add and associate the logical entities of a Dynamic Engine and Dynamic Engine environment to get the manifest files for deployment.
Set up SCIM provisioning to easily manage and synchronize user identities across your identity provider, Azure AD in this example, and Talend Cloud.
Synchronize your user identities.
Issue a POST request at the /security/role-mappings endpoint to create this kind of role mapping.
Use a specific API endpoint to easily pause or resume data integration task runs to suit the management needs of your system, for example, to fit a system maintenance window.
Get all task runs of a task scheduled until a given date and check whether some of those runs fall in the system maintenance window.
Pause a task to avoid partial executions and data integrity issues during a maintenance window.
Resume your task to reactivate the schedule executions after the maintenance.
A crawler allows you to retrieve a full list of assets contained in a connection, in a single operation.
This is an end-to-end scenario describing the different operations to create a crawler from a connection.
This is an end-to-end scenario describing the different operations to schedule a crawler run from a Windows environment.
A dataset is a collection of data.
Create or update a description for a specific dataset column.
Create or update descriptions for several dataset columns in one operation.
Get a list of all fields with a description in a specific dataset.
Automate the processes to create users, assign users to groups, assign roles to users and retrieve user profiles.
Call the account/users/ endpoint to create users.
Update a user's email address and keep assigned roles, groups, and workspaces.
Set up IP allowlist policy to restrict user access.
Call the /security/ip-allowlist endpoint to set up your IP allowlist and keep this list inactive.
Call the /security/ip-allowlist/ips endpoint to add IPs to your allowlist.
Each task run generates detailed logs and component metrics to help you monitor and analyze your tasks as often as you need.
Obtain task runs of a given period in a specific environment for monitoring purposes.
Obtain run metrics of a specific task without having to generate or download its logs.
Use the GET method to obtain logs of a task run from the "monitoring/executions/{runId}/logs" endpoint.
Use the monitoring endpoints to fetch run logs of a given period.
Use Talend API service to get the observability metrics of your Data Integration tasks, running on a Cloud Engine or a Remote Engine v2.12.0 onwards.
A service account represents a non-human user entity that uses access tokens to authenticate to Talend Cloud and call a Talend service.
Call the account/service-accounts endpoint to create a service account.
Call the /security/oauth/token endpoint to generate a token for a service account.
Use the service account and its token you created in previous sections to get users under your tenant.
Assign workspace permissions to a service account so that it could run tasks that belong to the related workspace.
Use a service account to run tasks in the following endpoint: https://api.<env>.cloud.talend.com/processing/executions
Use schedule dedicated API endpoints to easily arrange how and when a task or plan can be executed with multiple triggers.
Create a schedule, add triggers, simulate the upcoming events based on this schedule, associate the schedule with a task and if needs be, reuse this schedule for more tasks.
Upgrade your duplicated single-triggered tasks to one single task with multiple triggers.