Informatica PowerCenter/PowerMart Designer Guide

Informatica
PowerCenter/
PowerMart
Designer
Last Updated – 30/06/2014
Prepared by Saurastra Ranjan Pattanaik
Designer Workspace
 Designer
Windows are:
 Navigator
 Workspace
 Status bar
 Output
 Instance
Data
 Target
Center Of Excellence-Data Data

Warehousing 2
Designer Tools
 Source Analyzer - To import or create source definitions for
flat file, XML, Cobol, ERP, and relational sources
 Warehouse Designer - To import or create target definitions
 Transformation Developer - To create reusable

transformations
 Mapplet Designer - To create mapplets
 Mapping Designer - To create mappings
Center Of Excellence-Data
Warehousing 3
Source Analyzer
 The following types of source definitions can be imported or created or
modified in the Source Analyzer:
 Relational Sources – Tables, Views, Synonyms
 Files – Fixed-Width or Delimited Flat Files, COBOL Files
 Microsoft Excel Sources
 XML Sources – XML Files, DTD Files, XML Schema Files
 Data models using MX Data Model PowerPlug
 SAP R/3, SAP BW, Siebel, IBM MQ Series by using PowerConnect
Warehousing 4
Source Analyzer – Importing
Relational Source Definitions
 Can import relational source definitions from database
tables, views, and synonyms
 When you import a source definition, you import the

following source metadata:
 Source name
 Database location
 Column names
 Data types
 Key constraints Center Of Excellence-Data

Warehousing 5
Source Analyzer – Importing
Relational Source Definitions
Warehousing 6
Source Analyzer – Flat File
Sources
 When you create a flat file source definition, you
must define the properties of the file
 The Source Analyzer provides a Flat File Wizard to
prompt you for the following file properties:
 File name and location
 File type
 Column names and data types
 Column size and null characters for fixed-width

files
 Delimiter type, quote character, and escape
character for delimited files
Warehousing 7
Sources
 Delimited flat files features:
 They are always character oriented and line
sequential
 The column precision is always measured in
characters, and each row ends with a newline
character
 Fixed width flat files features:
 They are byte-oriented, which means that the field
lengths are measured in bytes
 They can also be line sequential, which means each
row ends with a newline character
Warehousing 8
Sources
 You can edit the following flat file properties in the

Source Analyzer:
 Table name, business purpose, owner, and description
 File type
 Delimiter type, quote character, and escape character for
delimited files
 Column names and datatypes
Warehousing 9
Warehouse Designer
 Can create target definitions in the Warehouse Designer
for file and relational sources
 Can Create definitions in the following ways:
 Import the definition for an existing target - Import
the target definition from a relational target
 Create a target definition based on a source
definition:
 Relational source definition
 Flat file source definition
 COBOL source definition

Warehousing 10
Warehouse Designer
 In addition to creating target definitions, you can
perform the following tasks in the Warehouse
Designer:
 Edit target definitions - When you change target
definitions, the Designer propagates the changes to
any mapping using that target
 Create relational tables in the target database - If the
target tables do not exist in the target database, you
can generate and execute the necessary SQL code to
create the target table
 Preview relationalCenter
target data - You can preview the 11
Of Excellence-Data
Warehousing
Warehouse Designer –
Create/Edit Target Definitions
Warehousing 12
Warehouse Designer
 When you import a target definition, the Designer
imports the following target details:
 Target name
 Database location
 Column names
 Datatypes
 Key constraints
 Key Relationships
Warehousing 13
Transformations
 A transformation is a repository object that
generates, modifies, or passes data
 Transformations can be active or passive
 An active transformation can change the number of
rows that pass through it
 A passive transformation does not change the
number of rows that pass through it
 Transformations can be connected to the data flow,
or they can be unconnected
Warehousing 14
Transformations
Transformation Types:
 Advanced External Procedure - Calls a procedure
in a shared library or in the COM layer of
Windows NT
 Aggregator - Performs aggregate calculations
 ERP Source Qualifier - Represents the rows that
the Informatica Server reads from an ERP source
when it runs a session
 Expression - Calculates a value
 External Procedure - Calls a procedure in a shared
library or in the COM layer of Windows NT
Warehousing 15
Transformations
Transformation Types Continued…
 Filter - Filters records
 Input - Defines mapplet input rows. Available only

in the Mapplet Designer
 Joiner - Joins records from different databases or
