Documente Academic
Documente Profesional
Documente Cultură
When you use a mapplet in a mapping, you use an instance of the mapplet. Like a reusable transformation,
any change made to the mapplet is inherited by all instances of the mapplet.
To use a mapplet in a mapping, first we need to configure it for input and output. In addition to
transformation logic that you configure, a mapplet has the following components:
Mapplet input
Mapplet output
Mapplet ports
Note:
Follow the following rules and guidelines when you edit a mapplet that is used by mappings:
•Do not delete a port from the mapplet. The Designer deletes mapplet ports in the mapping when you
delete links to an Input or Output transformation or when you delete ports connected to an Input or
Output transformation.
•Do not change the datatype, precision, or scale of a mapplet port. The datatype, precision, and scale
of a mapplet port is defined by the transformation port to which it is connected in the mapplet.
Therefore, if you edit a mapplet to change the datatype, precision, or scale of a port connected to a port
in an Input or Output transformation, you change the mapplet port.
•Do not change the mapplet type. If you remove all active transformations from an active mapplet, the
mapplet becomes passive. If you add an active transformation to a passive mapplet, the mapplet
becomes active.
Include source definitions. Use multiple source definitions and source qualifiers to provide source
data for a mapping.
Accept data from sources in a mapping. If you want the mapplet to receive data from the
mapping, use an Input transformation to receive source data.
Include multiple transformations. A mapplet can contain as many transformations as you need.
Pass data to multiple transformations. You can create a mapplet to feed data to multiple
transformations. Each Output transformation in a mapplet represents one output group in a
mapplet.
Contain unused ports. You do not have to connect all mapplet input and output ports in a
mapping.
Use the following rules and guidelines when you add transformations to a mapplet:
If you use a Sequence Generator transformation, you must use a reusable Sequence Generator
transformation.
If you use a Stored Procedure transformation, you must configure the Stored Procedure Type to be
Normal.
Metadata Extension
PowerCenter allows end users and partners to extend the metadata stored in the repository by
associating information with individual objects in the repository.
For example, when you create a mapping, you can store the contact information with the mapping.
You associate information with repository metadata using metadata extensions.
PowerCenter Client applications can contain the following types of metadata extensions:
User-defined: You create user-defined metadata extensions using PowerCenter. You can create,
edit, delete, and view user-defined metadata extensions. You can also change the values of user-
defined extensions.
Note:
You see the domains when you create, edit, or view metadata extensions.
If you use third-party applications or other Informatica products, you may see domains such as
Ariba or PowerExchange for Siebel.
You cannot edit vendor-defined domains or change the metadata extensions in them.
User-defined metadata extensions exist within the User Defined Metadata Domain. When you create
metadata extensions for repository objects, you add them to this domain.
Both vendor and user-defined metadata extensions can exist for the following repository objects:
1. Source definitions
2. Target definition
3. Transformations
4. Mappings
5. Mapplets
6. Sessions
7. Tasks
8. Workflows
9. Worklets
Bulk Load:
Powercenter loads the data bypassing the database log.This improves session performance.
But the disadvantage is that target database cannot perform rollback/recovery from the
failed session.
And need to disable/remove the key constraints before loading using the bulk mode
Normal mode:
Database log is not bypassed and therefore the target database can recover from an
incomplete session.
The session performance is not as high as is in the case of bulk load.
Transaction control transformation can be effective or ineffective for the downstream transformations
and targets in the mapping. The transaction control transformation can become ineffective for
downstream transformations or targets if you have used transformation that drops the incoming
transaction boundaries after it. The following transformations drop the transaction boundaries.
Use the following rules and guidelines when you create a mapping with a Transaction Control
transformation:
If the mapping includes an XML target, and you choose to append or create a new document on
commit, the input groups must receive data from the same transaction control point.
Transaction Control transformations connected to any target other than relational, XML, or dynamic
MQSeries targets are ineffective for those targets.
You must connect each target instance to a Transaction Control transformation.
You can connect multiple targets to a single Transaction Control transformation.
You can connect only one effective Transaction Control transformation to a target.
You cannot place a Transaction Control transformation in a pipeline branch that starts with a
Sequence Generator transformation.
If you use a dynamic Lookup transformation and a Transaction Control transformation in the same
mapping, a rolled-back transaction might result in unsynchronized target data.
A Transaction Control transformation may be effective for one target and ineffective for another
target. If each target is connected to an effective Transaction Control transformation, the mapping
is valid.
Either all targets or none of the targets in the mapping should be connected to an effective
Transaction Control transformation.
LOOKUP
Connected Unconnected
Connected to pipeline Unconnected and receives input from :LKP
expression in any other transformation
Can use STATIC and DYNAMIC cache Can use only static cache
Can return more than one value Can return only one value
Caches all the ports Caches only lookup condition port(s) and return
port
Supports user defined default values which it Do not support any defined default values
returns when lookup conditions are not satisfied
Active and Passive transformation
1. Change the number of rows between the transformation input and output
Ex- Filter
2. Changes the transaction boundary by defining commit or rollback. Ex- Transaction control
3. Change the row type like: insert, update, delete or reject. Ex- update strategy
Passive transformation- Which does not change the number of rows passes through it and neither
change the transaction boundary nor type of row. Example- Expression transformation
Types of Lookup:
Cache Lookup : Static/ read only Cache, Dynamic cache
Un-cached Lookup
Persistent and Non-persistent cache
Static cache: Which does not modify the cache once it is built and remains same when session
runs.
Dynamic cache: Which refresh during the session run by inserting or updating records in cache
based on the incoming data from source.
Note- By default informatica cache is static
Persistent cache: when Informatica retains the cache even after session run.
Non-persistent cache: When informatica deletes cache after completion of session.
Note- Lookup maintains a table for cache
Note- Dynamic Cache is synchronized with the target.
When sorter works like Active transformation?
When we select distinct option in its properties
Name any 4 files which Informatica server creates when it runs the session
Session log, Workflow log, Error log and Badfile
There are 10000 records in a flat file and we want to load record number 500 to record
number 600 in target.How we can do it?
Use sequence generator to generate row number. Then use filter to select row number from
500 to 600.
Types of SCD-2:
Versioning
Flag
Date
How can we store previous session log and prevent to overrite by current session log?
Just run session in time stamp mode.
Mapplet:
It is a set of reusable transformations for applying same business logic.
Session task
Assignment task
Command task
Control task
Decision task
E-mail task
Event raise task
Event wait task
Timer task
Link task