Informatica Overview

Overview & Components:

Informatica provides an environment that can extract data from multiple sources, transform the data according to the business logic that is built in the Informatica Client application and load the transformed data into files or relational targets.

Informatica components:

Informatica Server - The Informatica Server reads mapping and session information from the Repository. It extracts data from the mapping Sources and stores the data in memory while it applies the transformation rules in the mapping.The Informatica Server loads the transformed data into the mapping Targets. Platforms supported

•          Windows NT/2000

•          UNIX / Linux

•          Solaris

Informatica Client:

1) Repository Manager - To create and administer the Metadata Repository using the OPB tables and the MX views.

To create Repository Users and Groups, assign Privileges and Permissions.

Manage Folders and Locks.

Print Reports containing Repository Data.

2) Designer - To add source and target definitions to the repository. It is also used to create mappings that contain data transformation instructions

3) Workflow Manager - To create, schedule, execute sessions.

         4) Workflow Monitor – To monitor and execute sessions.


Designer:

Informatica’s Designer is the client application used to create and manage sources, targets, and the associated mappings between them. The Informatica Server uses the instructions configured in the mapping and its associated session to move data from sources to targets.

The client application provides five tools which is used to create mappings:

• Source Analyzer. Use to import or create source definitions for flat file, ERP, and relational sources.
• Target Designer. Use to import or create target definitions.
• Transformation Developer. Used to create reusable object that generates or modifies data.
• Mapplet Designer. Used to create a reusable object that represents a set of transformations.
• Mapping Designer. Used to create mappings.

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

Target Designer:

The following types of source definitions can be imported or created or modified in the Source Analyzer:

•          File - Fixed and delimited flat files and XML

•          Relational - Oracle, Sybase, Sybase IQ, Informix, IBM DB2, Microsoft SQL Server, and Teradata.

•          Extended – 

•          Integration server to load data into SAP BW.

•          PowerConnect for IBM MQSeries to load data into IBM MQSeries message queues.

•          Other - Microsoft Access.

•          ODBC or native drivers, FTP, or external loaders

Mapping:

Mappings represent the data flow between sources and targets. When the Informatica Server runs a session, it uses the instructions configured in the mapping to read, transform, and write data

Every mapping must contain the following components:

·         Source / Target definitions.

·         One or more transformations

·         Connectors

·         Mapplets (Optional)

Transformations used in Informatica

A transformation is a repository object that generates, modifies, or passes data. The Designer provides a set of transformations that perform specific functions. Transformations in a mapping represent the operations the Informatica Server performs on data. Data passes into and out of transformations through ports that you connect in a mapping or mapplet

Transformations can be active or passive.

Active Transformation: 

An Active Transformation can change the number of rows that pass through it.

Ex.:

·         Advanced External Procedure

·         Aggregator

·         ERP Source Qualifier

·         Filter

·         Joiner

·         Normalizer

·         Rank

·         Source Qualifier

·         Router

·         Update Strategy

Passive Transformation: 

A Passive Transformation does not change the number of rows that pass through it.

Ex:

·         Expression

·         External Procedure

·         Input

·         Lookup

·         Output

·         Sequence Generator

·         Stored Procedure

·         XML Source Qualifier

Workflow Manager:

A workflow is a set of instructions on how to execute tasks such as sessions, emails, and shell commands. A session is now one of the many tasks you can execute in the Workflow Manager. The Workflow Manager provides other tasks such as Assignment, Decision, and Events. You can also create branches with conditional links. In addition, you can batch workflows by creating worklets in the Workflow Manager.

Workflow Manager Tools:

Ø  Task Developer

•          Use the Task Developer to create tasks you want to execute in the workflow.

Ø  Workflow Designer

•          Use the Workflow Designer to create a workflow by connecting tasks with links. You can also create tasks in the Workflow Designer as you develop the workflow.

Ø  Worklet Designer

•          Use the Worklet Designer to create a worklet.

Workflow Tasks:

·         Command. Specifies a shell command run during the workflow.

·         Control. Stops or aborts the workflow.

·         Decision. Specifies a condition to evaluate.

·         Email. Sends email during the workflow.

·         Event-Raise. Notifies the Event-Wait task that an event has occurred.

·         Event-Wait. Waits for an event to occur before executing the next task.

·         Session. Runs a mapping you create in the Designer.

·         Assignment. Assigns a value to a workflow variable.

·         Timer. Waits for a timed event to trigger.

Workflow Monitor:

To monitor workflow, worklets, and tasks.The Workflow Monitor displays information about workflows in two views:

• Gantt Chart view
• Task view.

Debugger:

Debugger used to 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