flat file systems
 Lookup - Looks up values
 Normalizer - Normalizes records, including those

read from COBOL sources
Warehousing 16
Transformations
 Output - Defines mapplet output rows. Available only
in the Mapplet Designer
 Rank - Limits records to a top or bottom range
 Router - Routes data into multiple transformations
based on a group expression
 Sequence Generator - Generates primary keys
 Source Qualifier - Represents the rows that the
Informatica Server reads from a relational or flat file
source when it runs a session
Warehousing 17
Transformations
 Stored Procedure - Calls a stored procedure
 Update Strategy - Determines whether to insert, delete,

update, or reject records
 XML Source Qualifier - Represents the rows that the

Informatica Server reads from an XML source when it
runs a session
Warehousing 18
Transformations – Port Default
Values
 Can specify a default value for a transformation port with
which Nulls and errors will be overwritten
 Without Intervention:
 Input ports - Null values are passed without changes
 Output ports - Transformation errors are rejected,
sending input rows to session log
 With Intervention:
 Input ports - Null values will be changed as specified
 Output ports - Upon transformation error, the specified
default value will be used
Warehousing 19
Aggregator Transformation
 Performs aggregate
calculations
 Components of the
Aggregator
Transformation
 Aggregate
expression
 Group by port
 Sorted Input
option
Warehousing  Aggregate cache 20
To configure ports in the Aggregator transformation you
can:
 Enter an aggregate expression in any output port, using
conditional clauses or non-aggregate functions in the
port
 Create multiple aggregate output ports
 Configure any input, input/output, output, or variable

port as a Group By port, and use non-aggregate
expressions in the port
Warehousing 21
 The following aggregate functions can be used within an

Aggregator transformation:
 AVG, COUNT, FIRST, LAST, MAX , MEDIAN
 MIN, PERCENTILE, STDDEV,

Center SUM, VARIANCE
Of Excellence-Data
Warehousing 22
Expression Transformation
 Can use the Expression transformation to
 perform any non-aggregate calculations
 Calculate values in a single row
 test conditional statements before you output the

results to target tables or other transformations
 Ports that must be included in an Expression
Transformation:
 Input or input/output ports for each value used in
the calculation
 Output port for the expression
Warehousing 23
Expression Transformation
 can create any number of output ports in the

transformation
Warehousing 24
Filter Transformation
 All ports in a Filter transformation are input/output

 Only rows that meet the condition pass through it
 Does not allow setting output default values
Warehousing 25
Joiner Transformation
 Joins two related heterogeneous sources residing in different

locations or file systems
 Can be used to join
 Two relational tables existing in separate databases
 Two flat files in potentially different file systems
 Two instances of the same XML source
 A relational table and a flat

Center file source
Of Excellence-Data
Warehousing 26
 Use the Joiner transformation to join two sources with at
least one matching port
 It uses a condition that matches one or more pairs of ports
between the two sources
 Requires two input transformations from two separate data
flows
 It supports the following join types
 Normal (Default)
 Master Outer
 Detail Outer
 Full Outer
Warehousing 27
It can not be used in the following situations:
 Both input pipelines originate from the same
Source Qualifier transformation
Normalizer transformation
Joiner transformation
 Either input pipelines contains an Update
Strategy transformation
Warehousing 28
Lookup Transformation
 Used to look up data in a relational table, view, or
synonym
 It compares Lookup transformation port values to
lookup table column values based on the lookup
condition
 Can use the Lookup transformation to perform many
tasks, including:
 Get a related value
 Update slowly changing dimension tables
Warehousing 29
 Can configure the transformation to be connected or
unconnected, cached or uncached
 Cached or uncached Lookups:
 Sometimes you can improve session performance by
caching the lookup table
 If you cache the lookup table, you can choose to use
a dynamic or static cache
 By default, the lookup cache remains static and does
not change during the session
 With a dynamic cache, the Informatica Server inserts
rows into the cache during the session
 This enables you Center
to look up values in the target and
Of Excellence-Data
insert them if they doWarehousing
not exist 30
Some of the Lookup Transformation
Properties:
 Lookup SQL Override
 Lookup Table Name
 Lookup Caching Enabled
 Lookup Condition
 Location Information
Warehousing 31
 You might want to configure the transformation to use a

dynamic cache when the target table is also the lookup table.
When you use a dynamic cache, the Informatica Server inserts
rows into the cache as it passes rows to the target.
Warehousing 32
Connected Lookup Transformation
 Receives input values directly from another
transformation in the pipeline
 For each input row, the Informatica Server queries the
lookup table or cache based on the lookup ports and the
condition in the transformation
 If the transformation is uncached or uses a static cache,
the Informatica Server returns values from the lookup
query
 Passes return values from the query to the next
transformation
Warehousing 33
 Unconnected Lookup Transformation exists
separate from the pipeline in the mapping
 You write an expression using the :LKP reference
qualifier to call the lookup within another
transformation
 Some common uses for unconnected lookups
include:
 Testing the results of a lookup in an expression
 Filtering records based on the lookup results
 Marking records for update based on the result
of a lookup (for example, updating slowly
changing dimension tables)
Warehousing 34
 With unconnected Lookups, you can pass multiple input values

into the transformation, but only one column of data out of the
transformation
 Use the return port to specify the return value in an unconnected
lookup transformation CenterWarehousing
Of Excellence-Data
35
Rank Transformation
 Allows to select only the top or bottom rank of
data, not just one value
 Can use it to return
 the largest or smallest numeric value in a port or
group
 the strings at the top or the bottom of a session
sort order
 During the session, the Informatica Server caches
input data until it can perform the rank calculations
 Can select only one port to define a rank
Warehousing 36
Rank Transformation
 When you create a Rank transformation, you can configure the

following properties:
 Enter a cache directory
 Select the top or bottom rank
 Select the input/output port that contains values used to
determine the rank. You can select only one port to define a
rank Center Of Excellence-Data
Warehousing 37
 Select the number of rows falling within a rank
Rank Transformation
 Rank
Transformation
Ports:
 Variable port -
Can use to store
values or
calculations to
use in an
expression
 Rank port - Use
Center Of Excellence-Data to designate the
column for which
Warehousing 38
Router Transformation
 It is similar to a Filter transformation
 A Filter transformation tests data for one condition
and drops the rows of data that do not meet the
condition
 A Router transformation tests data for one or more
conditions and gives you the option to route rows of
data that do not meet any of the conditions to a
default output group
 If you need to test the same input data based on
multiple conditions, use a Router Transformation in
a mapping instead of creating multiple Filter
transformations toCenter
perform the same task
Of Excellence-Data
Warehousing 39
Comparing Router & Filter
Transformations
Warehousing 40
 It has the following
types of groups:
 Input
 Output
 There are two types of

output groups:
 User-defined groups
 Default group
 Create one user-defined

group for each
Warehousing
condition that you want41
 Can enter any expression that returns a single value in a group

filter condition or can also specify a constant for the condition
 A group filter condition returns TRUE or FALSE for each row
that passes through the transformation, depending on whether a
row satisfies the specified condition
Warehousing 42
Warehousing 43
Sequence Generator
Transformation
 Generates numeric values
 It can be used to
 create unique primary key values
 replace missing primary keys
 cycle through a sequential range of numbers
 It provides two output ports: NEXTVAL and CURRVAL
 These ports can not be edited or deleted
 Can not add ports to the sequence generator
transformation
Warehousing 44
Sequence Generator

Transformation
When NEXTVAL is connected to the input port of
another transformation, the Informatica Server generates
a sequence of numbers
 Properties of Sequence Generator Transformation:
 Start Value
 Increment By
 End Value
 Current Value
 Cycle
 Number of Cached Values
 Reset Center Of Excellence-Data

Warehousing 45
Sequence Generator
Transformation
 You connect the NEXTVAL port to a downstream

transformation to generate the sequence based on the Current
Value and Increment By properties
 You typically only connect the CURRVAL port when the
NEXTVAL port is alreadyCenterconnected to a downstream
Of Excellence-Data
Warehousing 46
transformation
Source Qualifier
Transformation
 Can use the Source Qualifier to perform the
following tasks:
 Join data originating from the same source
database
 Filter records when the Informatica Server reads
source data
 Specify an outer join rather than the default inner
join
 Specify sorted ports
 Select only distinct values from the source
 Create a custom query to issue a special SELECT

statement for the Informatica
Warehousing
Server to read 47
Source Qualifier Transformation
 For relational sources, the Informatica Server generates

a query for each Source Qualifier when it runs a session
 The Informatica Server reads only those columns in
Source Qualifier that are connected to another
transformation Warehousing 48
 Can use the Source Qualifier transformation to
perform an outer join of two sources in the same
database
 The Informatica Server supports two kinds of outer
joins:
 Left - Informatica Server returns all rows for the
table to the left of the join syntax and the rows from
both tables that meet the join condition
 Right - Informatica Server returns all rows for the
table to the right of the join syntax and the rows
from both tables that meet the join condition
 With an outer join, you can
Center Of generate the same results as49
Excellence-Data
Warehousing
 Properties that can be configured, are:
 SQL Query
 User-Defined Join
 Source Filter
 Number of Sorted Ports
 Select Distinct
 Tracing Level
Warehousing 50
Stored Procedure Transformation
 A Stored Procedure transformation is
 an important tool for populating and maintaining
databases
 used to call a stored procedure
 The stored procedure must exist in the database

before creating a Stored Procedure transformation
 One of the most useful features of stored
procedures is the ability to send data to the stored
procedure, and receive data from the stored
procedure
Warehousing 51
 There are three types of data that pass between the
Informatica Server and the stored procedure:
 Input/Output parameters - For many stored
procedures, you provide a value and receive a value in
return
 Return values - Most databases provide a return value
after running a stored procedure
 Status codes - Status codes provide error handling for
the Informatica Server during a session
Warehousing 52
 The following list describes the options for running
a Stored Procedure transformation:
 Normal - During a session, the stored
procedure runs where the transformation exists
in the mapping on a row-by-row basis
 Pre-load of the Source - Before the session
retrieves data from the source, the stored
procedure runs
 Post-load of the Source - After the session
retrieves data from the source, the stored
procedure runs
 Pre-load of the Target - Before the session
sends data to the
Centertarget, the stored procedure
Of Excellence-Data
runs Warehousing 53
 Can set up the Stored Procedure transformation in one of two

modes, either connected or unconnected
 The flow of data through a mapping in connected mode also
passes through the Stored Procedure transformation
 Cannot run the same instance of a Stored Procedure
transformation in both Center
connected and unconnected mode in a
Of Excellence-Data
mapping. You must create different

Warehousing
instances of the 54
 The unconnected Stored Procedure transformation is

not connected directly to the flow of the mapping
 It either runs before or after the session, or is called by
an expression in another
Center Of transformation
Excellence-Data in the mapping
Warehousing 55
Update Strategy Transformation
 It determines whether to insert, update, delete or
reject records
 Can configure the Update Strategy transformation
to either pass rejected rows to the next
transformation or drop them
 Update strategy can be set at two different levels:
 Within a session - When you configure a session,
you can instruct the Informatica Server to either
treat all records in the same way or use
instructions coded into the session mapping to
flag records for different database operations
 Within a mapping Center-OfitExcellence-Data
can be used to flag records
Warehousing 56
Update Strategy Transformation
 The most important
feature of this
Constants for Each Database
transformation is its
Constants for Each
Database Operation
update strategy
Nume expression
Operation Constant ric
Value  This expression is used
Insert DD_INSERT 0
Update DD_UPDATE 1
to flag individual
Delete DD_DELETE 2 records for insert,
Reject DD_REJECT 3
delete, update, or reject
 The Informatica Server
treats any other value as
an insert
Warehousing 57
Transformation Language
 The designer provides a transformation language to
help you write expressions to transform source data
 With the transformation language, you can create a
transformation expression that takes the data from a
port and changes it
 Can write expressions in the following
transformations:
 Aggregator
 Expression
 Filter
 Rank
 Router Warehousing 58
 It includes the following components:
 Functions - Over 60 SQL-like functions
 Operators
 Constants
 Mapping parameters and variables
Warehousing 59
 Expressions can consist of any combination of the

following components:
 Ports (input, input/output, variable)

 String literals, numeric literals
 Constants
 Functions
 Mapping parameters and mapping variables
 Operators Center Of Excellence-Data

Warehousing 60
Mapping
Sample Mapping
Warehousing 61
Mapping
 The Designer allows you to copy mappings:
 Within a folder
 To another folder in the same repository
 When you copy a mapping, the Designer creates a

copy of each component in the mapping
 The Designer allows you to export a mapping to an
XML file and import a mapping from an XML file
 Can debug a valid mapping to gain troubleshooting
information about data and error conditions
Warehousing 62
Mapping - Validation
 The Designer marks a mapping valid for the

following reasons:
 Connection validation - Required ports are
connected and that all connections are valid
 Expression validation - All expressions are valid
 Object validation - The independent object

