Run DQC
Runs a ONE plan or component. The plan is validated before the run: if the plan is invalid, the task fails with FINISHED_FAILURE state and log details into a log.
Properties
| Name | Type | Description | Expression support | 
|---|---|---|---|
Plan File  | 
mandatory  | 
Relative (to the workflow file) or absolute path to the plan or component to run.  | 
semi-expression  | 
Parallelism Level  | 
mandatory  | 
Parallelism level for a plan execution.
Default value:   | 
none  | 
Parameters  | 
optional  | 
Set of parameters to pass to a component.  | 
none  | 
Path Variables  | 
optional  | 
Set of local path variables to use with the current task.  | 
none  | 
Parameters properties
| Name | Type | Description | expression support | 
|---|---|---|---|
Name  | 
mandatory  | 
Name of the variable.  | 
none  | 
Expression  | 
mandatory  | 
Expression evaluating the value of the parameter. The expression must evaluate to a STRING data type value, otherwise an error is reported.  | 
expression  | 
Path variables properties
| Name | Type | Description | Expression support | 
|---|---|---|---|
Name  | 
mandatory  | 
Name of the path variable.  | 
none  | 
Value  | 
mandatory  | 
Value of the path variable.  | 
semi-expression  | 
Former versions of this task had the runtimeFile parameter, this attribute has been removed.
The Runtime Configuration is now an argument of the <ATACCAMA_HOME>/bin/runewf.[bat|sh] script (for batch jobs).
When workflows are started from ONE Runtime Server Admin, the runtime configuration is read from the Server Configuration.
 | 
Example
<executable class="com.ataccama.adt.task.exec.EwfDqcTask">
    <planFile>file_path</planFile>
    <parameters>
          <parameter name="test" expression="some_value"/>
          <parameter name="test2" expression="123" />
    </parameters>
    <pathVariables>
          <pathVariable name="myPathVariable" value="d:/var/server-root/workflows/one-data/" />
    </pathVariables>
</executable>
Logging
The step redirects logging of the plan to the log file located in the workflow resources directory (as specified in the server configuration).
For each workflow instance, there is a directory named wfinst-<instance_id>/task-<dqc_task_id>.log.
This directory and logging file are created only if there is some content in the log file.
Was this page useful?