Creating Custom Informatica Workflows

You must create custom workflows for all customized mappings. The general requirements for creating custom workflows are as follows:

 Create the workflow such that each loads only one table. This helps to integrate the workflow with the DAC.

 The workflow name should match a session name that is used inside the workflow. This helps the DAC to collect certain statistics.

 The flag "Fail parent if this task fails" should be checked for all the sessions within a workflow.

 The flag "Fail parent if this task does not run" should be checked for all the sessions within a workflow.

 The Stop on Errors parameter should be set to 1 for all sessions within a workflow. This parameter is located in the Error Handling area of the Config Object
tab in Informatica Designer.

 Set the appropriate source and target connection values in Informatica Designer.

 If the workflow is going to be used for full load command, you can choose to load in bulk mode (applicable only to Oracle and DB2-UDB databases). If the
workflow is going to be used for the full load command in the DAC, then in the Properties tab of Informatica Designer, set the Target Load type to Bulk. This requires that
the target table does not have any indices during the load. The DAC will drop the indices automatically; no action is required on your part.

 For all entities, such as dimension and fact tables, create two workflows, one to be used for a full load and the other to be used for an incremental load.
Both workflows are based on the same mapping. The same mapping gets executed during both full and incremental loads. This provides an opportunity to tune each of
these load scenarios.

 If the workflow is designed for loading a dimension in a full mode, make sure the workflow also includes a session for the unspecified row creation.

 When defining a task in the DAC, you must choose the appropriate truncate option. This helps the DAC to decide whether to drop and create indices on the
table.

 You should not truncate target tables using the Informatica 'truncate target' option. It is especially important that the DAC handle truncating tables when
extracting from more than a single source system and loading into the same data warehouse. The DAC will dynamically determine when tables need to be truncated. By
setting the truncate option in the Informatica workflow, the table will always be truncated, limiting your ability to extract and load data from multiple sources. For
example, you cannot extract data from two systems and load the data into the same staging table in parallel as the Informatica session will truncate the staging table
when another session is running.

 If some sessions have to be run in serial order and if all the sessions need to be rerun upon failure of the workflow, then you should consider designing a
single workflow that has sessions run in serial. If upon failure, not all of the sessions need to be run again, then consider designing separate workflows and define
dependencies in the DAC.

 The custom workflows can be plugged into an ETL process by registering them in the DAC. All new tasks need to be registered in the DAC, with the
appropriate properties set. Also, you must register in the DAC, source and target tables, task definitions, and dependencies.