definition matches the instance in the mapping
Warehousing 63
Mapping - Validation
Warehousing 64
Mapping Wizard
 The Designer provides two mapping wizards
 Getting Started Wizard
 Slowly Changing Dimensions Wizard
 Both wizards are designed to create mappings for

loading and maintaining star schemas, a series of
dimensions related to a central fact table
 The Getting Started Wizard can create two types of
mappings:
 Simple Pass Through
 Slowly Growing Target

Warehousing 65
Mapping Wizard
 The Simple Pass Through mapping inserts all source

rows
 Use it to load tables when you do not need to keep
historical data in the target table
 If source rows already exist in the target, truncate or
drop the existing target before running the session
 In the Simple Pass Through mapping, all rows are
current Center Of Excellence-Data
Warehousing 66
Mapping Wizard
 The Slowly Changing Dimensions Wizard can create
the following types of mapping:
 Type 1 Dimension mapping
 Type 2 Dimension/Version Data mapping
 Type 2 Dimension/Flag Current mapping
 Type 2 Dimension/Effective Date Range
mapping
 Type 3 Dimension mapping
 Can use the following sources with a mapping
wizard:
 Flat file Center Of Excellence-Data
Warehousing 67
 Relational
Mapping Wizard
 The Slowly Growing Target mapping performs the

following:
 Selects all rows
 Caches the existing target as a lookup table
 Compares logical key columns in the source against
corresponding columns in the target lookup table
 Filters out existingCenter
rows Of Excellence-Data
Warehousing 68
Mapping Wizard
 The Type 1 Dimension mapping filters source rows

based on user-defined comparisons and inserts only
those found to be new dimensions to the target
 Rows containing changes to existing dimensions are
updated in the target by overwriting the existing
dimension Center Of Excellence-Data
Warehousing 69
Mapping Wizard
The Type 1 Dimension mapping performs the following:
 Compares source columns against corresponding target
columns if key columns match
 Flags new rows and changed rows
 Creates two data flows: one for new rows, one for
changed rows
 Generates a primaryCenter
keyOffor new rows
Excellence-Data
Warehousing 70
 Inserts new rows to the target
Mapping Wizard
 The Type 2 Dimension/Version Data mapping filters source

rows based on user-defined comparisons and inserts both new
and changed dimensions into the target
 Changes are tracked in the target table by versioning the primary
key and creating a version number for each dimension in the
table
 In the Type 2 Dimension/Version Data target, the current
Warehousing 71
version of a dimension has the highest version number and the
Mapping Wizard
 The Type 2 Dimension/Version Data mapping performs
the following:
 Creates two data flows: one for new rows, one for
changed rows
 Generates a primary key
Center and version number for new
Of Excellence-Data
rows Warehousing 72
Mapping Wizard
 The Type 2 Dimension/Flag Current mapping filters source

rows based on user-defined comparisons and inserts both new
and changed dimensions into the target
 Changes are tracked in the target table by flagging the current
version of each dimension
Centerand versioning the primary key
Of Excellence-Data
Warehousing 73
Mapping Wizard
 The Type 2 Dimension/Flag Current mapping performs the
following:

 Creates two data flows: one for new rows, one for changed
rows Center Of Excellence-Data
 Generates a primary key and current flag for new rows

Warehousing 74
Mapping Wizard
 The Type 2 Dimension/Flag Current mapping
performs the following continued…
 Increments the existing primary key and sets the
current flag for changed rows
 Inserts changed rows in the target
 Updates existing versions of the changed rows in the

target, resetting the current flag to indicate the row is
no longer current
Warehousing 75
Mapping Wizard
 The Type 3 Dimension mapping filters source rows based on user-defined

comparisons and inserts only those found to be new dimensions to the
target
 Rows containing changes to existing dimensions are updated in the target
 When updating an existing dimension, the Informatica Server saves
existing data in different columns of the same row and replaces the
existing data with the updates
Warehousing 76
Mapping Wizard
 The Type 3 Dimension mapping performs the following:

 Creates two data flows: one for new rows, one for updating
changed rows
 Generates a primary Center
keyOfand optionally notes the effective
Excellence-Data
date for new rows Warehousing 77

Mapping Wizard
 The Type 3 Dimension mapping performs the
following continued…
 Inserts new rows to the target
 Writes previous values for each changed row into

previous columns and replaces previous values with
updated values
 Optionally uses the system date to note the effective
date for inserted and updated values
 Updates changed rows in the target
