Taskflows > Taskflows > Taskflows in a Customer Managed runtime environment
  

Taskflows in a Customer Managed runtime environment

A Customer Managed runtime environment allows Secure Agents to run autonomously after deployment, without requiring a constant internet connection to IDMC.
A taskflow on a Customer Managed Secure Agent group works as follows:
For more information, see Customer Managed Secure Agent groups in the Administrator help.

Rules and guidelines

Consider the following rules and guidelines when you create a taskflow on a Customer Managed Secure Agent group:

Creating a taskflow on a Customer Managed Secure Agent group

Create a taskflow from scratch or use a taskflow template.
    1In Data Integration, click New > Orchestration > Taskflow > Create.
    2Set general properties, start properties, input fields, output fields, and temporary fields for the taskflow. You can also add notes. For more details, see Setting taskflow properties.
    3Add steps to the taskflow. For more information, see Taskflow step support for Customer Managed Secure Agent groups. To reuse an existing taskflow, add it with the Subtaskflow step.
    4 Save the taskflow.

Taskflow step support for Customer Managed Secure Agent groups

A Customer Managed Secure Agent group runs taskflow steps locally, without a connection to IDMC. When you associate a taskflow with the environment, Data Integration validates that the environment supports each step in the taskflow.
The following table describes support for each taskflow step type:
Step
Support on a Customer Managed Secure Agent group
Assignment
Yes
Command Task
Yes
Data Task with a mapping task
Yes
Data Task with dynamic mapping task
No
Data Task with data transfer task, synchronization task, or PowerCenter task
No
Decision
Yes
End
Yes
File Watch Task
No
IntegrationOps Task
No
Data Ingestion and Replication Task
No
Jump
Yes
Notification Task
No
Parallel Paths
Yes
Subtaskflow
Yes
Throw
Yes
Wait
Yes
When you save a taskflow associated with a Customer Managed Secure Agent group, Data Integration also validates the conditions in the following table:
Condition
Result
A step uses a step type that the runtime environment doesn't support.
You can't save the taskflow.
A step references a task or asset associated with a different runtime environment.
You can't save the task.
A step references a task or subtaskflow that hasn't deployed to the environment.
You can't save the taskflow. To resolve this error, deploy the task or subtaskflow with Deploy Tasks. For more information, see Synchronizing a taskflow on a Customer Managed Secure Agent group.
Note:
If you create a runtime environment after you open Data Integration, the environment might not appear in the Runtime Environment list. To refresh the list, clear the browser cache, and then hard reload the page. A standard reload or logging out doesn't refresh the list.

Synchronizing a taskflow on a Customer Managed Secure Agent group

A standard Secure Agent group that is connected to IDMC applies task and schedule changes automatically. A Customer Managed Secure Agent group applies changes only when you synchronize them.
Before you synchronize a taskflow, verify the following prerequisites:
Rules and guidelines
Consider the following rules and guidelines before you synchronize a taskflow:
Synchronizing a taskflow
After you save a taskflow that uses a Customer Managed Secure Agent group, configure the taskflow schedule. For more information, see Scheduling a taskflow. Then synchronize the taskflow to the agent group.
  1. 1In Administrator, click Runtime Environment and select the taskflow that you want to synchronize.
  2. 2From the Actions menu, select Sync Runtime Environment to start the asset synchronization. Data Integration synchronises the taskflow, schedule, and dependencies to the agent group. The synchronization status appears in the notification area. Schedules trigger after all associated assets finish synchronization and activation. For more information, see Runtime Environments in the Administrator help.
  3. 3After synchronization completes, click the taskflow and go to the Monitor tab to view the status. You can also view the taskflow status on the My Jobs page in Data Integration. For more information, see Runtime Environments in the Administrator help.
While the agent group is disconnected, the agent stores run entries locally. When the connection is restored, the entries synchronize automatically to the cloud monitors.
To start a run outside the schedule, use the agent-side REST API. To monitor the run status, see Monitoring taskflow runs on a Customer Managed Secure Agent group.

Monitoring taskflow runs on a Customer Managed Secure Agent group

A Customer Managed Secure Agent group can run taskflows while the agent group is disconnected from IDMC. Monitoring these taskflow runs differs from monitoring runs on an agent group that's connected to IDMC.
Status synchronization
Consider the following behavior when the agent group is disconnected from IDMC:
Job actions
To stop a taskflow run while the agent group is disconnected, use the agent REST API. For more information, see REST API Reference.
View run details while disconnected
While the agent group is disconnected, you can view run details in the following ways:
Notifications and alerts aren't available for taskflow runs on a Customer Managed Secure Agent group. To check the run status, use one of the following methods: