Module 9: Working With Data Warehouse Application Console
Module 9: Working With Data Warehouse Application Console
Module 9: Working With Data Warehouse Application Console
7)
Module Objectives
After completing this module you will be able to:
Use the tools and views of the Data Warehouse Application Console (DAC) Describe DAC objects, how they relate to each other, and their roles in Siebel Relationship Management Warehouse (SRMW) ETL
2 of 34
Is a centralized console, providing access to the entire SRMW application to create, configure, and execute ETL
Single command and control point for the SRMW
Provides a framework for the entire life cycle of SRMW implementations Is used to create and manage DAC objects in the DAC repository and to monitor ETL
3 of 34
4 of 34
DAC Versions
Two licensing versions available for DAC The DAC Lite version:
Standard version that comes with any Analytics application Allows you to build and execute ETL plans Is suitable for small data warehouses little or no customization
5 of 34
Editable form
6 of 34
DAC Views
Views
Tabs
Views
7 of 34
Design View
Provides access to create and manage execution plans and related entities
Top pane contains tabs, each of which represents a component of the execution plan, in descending order Bottom pane contains child tabs that relate to the tab selected in the top pane
New entities are edited in the lower pane Execution plan Tasks preceding execution plan Tabs access DAC entities
Database connections
8 of 34
Setup View
Provides access to set up DAC system properties, Informatica servers, database connections, and email notification
Set DAC system properties Register Informatica Servers Set up email recipients
9 of 34
10 of 34
Description
Number of days before DAC automatically updates database statistics If set to True, DAC Server automatically issues statements to update statistics when a table is truncated and loaded If set to True, DAC Server, automatically restarts ETL after a task failure
During ETL, DAC Server drops all query indexes on targets; if set to True, DAC Server groups all indexes for CreateQueryIndexesAtTheEnd creation after ETL is complete
DropAndCreateIndexes If set to True, DAC Server drops and recreates query indexes during ETL
11 of 34
Database Connections tab is used to define database connections for Siebel Transactional and SRMW Refresh date corresponds to LAST_REFRESH_DATE column on source table
12 of 34
Execute View
Schedule ETL
ETL_PROC_WID
Task status
13 of 34
DAC Objects
The DAC repository stores application objects in a hierarchical format that defines a warehouse application DAC objects include:
Tasks
Unique steps executed during ETL Related to data transformation or database objects Are associated with a set of source and target database tables, calling Informatica workflows
Can also create files, call database stored procedures, and execute SQL or XML scripts or operating system commands
At run time, execute based on whether primary source and target tables are component tables of execution plan
Tables
Physical database tables in the transactional or SRMW databases Can be source, fact, dimension, hierarchy, aggregate, or staging, among others
Module 9: Working with Data Warehouse Application Console
14 of 34
Logical grouping of tables Based on a main table that drives the relationship between the other tables in the group Can be star or dimension type group
Subject areas
Logical grouping of table groups Derives component tables from table groups Are included in execution plans
Execution plans
Contains one or more subject areas Plan defined on subject areas that need to be transformed at certain frequencies Derives component tables from subject areas Can be executed manually or scheduled
Module 9: Working with Data Warehouse Application Console
15 of 34
Execution Plans
Schedules
Subject Areas
Table Groups
Tables
Tasks
Dependencies
16 of 34
Execution Plans
Schedules
Subject Areas
Table Groups
W_INVOICE_F
Tables
Tasks
Dependencies
17 of 34
Tasks
Tasks are lowest objects in DAC hierarchy that perform unique ETL steps Tasks are prioritized in queue by DAC Server based on phase
Image Build General Extract Dimension Extract Fact Load Dimension Load Fact Visibility Dimension Hierarchy Slowly Changing Dimension
18 of 34
Task Definitions tab is used to configure tasks For example, the Extract for Invoice Fact task extracts the invoice data
Task name
If there is no refresh date for the source table during extract, this command is issued to Informatica Server; otherwise, Command for Incremental Load is issued
19 of 34
Source Tables and Target Tables tabs are used to specify source and target tables for tasks
S_INVOICE is the main source table for Extract for Invoice Fact task W_INVOICE_FS is the main target table for Extract for Invoice Fact task
The Build Image flag invokes the Change Capture process for the base source tables listed for the task Change Capture is an internal DAC task that populates image tables of the corresponding base source tables
The Build Image flag invokes the Change Capture process for both Primary and Auxiliary source tables
Primary: Primary source of data; track change in a single table Auxiliary: Secondary source of data; track change in more than one table
22 of 34
All Primary or Auxiliary table sources in the Siebel database are assigned an Image Suffix to assist with the change capture process For example, S_ETL_R_IMG_73, S_ETL_I_IMG_73, S_ETL_D_IMG_73 are the image tables for S_INVOICE base source table
23 of 34
Depends on Tasks tab is used to specify prerequisite tasks For example, Extract Missing Codes for List of Values from Invoices is the prerequisite task for the execution of Extract for Invoice Fact
Prerequisite task
24 of 34
The Depends on Tasks tab displays dependent tasks Can be specified in either Depends on Tasks or Dependent Tasks tab depending on which task you are working on
For example, Load into Invoice Fact is a dependent task for Extract for Invoice Fact
Dependent tasks
25 of 34
Tables
Physical database tables in the transactional or SRMW databases Tables tab is used to configure tables in DAC Fact or Dimension tables belong to more than one Table Group
W_INVOICE_F is the main table for INVOICE FACT GROUP
26 of 34
Table Groups
Logically groups tables Contains a central or main table that drives the logical relationship between itself and other tables in the group For example:
W_INVOICE_F is the main table in the INVOICE FACT GROUP INVOICE FACT GROUP table group contains other component tables
27 of 34
Table Groups Tab is used to configure table groups Used to create new table group
28 of 34
Subject Areas
29 of 34
Execution Plans
Contains one or more subject areas defined based on business requirements All Subject Areas is a member of the Complete ETL execution plan Execution Plans tab is used to configure execution plans
Select New to create a new subject area Execution plans can be run from the Design view
30 of 34
Dependency Report
Used to analyze dependencies between tasks that are executed for the selected DAC object To generate a dependency report, select an object and click the Preview button in the Design view
Available for the following objects: table groups, subject areas, and execution plans
31 of 34
32 of 34
Summary
This module showed you how to:
Use the tools and views of the Data Warehouse Application Console (DAC) Describe DAC objects, how they relate to each other, and their roles in Siebel Relationship Management Warehouse (SRMW) ETL
33 of 34
Lab
34 of 34