Warehousing 78
Mapping Parameters
 It represents a constant value that can be defined
before running a session
 It retains the same value throughout the entire
session
 Can declare and use the parameter in a mapping or
mapplet
 The value of the parameter should be defined in a
parameter file for the session
 During the session, the Informatica Server evaluates
all references to the parameter
Warehousing 79
Mapping Variable
 It represents a value that can change through session
 Can declare the parameter in a mapping or mapplet and
then use a variable function in the mapping to
automatically change the value of the variable
 At the beginning of a session, the Informatica Server
evaluates references to a variable to its start value
 At the end of a successful session, the Informatica Server
saves the final value of the variable to the repository
 Can override the saved value by defining the start value of
the variable in a parameter file for the session
Warehousing 80
Debugger
 Can debug a valid mapping to gain troubleshooting
information about data and error conditions
 To debug a mapping, you configure and run the Debugger
from within the Mapping Designer
 When you run the Debugger, it pauses at breakpoints and
allows you to view and edit transformation output data
 After you save a mapping, you can run some initial tests
with a debug session before you configure and run a
session in the Server Manager
Warehousing 81
Debugger
Warehousing 82
Debugger
 Can Use the following process to debug a mapping:
 Create breakpoints
 Configure the Debugger
 Run the Debugger
 Monitor the Debugger
 Debug log
 Session log
 Target window
 Instance window
 Modify data and breakpoints

Warehousing 83
Debugger
 After you set the instance name, breakpoint type, and optional
data condition, you can view each parameter in the Breakpoints
section of the Breakpoint Editor
Warehousing 84
Debugger
 After initialization, the Debugger moves in and out of
running and paused states based on breakpoints and
commands
 The Debugger can be in one of the following states:
 Initializing - The Designer connects to the
Informatica Server
 Running - The Informatica Server processes the data
 Paused - The Informatica Server encounters a break

and pauses the Debugger
 While the Debugger pauses, you can review and modify
transformation output data Warehousing 85
Mapplet
 A mapplet is a reusable object that represents a set of
transformations
 It allows to reuse transformation logic and can contain as
many transformations as needed
 Mapplets can:
 Include source definitions
 Accept data from sources in a mapping
 Include multiple transformations
 Pass data to multiple pipelines
 Contain unused ports
Warehousing 86
Mapplet
 For example, the mapplet in the figure above, contains a set of

transformations with reusable logic
 The mapplet uses a series of Lookup transformations to
determine if dimension data exists for each input row
 The Update Strategy transformation flags rows differently
depending on the look up results
Warehousing 87
Mapplet
 A mapplet can contain transformations, reusable
transformations, and shortcuts to transformations
 Each mapplet must include the following:
 One Input transformation, Source Qualifier, or ERP
Source Qualifier transformation
 At least one Output transformation
 A Mapplet should contain exactly one of the following:
 Input transformation with at least one port connected to
a transformation in the mapplet
 Source Qualifier transformation with at least one port
connected to a source definition
 ERP Source Qualifier transformation with at least one
port connected to a source definition
Warehousing 88
Sample Mapplet in a Mapping
Warehousing 89
Mapplet
The Designer does not support
the following objects in a
mapplet:
 COBOL source definitions
 Joiner transformations
 Normalizer
transformations
 Non-reusable Sequence
Generator transformations
 Pre- or post-session stored
procedures
 Target definitions
 PowerMart 3.5-style
Warehousing 90
LOOKUP functions
Mapplet
 Source data for a mapplet can originate from one of two
places:
 Sources within the mapplet
 Sources outside the mapplet
 A mapplet can be connected to sources in a mapping by
creating mapplet input ports
 By adding an Input transformation to the mapplet, input
ports can be created
 Ports in an Input transformation cannot be connected
directly to an Output transformation and each port in it
can be connected to only one transformation
Warehousing 91
Mapplet
 For example, in the figure, the mapplet uses the Input

transformation IN_CustID_FirstLastName to define mapplet
input ports. The Input transformation is connected to one
transformation, EXP_WorkaroundLookup, which passes data to
two separate transformations
Warehousing 92
Mapplet
 To create mapplet output ports, you add Output
transformations to the mapplet
 Each port in an Output transformation connected to
another transformation in the mapplet becomes a
mapplet output port
 Each Output transformation in a mapplet represents a
group of mapplet output ports, or output group
 Each output group can pass data to a single pipeline in
