Use a taskflow to control the execution sequence of multiple
Data Integration
tasks.
You can invoke and run a taskflow in the following ways:
From the taskflow designer
To run a taskflow from the taskflow designer, open the taskflow and click
Run
in the upper-right part of the page.
You can also create one or more taskflow inputs and run the taskflow with the inputs. To run the taskflow using taskflow inputs, open the taskflow, and then from the
Actions
menu, select
Run Using
.
As an API
To run a taskflow as an API, you must first publish the taskflow as a service, and then run it. When you publish a taskflow, Data Integration generates the service URL and the SOAP service URL. You can use these endpoint URLs to run the taskflow as an API. When you run a taskflow as an API, you can dynamically provide input parameters for the tasks that the taskflow contains and perform orchestration.
Using the RunAJob utility
To run a taskflow using the RunAJob utility, the taskflow must be published. To use the RunAJob utility, type the RunAJob utility command
cli.bat runAJobCli
followed by arguments.
Initiated by a file listener
You can invoke a taskflow through a connector file listener. Within the taskflow, define the binding type as
Event
and select the connector file listener as the event source. When you publish the taskflow, the taskflow subscribes to the connector file listener that is defined in it. When a file event occurs, the connector file listener invokes the taskflow. For example, if you configure the connector file listener to listen for new files on a folder, the connector file listener invokes the associated taskflow each time a new file arrives in the specified folder.
For more information about file listeners, see
Components
.
Initiated by Data Ingestion and Replication tasks
You can use the following types of
Data Ingestion and Replication
tasks to invoke a taskflow:
Application Ingestion and
Replication
tasks
Database Ingestion and
Replication
tasks
Define the binding type as
Event
and select an
application ingestion and replication
task or a
database ingestion and replication
task as the event source. When you define an ingestion
and replication task, you can select the
Execute in
Taskflow
option on the last wizard page to make the task
available to add to taskflows. For incremental load jobs, you can also
optionally select the
Add Cycle ID
option on the page
for the target to include cycle ID metadata in the target table. When you
configure the taskflow, you can select an ingestion and replication task as
an event source and add any appropriate transformation type to transform the
ingested data. The taskflow is automatically triggered to start when either
the initial load task successfully completes or after each CDC cycle in an
incremental load operation. If a CDC cycle ends but the previous taskflow
run is still running, the data is queued and waits for the previous taskflow
to complete.
For more information about
Data Ingestion and Replication
tasks, see
Data Ingestion and Replication
.
According to a schedule
To run a taskflow on a schedule, create a schedule in Administrator and associate the taskflow with the schedule.
ASK INFAPreview
