Support lineage for Command Tasks in IFPC

Background

Informatica PowerCenter provides a Command task that allow users to leverage bash scripts in Linux system or DOS/batch scripts in Window systems. For example, you can specify shell commands in the Command task to delete reject files, copy a file, or archive target files.

Command task can be used in following ways.

Standalone Command task.

Use a Command task anywhere in the workflow or worklet to run shell commands.

Pre- and post-session shell command.

You can call a Command task as the pre- or post-session shell command for a Session task.

We can use parameters and variables in standalone Command tasks and pre- and post-session shell commands. For example, you might use a service process variable instead of hard coding a directory name.

Standalone Command tasks.

Can use service, service process, workflow, and worklet variables in standalone Command tasks. You cannot use session parameters, mapping parameters, or mapping variables in standalone Command tasks. The Integration Service does not expand these types of parameters and variables in standalone Command tasks.

Pre- and post-session shell commands.

Can use any parameter or variable type that you can define in the parameter file.

Reference: ifpc-command-task

Example of command task used:

Example 1:

Repository: eim_edw_rep_dev101

IFPC folder: ACO

IFPC Workflow Name: wf_ACO_mth_dep_ALCO (Ref: wf_ACO_mth_dep_ALCO.png)

Environment: Manta DEV

Command type: Pre-session Command

Details of the command (taken from IFPC Workflow Manager) (Ref: wf_ACO_mth_dep_ALCO_s_ACO_ALCO_ff_rep.png)

Example 2:

Repository: eim_edw_rep_dev101

IFPC folder: WDY

IFPC Workflow Name: wf_WDY_VWUBSTTIMEOFFBALANCE_DLZ

Environment: Manta DEV

(Ref: wf_WDY_VWUBSTTIMEOFFBALANCE_DLZ.png)

Impact Analysis:

Total number of Command task present in Workflow .xml files is 40779 out of 14142 workflow.xml scanned

Summary

Manta when encounters command task in IFPC workflows then it fails to parse them and silently ignore them in the lineage view. As a result, the generated lineage is incomplete. Current solution is OMD to bridge the lineage gaps due to unsupported dynamic commands in Manta.

Expected Outcome:

Manta should provide a way to represent the source or target when command task is executed