the mapping
 To pass data from a mapplet to more than one pipeline,
create an Output transformation for each pipeline
Warehousing 93
Mapplet
 For example, in the figure above, the mapplet contains three

Output transformations to allow the mapplet to connect to three
different pipelines in a mapping. Notice the Output
transformation OUT_UpdateChanges contains an unconnected
port named LAST_NAME Center Of Excellence-Data
Warehousing 94
Mapplet
Warehousing 95
Business Components
 They allow to organize, group, and display sources

and mapplets in a single location in a repository folder
 They let you access data from all operational systems

within your organization through source and mapplet
groupings representing business entities
 They let you view your sources and mapplets in a

meaningful way using hierarchies and directories
Warehousing 96
Business Components
 A business component is a reference to any of the
following objects:
 Source
 Mapplet
 Shortcut to a source
 Shortcut to a mapplet
 The Designer creates a business component when you

drag any source or mapplet into any directory of the
business component tree
 Can use the same source or mapplet multiple times in the
business component tree
Warehousing 97
Business Components
Warehousing 98
Business Components
 Since business components are references to another
object, you can edit the object from its original location
or from the business components directory
 Can create business components from sources or
mapplets within the repository by creating a local
shortcut
 can create business components from sources or
mapplets across repositories by creating a global
shortcut
Warehousing 99
Cubes and Dimensions
 Can create multi-dimensional metadata through the
Designer by defining Cubes and Dimensions
 Can create and edit cubes and dimensions through
Warehouse Designer interface
 A Dimension is a set of level properties that describe a
specific aspect of a business, used for analyzing the
factual measures of one or more cubes which use that
dimension
 A Cube is a set of related factual measures, aggregates,
and dimensions for a specific dimensional analysis
problem. Example: regional product sales
Warehousing 100
Questions
Warehousing 101

Informatica PowerCenter/PowerMart Designer Guide

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Informatica PowerCenter/PowerMart Designer Guide

Încărcat de

Drepturi de autor:

Formate disponibile

Informatica

Center Of Excellence-Data Data

 Warehouse Designer - To import or create target definitions

 Transformation Developer - To create reusable

 Mapplet Designer - To create mapplets

 Mapping Designer - To create mappings

 Files – Fixed-Width or Delimited Flat Files, COBOL Files

 Microsoft Excel Sources

 XML Sources – XML Files, DTD Files, XML Schema Files

 Data models using MX Data Model PowerPlug

 SAP R/3, SAP BW, Siebel, IBM MQ Series by using PowerConnect

 When you import a source definition, you import the

 Key constraints Center Of Excellence-Data

 Column names and data types

 Column size and null characters for fixed-width

 You can edit the following flat file properties in the

 Flat file source definition

 COBOL source definition

 Input - Defines mapplet input rows. Available only

 Normalizer - Normalizes records, including those

 Update Strategy - Determines whether to insert, delete,

 XML Source Qualifier - Represents the rows that the

 Configure any input, input/output, output, or variable

 The following aggregate functions can be used within an

 MIN, PERCENTILE, STDDEV,

 Calculate values in a single row

 test conditional statements before you output the

 can create any number of output ports in the

 All ports in a Filter transformation are input/output

 Joins two related heterogeneous sources residing in different

 Two flat files in potentially different file systems

 Two instances of the same XML source

 A relational table and a flat

 You might want to configure the transformation to use a

 With unconnected Lookups, you can pass multiple input values

 When you create a Rank transformation, you can configure the

 There are two types of

 Create one user-defined

 Can enter any expression that returns a single value in a group

 Number of Cached Values

 Reset Center Of Excellence-Data

 You connect the NEXTVAL port to a downstream

 Select only distinct values from the source

 Create a custom query to issue a special SELECT

 For relational sources, the Informatica Server generates

 Number of Sorted Ports

 The stored procedure must exist in the database

 Can set up the Stored Procedure transformation in one of two

mapping. You must create different

 The unconnected Stored Procedure transformation is

 Mapping parameters and variables

 Expressions can consist of any combination of the

 Ports (input, input/output, variable)

 Mapping parameters and mapping variables

 Operators Center Of Excellence-Data

 To another folder in the same repository

 When you copy a mapping, the Designer creates a

 The Designer marks a mapping valid for the

 Object validation - The independent object

 Slowly Changing Dimensions Wizard

 Both wizards are designed to create mappings for

 Slowly Growing Target