Conditional Logics in DAC (1)
Posted by Dylan Wan on December 9, 2010
This post will describe three advanced features available in DAC. These are not new, but are not commonly known unless you are an expert of DAC.
DAC is the engine BI Apps uses to generated ETL process flow. It was provided since the Informatica workflow was not able to provided such flexibility to the prepackaged apps.
A tool provided for the software vendor to build the prepackaged apps and the tool provided for building your custom data warehouse have different requirements. The prepackaged apps need to address the deployment requirement from various customers using the same set of the software components. It needs to allow the customers to configure and support the configuration during upgrade, or at least simplify the upgrade process. It needs to support growth and support incremental deployment.
The DAC features described here were designed for these purposes.
1. Configuration Tag
DAC generates the execution plan based on the table dependencies.
Sometimes you want to has better control over it. Putting the tasks into configure Tag will stop the task being added into subject area using the typical generation logic.
You can use Config Tag to group a list of tasks and explicitly add the configure tag to the subject area you want to the tasks to be added.
(to be continued…)
I will talk about these features in the subsequent posts:
2. Related tables
3. Conditional tables
Conditional Logics in DAC (1) | Business Blogs said
[...] This post will describe three advanced features available in DAC. These are not new, but are not commonly known unless you are an expert of DAC. DAC is the engine BI Apps uses to generated ETL process flow. It was provided since the Informatica workflow was not able to provided such flexibility to the prepackaged [...] Dylan’s BI Study Notes [...]